AML and KYC for Cryptocurrency Payments and What to Do When a Transfer Is Delayed

AML and KYC for cryptocurrency payments are checks on the origin of assets and the customer's identity that help a service assess transfer risk. Exchanges, crypto payment processors, and payment providers use them before crediting or returning funds. During a review, the history of the assets, sender details, and completeness of the document package all matter.
A blockchain confirmation does not mean the merchant has credited the payment. The network has only recorded a transfer between addresses; the provider may still check the address, earlier movements of the assets, and whether the payer's details match. The same applies when rewards from participating in a cryptocurrency airdrop are later used for payment: a legitimate token allocation still needs a clear paper trail.
If a payment is marked pending, under review, or on hold, do not resend it at random. First save the TxID, recipient address, network, amount, time, and invoice. Then check notifications in your account and messages from the service's official email address. This helps you identify the reason for the delay without risking another review.
What do AML and KYC mean for a cryptocurrency payment?
AML covers anti-money laundering controls: assessing customer and transaction risk, monitoring transactions, screening for sanctions, and, where needed, establishing the payment's economic purpose. KYC is part of the broader compliance process and concerns identifying and verifying the customer. In cryptocurrency payments:
- AML helps assess the origin of assets, links to high-risk addresses, and other signs of suspicious activity
- KYC helps establish and verify the customer's identity and match submitted information against documents
The concepts are related, but they are not interchangeable. Passing KYC on an exchange does not tell another provider where a specific batch of USDT or ETH came from. Likewise, an asset history with no known risky links does not replace verification of the account owner. A basic definition of an airdrop as a token distribution method is not proof that a particular person participated either; allocation records and the subsequent movement of assets are still required.
After large-scale NFT minting with separate wallets, an AML system may analyze a particular transfer, the wallet address, and the associated address cluster. An analytics service builds a transaction graph and measures proximity to:
- sanctioned addresses
- stolen funds
- fraudulent schemes
- mixers
- high-risk services
The output is a risk score, but the final decision depends on the provider's policy and jurisdiction.
The Travel Rule also applies. FATF Recommendation 16 sets an international standard for exchanging specified sender and recipient information between relevant virtual asset service providers.
FATF recommendations are not, by themselves, directly binding law for a user. Specific legal duties come from the rules of the applicable jurisdiction and depend on the type of transfer and the parties' status. Where those rules apply, providers must:
- collect specified sender and recipient data
- retain that data
- transmit it
In the EU, information accompanying transfers of crypto-assets is governed by Regulation (EU) 2023/1113. Depending on the circumstances and the outcome of a risk-based assessment, a provider may:
- request missing information
- reject the transfer
- return the transfer
- suspend the transfer based on its risk assessment
The practical point for users is simple: missing or inconsistent information can delay a technically valid transfer. Requirements for transfers involving self-hosted wallets differ from those for transfers between providers.
A revealing case occurs when a team uses dozens of addresses as part of its operating structure. A compliance system sees:
- a cluster
- synchronized transfers
- a shared funding source
Without an address register and an explanation of each transaction's purpose, the arrangement may look more complicated than it really is.
Why does a crypto payment undergo an AML review?
A payment may undergo an AML review because of automated scoring signals, mandatory regulatory procedures, or a provider's internal rules. A review does not by itself mean that a violation occurred. Even when all required data is present, the service may refer the transaction for additional assessment.
Usually, several factors combine. A large amount may be normal on its own, but a first large payment from a new address, over a new network, with no established account history creates a different risk profile.
| Signal | What the provider sees | What helps explain the transaction |
|---|---|---|
| link to a high-risk address | direct or indirect contact with a sanctioned, fraudulent, or compromised wallet | exchange statement, purchase history, and TxIDs for earlier transfers |
| P2P origin of assets | coins received from an unknown counterparty with an unknown history | P2P order, payment receipt, platform details, and messages within the service |
| unusual amount or frequency | activity that differs from the account's normal behavior | invoice, contract, explanation of the economic purpose, and expected turnover |
| incomplete Travel Rule data | missing or inconsistent sender or recipient information | exact legal name or company name, address, beneficiary details, and payment purpose |
| transfer from a self-hosted wallet | no institution visible to the provider has identified the address owner | signed message or another proof of wallet control accepted by the provider; a test transaction only on its direct instruction |
| chain of intermediary wallets | the source of funds is difficult to trace through numerous intermediate transfers | a complete funds-flow map explaining the role of every address |
The table is not a list of automatic rejection reasons. An indirect link to a high-risk address, for example, does not prove that assets came from illegal activity. One service may clear the transaction after automated scoring, while another sends it to an analyst. Risk-score thresholds and tracing depth are not universal.

