For business

AML screening for exchangers and OTC desks

How to build USDT TRC-20 address screening into an exchanger or OTC workflow: manual checks from the account area, plus API and webhooks on the Business plan.

Why an exchanger should screen addresses

Exchangers and OTC desks accept funds from hundreds of counterparties. A single incoming transfer from an address linked to a hack or sanctions can freeze a hot wallet at a partner exchange and halt all operations. Screening addresses before acceptance and before payout is a basic safeguard for working capital.

Reports also serve as evidence of due diligence when banks, exchanges, or regulators ask questions.

What to screen

  • The client's wallet before accepting USDT: ask the client for an AMLTrace report on their wallet (PDF or public link) and compare the address.
  • The recipient's wallet before payout: ask for a report on the address the client expects the transfer to.
  • Your own hot wallets through WalletConnect regularly: whether risky links have accumulated that a partner exchange would notice.

How to set up the process

  1. Define the review process: required documents, responsibility for exceptions and triggers for further checks; do not decide on a number alone.
  2. Make an AMLTrace report a condition of the deal: the client checks their own wallet (the first check is free) and sends the report before the transfer.
  3. Check your own wallets from the account area, which keeps history with comments on each check.
  4. For automation, use the Business plan API: screening results are available in JSON with the score, categories, sources, and a report link.
  5. Configure webhooks to receive screening events in your CRM or accounting system.
  6. Store PDF reports for each deal as part of your compliance file.

What the Business plan includes

A bundle of checks, API access with JSON responses, webhooks for screening events, screening history, and PDF export. Current limits and prices are on the pricing page; payment is accepted in USDT TRC-20.

Building a repeatable review process

A business needs a consistent decision process, not just an occasional favourable report. Define who collects customer information, who verifies the address and who handles exceptions. Separate wallet review, identification, sanctions questions and the economic purpose of the trade. These processes overlap, but completing one does not mean the others have been completed.

Specify events that trigger reconsideration: a new address, different payer, changed purpose or activity inconsistent with the explanation given. Criteria should fit the business and applicable obligations, not an arbitrary number copied from another provider. Assign responsibility for maintaining the procedure and checking whether staff actually follow it.

What belongs in an operation file

A useful file connects the request, parties, agreed terms, addresses, network and actual transfers. Include the report date and documents considered. Keep each clarification request with its response so another reviewer can see why the question arose. Screenshots without a request identifier and address are weak records for reconstructing a decision later.

For a customer's wallet report, ask the customer to run their own check and share it. Do not describe AMLTrace as an arbitrary manual search for anyone else's wallet. If independent external investigation is required, select a tool that actually supplies that function under suitable terms. Personal-data handling and retention requirements depend on your jurisdiction and business policy.

Handling exceptions and changes

Suppose a regular client wants settlement through a new company but supplies a report for the old address. Earlier successful trades do not explain the new arrangement. Reconfirm current payment details, establish the new party's role and escalate the discrepancy according to policy. A familiar name is not a reason simply to copy the earlier decision.

Record reasoned approvals as well as rejections. A useful note explains the concern, evidence that resolved it and person responsible for the outcome. Give exceptional arrangements a review point rather than leaving them indefinitely approved. API access and notifications may help a workflow, but their actual availability, limits and plan terms must be verified rather than assumed.

Reviewing process quality

Periodically sample completed transactions and ask whether the retained materials reconstruct the decision. Look for missing identifiers, reports from a different wallet and documents not connected to a specific trade. This shows weaknesses more clearly than counting checks alone. Also inspect whether temporary exceptions have quietly become normal practice.

Do not promise customers that a report guarantees acceptance by any exchange or fulfils every business obligation. Distinguish analytical information from a legal opinion in your own procedures and wording. Where a case may require a report to an authority, a restriction or refusal, follow the applicable process and obtain qualified advice instead of relying on general educational guidance.

Sources and scope

These sources describe general principles and technical data, not proof that a particular address was screened in AMLTrace. Examples are hypothetical; this article is not a legal opinion.

Business questions

Can I screen a client's wallet myself?

No. A check is started by the wallet owner through WalletConnect. Ask the client for an AMLTrace report — a PDF or a public link — and compare the address in the report with the transfer address.

How many checks does an exchanger need?

Estimate from the number of your own wallets and how often you check them; clients produce their own reports. Bundle limits are on the pricing page.

Are networks other than TRON supported?

AMLTrace works with TRON network addresses and USDT on the TRC-20 standard.

How do I get API access?

Register, choose the Business plan on the pricing page, and submit a payment request. Access opens in the account area after the payment is confirmed.