An NFT marketplace payment compliance workflow should decide what happens before a user buys, sells, or receives funds—not after a problem appears. This reusable checklist shows where identity verification, sanctions screening, wallet risk checks, payment holds, manual review, and record retention fit into the transaction journey. Use it as an operational starting point, then confirm the applicable requirements, provider capabilities, and marketplace policies with qualified compliance counsel.
Overview
Compliance controls are easiest to manage when they are connected to specific events in the payment flow. A marketplace may have different obligations and risk decisions for account creation, an external wallet connection, a fiat onramp handoff, a crypto checkout, a creator payout, and a refund or failed transaction. Treating every event as the same can create gaps or unnecessary friction.
A practical NFT marketplace AML workflow usually separates five decisions:
- Who is the customer? Collect and verify the information required for the marketplace’s user type, product, jurisdictions, and providers.
- Is the person or entity restricted? Apply sanctions and other applicable screening controls using appropriately maintained data sources.
- Is the payment or wallet activity unusually risky? Review transaction context, wallet signals, account behavior, and payment-provider alerts.
- Should the transaction proceed? Route it to approval, rejection, or manual review according to documented rules.
- Can the marketplace explain the decision later? Preserve relevant records, decision reasons, evidence, and escalation notes for the required retention period.
The process map is: account creation → identity and jurisdiction checks → wallet connection or fiat onramp handoff → sanctions and wallet screening → transaction risk decision → payment, mint, transfer, or hold → payout review → record retention and escalation. The exact order may vary by custody model and payment architecture. A custodial marketplace controls more of the wallet and payout process, while a non-custodial marketplace may need to coordinate controls across its checkout provider, wallet infrastructure, and onramp partners. For background, compare the operational implications in Custodial vs Non-Custodial Wallets for NFT Marketplaces.
Checklist by scenario
1. Account creation and onboarding
- Define which user types require onboarding: buyers, sellers, creators, collectors, business accounts, and payout recipients.
- Capture the minimum information needed to identify the user, determine location, and apply the marketplace’s risk policy.
- Identify beneficial owners or controlling persons where the account structure and applicable requirements call for it.
- Check age, geographic eligibility, restricted-country rules, and product access before enabling purchases or payouts.
- Record the verification status, provider response, timestamp, and reason for any failed or incomplete check.
- State clearly in marketplace terms and privacy notices how verification, screening, holds, and account restrictions work.
2. Fiat onramp and payment-provider handoffs
- Document which party performs customer identification, payment screening, sanctions screening, fraud checks, and transaction monitoring.
- Define the handoff point: what information is shared, what identifier links the records, and which system is the source of truth.
- Confirm how the provider reports declined, pending, reversed, disputed, or held payments to the marketplace.
- Prevent the marketplace from treating a successful card or bank authorization as proof that all wallet and compliance checks have passed.
- Specify when an NFT transfer, mint, or creator payout remains paused while the payment provider completes its review.
- Test webhook authentication, duplicate events, delayed events, and provider outages before launch. The NFT Marketplace Payment Integration Testing Checklist can support this control review.
3. Wallet connection and crypto checkout
- Record the wallet address, chain, relevant transaction identifier, user account, and time of the screening decision.
- Screen the wallet and transaction context using a risk-data provider appropriate to the marketplace’s needs; document what the provider can and cannot detect.
- Set rules for exposure to sanctioned addresses, theft indicators, scams, mixers or obfuscation services where relevant to the marketplace’s risk policy, and other high-risk typologies identified by counsel or providers.
- Do not assume that a wallet address alone identifies its owner. Use wallet screening as one input alongside account, payment, behavioral, and transaction information.
- For multi-chain operations, maintain chain-specific coverage and map assets, contracts, bridges, and transaction identifiers consistently.
- Apply controls before irreversible actions where possible, especially before releasing an NFT, transferring funds, or allowing a payout.
4. High-risk signals and manual review
- Define signals that require review, such as inconsistent identity and payment details, rapid account changes, unusual transaction size or frequency, repeated failed checks, or wallet exposure flagged by a screening provider.
- Use a risk-based queue with clear priority levels, ownership, service targets, and escalation paths.
- Require reviewers to record the evidence considered, questions sent to the customer, decision rationale, and approving person where applicable.
- Limit account functionality while a review is open according to documented policy. A hold should specify what is paused: purchase, transfer, listing, withdrawal, or payout.
- Use consistent customer communications that avoid disclosing sensitive detection logic or making unsupported accusations.
5. Blocked payments, rejected accounts, and escalations
- Define when a transaction must be blocked, when it may be declined, and when it can be released after additional information or review.
- Preserve the decision and supporting evidence even when no transaction completes.
- Provide an internal escalation route for possible sanctions matches, suspicious activity, stolen assets, account takeover, and repeated evasion attempts.
- Escalate legal and regulatory questions to qualified compliance counsel rather than relying on a product, support, or engineering decision alone.
- Coordinate investigations with payment providers and wallet-screening vendors without sharing more personal information than necessary.
6. Payouts and ongoing monitoring
- Recheck payout recipients and destination wallets when policy, risk, or transaction circumstances require it.
- Separate sale proceeds, royalties, refunds, reserves, and fees in the ledger so compliance and finance teams can reconstruct the flow.
- Monitor changes to creator identity, payout destination, wallet permissions, and account access.
- Keep payout statements and audit fields aligned with the compliance record. See the NFT Marketplace Payout Statements guide for a reporting structure.
What to double-check
Before approving the workflow, create a control matrix with these columns: event, owner, data collected, screening performed, decision outcome, hold behavior, customer message, retained evidence, and escalation route. This exposes gaps between a marketplace’s NFT payments API, wallet API, payment gateway, and operations console.
Check the following areas in particular:
- Jurisdiction scope: Confirm which countries and user locations the marketplace serves, and whether the same product is available everywhere.
- Provider responsibility: Read current agreements and technical documentation. A provider’s screening feature may not cover every asset, chain, user type, or legal obligation.
- Data quality: Test name variations, transliteration, corporate accounts, false positives, missing wallet labels, and delayed screening results.
- Decision consistency: Ensure support staff cannot bypass a compliance hold without an authorized override and a recorded reason.
- Security: Restrict access to identity documents, screening results, and investigation notes. Review API keys, webhook secrets, and administrative permissions using the secret rotation runbook.
- Retention: Confirm the applicable retention period for identity, transaction, screening, case, and communications records. Do not choose a period solely because a database or vendor defaults to it.
- Incident recovery: Define what happens if screening is unavailable, a webhook is delayed, a transaction is stuck, or a false match blocks a legitimate buyer. The failed transaction recovery workflow is a useful companion control.
Common mistakes
- Screening only at signup: Risk can change at checkout, wallet connection, payout, or after a material account change.
- Using one signal as a final verdict: A wallet flag, payment decline, or name match should follow the marketplace’s documented review process rather than trigger an unexplained automatic conclusion.
- Leaving holds undefined: “Compliance review” is not an operational state unless teams know what is frozen, who owns the case, and how release decisions are recorded.
- Ignoring non-custodial boundaries: A marketplace may not control an external wallet, but it still needs clear rules for whether a transaction can proceed.
- Failing to reconcile systems: If the checkout, blockchain indexer, wallet service, and ledger use different identifiers, investigations become slower and less reliable.
- Promising fixed timelines or outcomes: Customer-facing language should explain possible review and delay without guaranteeing approval, release, or a particular legal result.
- Forgetting policy updates: Old terms, outdated provider assumptions, and stale screening configurations can undermine otherwise strong controls.
When to revisit
Review this NFT payment compliance checklist before seasonal planning cycles and whenever workflows or tools change. At minimum, schedule a documented review at least twice a year, while recognizing that applicable requirements and provider terms may call for more frequent updates.
Trigger an additional review when launching a new country, chain, asset type, fiat onramp, wallet model, or payout method; changing a payment gateway or screening provider; introducing embedded wallets; changing custody arrangements; investigating suspicious activity; or testing a major incident. Also revisit the workflow after material changes to marketplace terms, privacy notices, retention rules, or customer communications.
To make the review actionable, assign one owner to update the control matrix, one technical owner to test integrations and holds, one operations owner to sample cases, and qualified compliance counsel to assess jurisdiction-specific questions. Record the review date, changes made, open risks, and next test date. Then run a small end-to-end test—from account creation through wallet screening, payment hold, manual review, release or rejection, payout, and record retrieval—before treating the updated workflow as complete.