Indirect exposure matters too. If the assets passed through a mixer or a compromised address several transactions earlier, the current holder may not know. The analytics system still sees the link. That is why saying "my wallet is new" does not answer questions about the coins' history.
Another group of causes has nothing to do with AML. A transfer may be stuck because of the wrong network, an amount that falls below the minimum after fees, an expired invoice, a missing memo, or too few confirmations. First separate a technical problem from a compliance review by checking the status in your account and the wording of the official message.
How do AML, KYC, and technical checks differ?
AML covers customer and transaction risk assessment, transaction monitoring, and other anti-money laundering measures. KYC focuses on identifying and verifying the customer, while a technical check establishes whether the transfer itself was completed correctly. The three processes may run in sequence or in parallel. As a result, the status in a blockchain explorer often differs from the invoice status shown by the service.
| Check | Main question | Typical data | Possible outcome |
|---|---|---|---|
| AML | where did the assets come from and who are they linked to? | transaction graph, risk score, sanctions matches, source of funds | credit, manual review, return, or rejection |
| KYC | who is the customer or beneficiary? | identity document, selfie, address, date of birth, company details | approval, request for clarification, or account restriction |
| KYB | who controls the legal entity? | registration documents, ownership structure, UBO, business activity | business approval or enhanced review |
| technical | was the blockchain transfer completed correctly? | TxID, network, token, memo, amount, confirmation count | credit, waiting period, or recovery procedure |
Source of funds and source of wealth are also different. The first concerns the origin of the specific funds used for a transaction, such as salary, proceeds from a service, a cryptocurrency purchase, or a contract payment. The second describes how the customer built their overall wealth. A routine payment delay is more likely to require the first package, though a provider may request both.

Why is an identity document sometimes not enough? It proves who the person is, but it does not explain the transaction's economic purpose. For a payment for marketing services, a contract, invoice, bank statement showing the asset purchase, and the TxID for withdrawal to the customer's own wallet form stronger evidence.
What should you do if a crypto payment is delayed?
If a crypto payment is delayed, record the transaction details, verify the official channel for the request, and submit exactly the evidence the provider asks for. Do not split the amount or send another payment without the provider's instructions. Those actions create new signals and make the review harder to resolve.
Keep one support case for each transaction and use the official channel. Include the order number in the subject line or support form and provide the TxID as plain text. An explorer screenshot can illustrate the issue, but it does not replace the transaction hash.
- save the TxID, recipient address, token, network, amount, and sending time
- check the invoice status and confirmation count in a blockchain explorer
- open the notification in the service account and verify the sender's email domain
- list every requested document without making arbitrary substitutions
- prepare a short timeline tracing the funds from their original source to the payment
- submit the materials through the provider's official secure channel or form
- record the case number and the date of the support response
- wait for the decision and reply in the same case if the provider asks a follow-up question
The timeline should make sense without extra explanation. For example: on October 12, the company received payment for an invoice; on October 13, it bought USDT on a regulated exchange; on October 14, it withdrew the assets to a corporate self-hosted wallet; and on October 16, it paid for a subscription. Attach a document or TxID to every transition.

