> ## Content Index
> Fetch the complete content index at: https://blog.amlbot.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# AML for Crypto OTC Desks: How to Screen Clients, Wallets, and Trades
- URL: https://blog.amlbot.com/crypto-otc-aml/
- Published: 2026-10-30T12:53:42.000Z
- Updated: 2026-10-30T12:53:42.000Z
- Author: Andrew Aleksandrov

The hardest compliance moment on an OTC desk is rarely onboarding. It is the message that lands twenty minutes before settlement: a new settlement address, supplied by the client, replacing the one reviewed when the relationship opened. Nothing in that request is necessarily wrong, clients do rotate custodians. But the desk has to decide, on a trade already priced, whether the destination changes the risk picture, and it usually decides without supervisory precedent to copy. FATF's [Seventh Targeted Update on virtual assets and VASPs](https://www.fatf-gafi.org/en/publications/Fatfrecommendations/targeted-updated-virtualassets-vasps-2026.html?ref=blog.amlbot.com), published in July 2026, found that of jurisdictions with Travel Rule legislation in force, around 60% had issued no related finding, directive, or enforcement action.

An OTC trade differs from a retail order in more than size. One ticket can involve negotiated pricing, an individual or corporate client, a third-party introducer, crypto and fiat legs, self-hosted wallets, an institutional custodian, and settlement to an address nobody has seen before. So “who is the client?” is not enough. The desk also needs to know where the assets came from, where they are going, and whether the trade makes sense for this client. AML controls for a crypto OTC desk should follow the trade flow from client onboarding through funding, execution, settlement, and ongoing monitoring.

## Map the OTC Trade Flow Before Applying AML Controls

Before choosing checks, write down the trade as it actually happens:

**Client → Onboarding → Trade Request → Funding → Execution → Settlement → Ongoing Relationship**