Never send a seed phrase, private key, exchange password, 2FA codes, or a wallet backup file. AML and KYC reviews do not require this information. If an email requests any of it, stop the correspondence and open support yourself through the official website or app.
There is an important limit: support can provide the status and the list of required materials, but it will not usually reveal the weight assigned to every risk signal. Some information may be restricted by internal policy or law. Demanding an "exact contamination percentage" is often pointless. A verifiable chain showing the origin of the assets is more useful.
Which documents prove source of funds?
The strongest source-of-funds package combines an underlying document, a record of the money movement, and blockchain evidence. A balance screenshot is insufficient because it does not show how the assets were obtained. A complete package connects the person, the basis on which the funds were received, and the specific transaction.
For an individual, relevant evidence may include a cryptocurrency purchase receipt, bank statement, exchange report, asset sale agreement, tax document, or payout history. Companies more often need an invoice, contract, corporate bank statement, accounting entry, and explanation of the relationship with the counterparty.
If the funds came from several sources, do not combine every file into one archive without explanation. Create a file index. A name such as 01_invoice.pdf tells an analyst more than IMG_8421.jpg, and a table matching documents to transactions can prevent several rounds of follow-up questions.
A practical package includes:
- a short explanation of the payment's purpose and each party's role
- the TxID of the current payment and earlier transfers
- an exchange statement or P2P order showing the date, amount, and asset
- an invoice, contract, or another underlying document
- proof of control over the self-hosted wallet, if requested
- a translation of key document fields if the provider does not accept its language
Separation is especially important for payouts from operations involving multiple crypto accounts. Do not mix personal funds, a client's budget, and a corporate reserve in one explanation. A separate register of owners, accounts, wallets, and invoices helps show the economic purpose without contradictions.

Before uploading a document, check its expiry date, make sure every corner is readable, and confirm that the name matches the profile. Do not alter details in an image editor. If some data may be redacted, read the provider's requirements first: excessive masking can make a document unusable.
Which tools help investigate a delayed payment?
A basic investigation requires five types of tools: a blockchain explorer, the provider account, a transaction ledger, secure document storage, and a case management system. They do not change the AML decision. Their job is to collect accurate facts quickly and preserve context between support, finance, and the wallet owner.
A blockchain explorer shows the status, confirmation count, addresses, amount, token, and network. Start with the TxID, not an amount search, because identical payments can exist at the same time. For tokens, check the contract event as well as the native coin transfer. A successful transaction does not by itself prove that the intended token reached the recipient; verify the token transfer events, recipient address, and amount.
An optional AML checker may provide a preliminary risk assessment, including a risk score or exposure categories. Such a report can help with initial risk review, but it cannot guarantee a favorable payment-provider decision. The provider may use different data sources, transaction-tracing depth, and thresholds. Save the report date and the address checked because the score may change when labels are updated.

Keep the transaction ledger in a structured table or internal database. At minimum, record the date, asset, network, amount, sender address, recipient address, TxID, economic purpose, owner of the funds, and link to the underlying document. If a record cannot be matched to an invoice or contract, someone will have to reconstruct that information manually during the review.
For a team, add separate case-status fields:
- new provider request
- document package in preparation
- materials under internal review
- response sent
- decision pending
- case closed with credit or return
These statuses prevent duplicated work. Team members should align their explanation of the transaction before submitting it. Differences in dates, payment purpose, or wallet-owner details may prompt further questions from the analyst.
Document storage should support access controls and an audit log. A passport, bank statement, and company ownership structure should not sit in a shared team folder. Create a directory under the case number instead of the person's name, and set a retention period in line with internal policy and applicable law.
The case management system completes the process. Store the case number, official channel, latest response, deadline, and next action there. Avoid copying the documents into notes if they already reside in secure storage. A controlled link with the right permissions is enough.

This toolset creates an orderly review process. A team member joining the case sees the facts, documents, and decision history instead of reconstructing them from fragments of correspondence. And if the provider requests a statement covering an additional period, the team immediately knows who will obtain the file and who will review it before submission.
For complex corporate reviews, especially when several employees submit materials, record the checksum of each transmitted file and its UTC submission time. This makes it possible to verify integrity and identify which document version was sent if correspondence continues for several weeks.
Confirm separately that the provider received the file, for example through a transfer log or a support reply. Do not rename or replace a submitted file under the same name. Create a new version, state the reason for the change, and retain the previous one in a restricted archive. That version history is useful for internal audits too.
How can a crypto payment review end?
A review may end with the payment being credited, a request for more information, a return of the assets, or refusal of service. In serious cases, the service may restrict particular operations or the account under its rules and applicable law. No one can guarantee the outcome or timing in advance.
| Outcome | What it means | Next action |
|---|---|---|
| payment credited | the provider completed its review and allowed the credit | retain the case and evidence package for accounting records |
| clarification requested | the analyst needs a missing document, period, or connection between addresses | reply precisely within the existing case and attach the missing evidence |
| payment being returned | the provider cannot credit the funds but permits a return | confirm the token, network, and return address according to the service's instructions |
| transaction rejected | the risk level falls outside the provider's requirements or a legal restriction applies | request written status information and the available appeal process |
| account restricted | the review concerns more than one payment | preserve the data, meet the review requirements, and do not create duplicate accounts |
A return needs the same care as the original payment. The address must support the correct network and asset. Returning funds to an exchange deposit address without the required memo can trigger a separate recovery process even if the provider sent the assets successfully.
Timing depends on the case's complexity, the jurisdiction, and how quickly the customer responds. Public promises such as "every review is completed within one day" are unreliable. For an urgent payment, allow extra time and arrange an alternative lawful payment channel before a hold occurs, not after it.
How can you reduce the chance of another AML review?
You cannot eliminate the possibility of a review, but a clear source-of-funds history reduces unexplained signals. Keep asset movements traceable, maintain current profile details, and retain documents before making a payment.
Do not try to conceal the origin of coins through a mixer, chains of addresses, or payment splitting. These actions do not erase blockchain history and may increase transaction risk. Providers use different risk-assessment methods.
An operations team can use a short pre-payment check:
- token, network, amount, memo, and invoice expiry verified
- profile KYC or KYB is current, and party names match the documents
- the source of assets has an underlying document and traceable TxID
- P2P transfers received before payment have a documented source-of-funds explanation
- the responsible employee can access the work email account
- a case owner and backup payment method have been assigned
If the team works with rewards, NFTs, or airdrops, keep an address register from the moment each wallet is created. Record the owner, project, funding date, purpose, and linked accounts. This also simplifies the analysis of wallet cluster relationships when an automated system sees a shared gas source or synchronized behavior.

When retaining evidence, follow personal-data protection requirements. Give access to passports, statements, and contracts only to authorized employees who need the materials for the review. Do not copy files into shared chats, and clear the browser's downloads folder in line with the internal retention policy.
How should a team organize AML cases with separate browser sessions?
A team needs controlled access to accounts, correspondence, and evidence, not a way around the review. Using shared browser sessions for different clients creates a risk of uploading the wrong document, losing relevant correspondence, or entering the wrong payment profile.
Afina can separate working browser sessions. Each profile retains cookies and the login state for a specific service, making it easier for an operator to tie a case to the correct client or legal entity. This does not affect the transaction's AML risk score and does not replace KYC. Its benefit is strictly operational: less confusion around access and sessions.
Build the internal process around roles. One employee prepares the document package, another checks the details before submission, and the account owner communicates through one official channel. Do not store wallet access secrets or unencrypted document copies in the browser profile.
Keep the browser session separate from the evidence repository. The profile provides consistent access to the account and email, while documents belong in controlled corporate storage with access logs. After the review, record the outcome, date, and materials used. The next request will not have to begin with a search through old screenshots.
Review access rights regularly, especially after team roles change.
DownloadFAQ — Frequently Asked Questions
What is an AML review of a cryptocurrency payment?
An AML review assesses the origin of assets and the risky links of a specific transaction. The provider analyzes addresses, services along the route, and the evidence submitted.
Why is a payment confirmed on the blockchain but not credited?
The blockchain confirms a transfer between addresses, not the payment provider's decision. Crediting may still depend on an AML, KYC, or technical review.
How does KYC differ from AML?
KYC establishes the customer's identity, while AML assesses the risk of the funds and transaction. Completed KYC does not prove the origin of every new transaction.
Which documents are needed to prove source of funds?
An exchange statement, invoice or contract, and TxIDs for related transfers are commonly required. The provider determines the exact list for each case.
How long does an AML review of a crypto payment take?
There is no universal timeframe. Duration depends on the chain's complexity, jurisdiction, document completeness, and response speed.
Can a low risk score prevent a review?
A low risk score reflects only one AML service's methodology and does not guarantee that the payment will be credited.
Can I resend the payment from another wallet?
First establish the delayed transaction's status and obtain instructions from the provider. Only then decide whether a new transfer is needed.
Can I share a seed phrase for KYC or a refund?
No, a seed phrase and private key are never required for KYC or AML. A request for them is a sign of fraud.
How can a team avoid mixing documents from different AML cases?
Assign each case an owner, a separate register, and a browser session. This reduces confusion between clients and support histories.