Whether an OTC desk qualifies as a VASP, CASP, MSB, or another regulated financial service depends on the activities performed, custody or control of assets, jurisdiction, customer location, and settlement structure. Where the activity falls within a regulated framework, CDD, recordkeeping, sanctions, transaction monitoring, and reporting obligations may apply under that framework. [FATF Recommendation 15](https://www.fatf-gafi.org/en/publications/Fatfrecommendations/Guidance-rba-virtual-assets-2021.html?ref=blog.amlbot.com) requires VASPs within its scope to be subject to relevant AML/CFT preventive measures and risk-based controls, and FATF's 2021 risk-based approach guidance should be read together with its later updates, including the 2025 revisions.

The flow changes shape with the pair. In crypto-to-fiat and fiat-to-crypto, one leg carries bank-rail evidence and the other on-chain evidence, and explaining the trade later needs both. In crypto-to-crypto, both settlement legs sit on-chain, so both ends carry blockchain risk context.

What this rules out is the single gate, because each stage answers a different question:

- Onboarding → Who is the client?
- Trade Request → Does this trade fit the client profile?
- Funding → Where are the assets coming from?
- Wallet Screening → What risk attaches to the crypto source?
- Settlement → Where are the assets going?
- Post-Trade → Has the relationship or the risk changed?

## Onboard the Client Before the First OTC Trade

### Individual and Corporate Clients Need Different Evidence

For an individual client, the file generally covers identity, relevant screening, residence and geography, expected activity, and the purpose or intended use of the service.

For a company, the set is wider: the legal entity, directors and authorised persons, beneficial ownership, actual business activity, expected trade volumes, and relevant corporate documentation. In practical terms, the corporate file has to answer who ultimately controls the entity, whether the people issuing trading instructions are authorized to issue them, and whether the stated business explains the asset flows about to arrive.

> For the general mechanics, see our guide to [crypto customer due diligence](https://blog.amlbot.com/crypto-customer-due-diligence/); for the entity side, [crypto KYB and beneficial ownership verification](https://blog.amlbot.com/crypto-kyb-business-verification-vasps/) covers how corporate structures are unpacked.

### Understand Why the Client Is Using the OTC Desk

Clients choose negotiated execution for price certainty, size, discretion, or settlement flexibility. The use of an OTC desk is not itself a suspicious activity indicator; risk depends on the customer, funding source, transaction pattern, counterparties, geography, and purpose of the trade.

What matters is that the reason is recorded rather than assumed: purpose of the relationship, expected trade size and frequency, expected assets, expected funding method, typical source and destination, whether the client trades for itself or another entity, and expected counterparties where relevant.

A large trade can only be assessed properly if the desk knows what normal activity should look like for that client. Without that baseline, escalation decisions become guesses dressed up as judgments.

## Decide When Source of Funds or Source of Wealth Needs Deeper Review

Not every OTC trade requires a Source of Wealth file, and no fixed trade size automatically triggers enhanced due diligence. Depth depends on applicable regulation, customer risk, trade size relative to the client's own profile, source and destination, geography, ownership complexity, transaction behavior, and other risk indicators.

In practical terms, the useful question is not *“How big is this?” But* *“What here is not yet explained?”* Triggers that commonly justify a more in-depth look:

- an amount materially inconsistent with the expected profile;
- funding that arrives without a prior explanation;
- a newly created or previously unknown funding wallet;
- third-party funding;
- an opaque corporate structure;
- an unusual asset origin for the stated business;
- a sudden change in behavior against the client's own history;
- higher-risk transaction exposure identified on-chain;
- a PEP or other higher-risk relationship, where applicable.

Source of Funds review in crypto is strongest when customer explanations and supporting documents are assessed together with the actual on-chain path of the assets. One layer alone produces files that look complete and explain nothing. Our guide on how to [verify Source of Funds against on-chain evidence](https://blog.amlbot.com/source-of-funds-in-crypto-aml-how-to-match-customer-information-with-on-chain-evidence/) covers the matching process, and already treats an OTC trade confirmation as a supporting record a desk may be asked to produce.

## Screen the Funding Wallet Before Accepting Crypto

When a client funds the trade in crypto, the desk establishes which address is sending the funds, whether it fits the client context already on file, whether there is sanctions or direct high-risk exposure, what relevant indirect exposure exists, which service or entity the address is attributed to, and — where deeper review is warranted — the path the funds took to get there.

A risk result is an input, not a decision. A low-risk screening result does not by itself mean the transfer should be accepted; the decision sits alongside the customer profile, transaction size, stated purpose, other evidence in the file, and internal risk policy. Wallet screening does not replace customer due diligence because on-chain risk does not establish who the customer is or why the trade is taking place.

Two providers can also return different results on the same address, for reasons closer to attribution data and scoring methodology than to one being wrong — see [why wallet risk results can differ across AML providers](https://blog.amlbot.com/why-crypto-aml-results-differ/). At the funding stage, [AML wallet screening](https://amlbot.com/crypto-wallet-screening?ref=blog.amlbot.com) runs before the crypto leg is accepted rather than after it settles.

## Screen the Settlement Destination Before Releasing Crypto

This is the distinction that separates OTC workflow design from retail. The wallet funding an OTC trade and the wallet receiving settlement are separate risk points and may require separate screening decisions. A clean inbound transfer says nothing about where the value goes next.

Before releasing crypto, a desk can check the destination against the same risk model it applies on the way in: sanctions exposure, known high-risk attribution, the counterparty or service type behind the address, whether it was supplied only moments ago, whether it contradicts information given at onboarding, whether it belongs to a third party, whether it is self-hosted, and whether the jurisdiction or counterparty context is unusual for this client.

Self-hosted destinations deserve care rather than suspicion. Not every withdrawal to a self-hosted wallet requires proof of ownership, and treating all of them as high risk misfires on ordinary institutional clients. Depending on applicable rules and risk, a business may rely on a customer declaration, address verification, technical proof of control, additional documentation, or enhanced monitoring. Technical proof that a customer controls a self-hosted wallet does not necessarily prove legal or beneficial ownership of the assets held in that wallet. Our guide sets out [what self-hosted wallet ownership verification can and cannot prove](https://blog.amlbot.com/self-hosted-wallet-ownership-verification/). In the EU, CASPs handling relevant self-hosted-address transfers also have specific risk-assessment and transfer-information requirements under the [EBA Travel Rule Guidelines](https://www.eba.europa.eu/activities/single-rulebook/regulatory-activities/anti-money-laundering-and-countering-financing-terrorism/guidelines-information-requirements-relation-transfers-funds-and-certain-crypto-assets-transfers?ref=blog.amlbot.com), applicable since 30 December 2024.

## Treat High-Value or Unusual Trades With Risk-Based Escalation

High value is context, not an automatic verdict. A high-value OTC trade does not automatically require enhanced due diligence solely because of its size; the decision depends on applicable rules and the full customer and transaction risk context. A $500,000 ticket can be routine for an institutional treasury and distinctly odd for a client whose file describes occasional retail-scale activity.

In practical terms, escalation is better anchored to mismatch than to magnitude. Signals worth escalating include a trade materially above expected activity, repeated trades sitting just below the desk's own escalation levels, third-party funding, third-party settlement, an economic rationale that does not hold together, unexplained wallet changes, a source-of-funds mismatch, sudden geography changes, mixer or other high-risk exposure, multiple accounts or entities connected to the same flows, and repeated rapid crypto-to-fiat conversions without the business rationale the profile would predict.

The response is equally graded: request more information, open a SoF or SoW review, ask for additional KYB or ownership documents, route the trade to management or compliance approval where required, run a deeper blockchain review, delay settlement where legally and contractually permitted, or decline or report where applicable. One universal action for every alert does not work, because an alert on a new destination address and an alert on structuring behavior are not the same problem. Our overview of [risk-based AML controls for crypto businesses](https://blog.amlbot.com/risk-based-approach-crypto-aml/) covers how these tiers are built, and geography works best as one input rather than a verdict — see [jurisdiction risk in crypto AML](https://blog.amlbot.com/jurisdiction-risk-crypto-aml/).

## Monitor Repeat OTC Clients Across Trades

OTC AML does not end at settlement. For a recurring client the risk picture is built from the sequence, not the ticket: cumulative volumes, frequency, changing source and destination wallets, new counterparties, repeated risk exposures, behavioral changes, structuring patterns, explanations that stop lining up with earlier ones, and updated sanctions or PEP status where applicable.

A single OTC trade may look reasonable in isolation while a sequence of trades reveals a different risk pattern. A recurring OTC client should be assessed across multiple trades because cumulative activity can reveal patterns that are not visible in a single transaction. That only works if the onboarding baseline is something the desk compares against, rather than a form filled in once and never reopened.

Our guides cover [how KYT works in crypto transaction monitoring](https://blog.amlbot.com/know-your-transaction-kyt/) and how [continuous crypto transaction monitoring](https://blog.amlbot.com/amlbot-continuous-transaction-monitoring/) differs from checking an address once at the point of transfer. Between trades, [crypto transaction monitoring](https://amlbot.com/transaction-monitoring?ref=blog.amlbot.com) keeps actual activity measured against the expected profile.

## When the Other Side Is Another Exchange, Broker, or VASP

Where an OTC desk trades or settles through another regulated crypto provider, customer screening does not cover the institutional relationship. Customer due diligence and counterparty VASP due diligence are separate controls that can both be relevant to the same OTC trade.

Those checks sit at the entity level: the exact legal entity, its regulatory status where applicable, service scope, jurisdiction, settlement wallets, AML and Travel Rule readiness where relevant, and ongoing on-chain risk. Client due diligence and VASP counterparty due diligence answer different questions. Our [counterparty VASP due diligence](https://blog.amlbot.com/counterparty-vasp-due-diligence-guide/) guide covers the full process.

## A Practical AML Workflow for Crypto OTC Desks

Each point in the trade flow carries its control and produces its own evidence:

- **Client onboarding** — KYC/KYB/CDD → verified client and risk profile.
- **Trade request** — profile consistency check → documented purpose and expected activity.
- **Funding** — SoF review where warranted → funding explanation and evidence.
- **Crypto inflow** — wallet and transaction screening → risk result and decision.
- **Escalation** — EDD where triggered → additional review and approval record.
- **Settlement destination** — destination screening → approved settlement address.
- **Execution and settlement** — transaction recordkeeping → complete trade evidence.
- **Ongoing relationship** — KYT and behavioral monitoring → alerts and updated risk profile.
- **Institutional counterparty** — VASP due diligence → counterparty approval and monitoring.

Every control should attach to a point in the trade flow and produce evidence that explains the final decision.

Tooling can carry several of these layers in one place. AMLBot supports [KYC and KYB verification](https://amlbot.com/kyc?ref=blog.amlbot.com) for individual and corporate onboarding, wallet screening at funding and settlement, on-chain risk analysis, and ongoing [transaction monitoring](https://amlbot.com/transaction-monitoring?ref=blog.amlbot.com) across a repeat client's trade history — which matters on an OTC desk because the baseline, the wallet result, and the trade sequence have to sit in one workflow to be read together. What it does not do is stand in for internal AML policy, licensing analysis, legal classification, the compliance officer's decision on a trade, Source of Wealth evidence, or the firm's own reporting responsibility. Those stay with the desk.

## Conclusion

OTC AML is not a single check performed before a large trade. It is a workflow that connects client due diligence, trade context, funding evidence, wallet risk, settlement controls, and ongoing monitoring. Blockchain analytics supports OTC AML decisions but does not replace internal policies, legal obligations, customer evidence, or compliance judgment.

For OTC desks handling recurring or high-value crypto flows, the operational goal is to make every trade explainable from client onboarding through settlement and post-trade monitoring.

## FAQ

### What AML Checks Should a Crypto OTC Desk Perform?

Depending on applicable regulation and risk: KYC and KYB, a customer risk assessment, sanctions and PEP screening, Source of Funds or Source of Wealth review where relevant, wallet screening, transaction monitoring, counterparty due diligence, and recordkeeping and reporting.

### Do Crypto OTC Desks Need KYC?

Where a desk operates within a regulated framework requiring customer due diligence, customer identification and verification will generally form part of its AML process. A desk's status depends on its activities, jurisdiction, and settlement structure rather than on the OTC label.

### Is Enhanced Due Diligence Required for Every Large OTC Crypto Trade?

No. Large value can be a risk factor, but enhanced due diligence should depend on applicable rules and the full context: client profile, expected activity, source of funds, geography, ownership, and transaction exposure.

### When Should an OTC Desk Ask for Source of Funds?

When the trade or relationship creates sufficient reason under the applicable framework or internal risk policy — unusual volume, unexplained funding, high-risk exposure, a profile mismatch, or an enhanced due diligence trigger.

### Should an OTC Desk Screen the Client's Funding Wallet?

Where crypto funds are being accepted, wallet and transaction screening helps assess sanctions exposure, known illicit attribution, and other on-chain risk before the trade proceeds. It is not a substitute for customer due diligence.

### Should the Destination Wallet Also Be Screened?

Yes, where appropriate to the business's AML and sanctions controls. The destination is a separate risk point from the funding wallet and can introduce different counterparty or sanctions exposure.

### Does a Self-Hosted Wallet Require Proof of Ownership?

Not universally. Requirements depend on jurisdiction, transfer type, and risk. Technical proof of control may show the ability to use a private key, but it does not necessarily prove legal or beneficial ownership.

### How Does Transaction Monitoring Work for Repeat OTC Clients?

Monitoring compares cumulative trade volume, wallet changes, counterparties, transaction patterns, and risk exposure against the client's expected profile and historical behavior, so a change in the sequence is visible even when each trade looks ordinary.

### What Is the Difference Between Client Due Diligence and OTC Counterparty Due Diligence?

Client CDD assesses the person or company buying or selling through the desk. Counterparty VASP due diligence assesses another exchange, broker, liquidity provider, or crypto service provider used in the trade or settlement flow.

### Can Blockchain Analytics Replace Source of Funds Checks for an OTC Trade?

No. Blockchain analytics shows fund paths and on-chain exposure, while a Source of Funds review may also require the customer's explanation and supporting records. Where more profound review is needed, both layers should be read together.