Choosing an NFT payment gateway is an infrastructure decision, not only a checkout decision. This reusable due diligence checklist helps marketplace, product, engineering, finance, and compliance teams compare providers, structure an RFP, run a proof of concept, and identify operational risks before connecting a gateway to production.
Overview
An NFT payment gateway may sit between your marketplace, a buyer’s wallet, blockchain networks, card or bank-rail providers, and your settlement accounts. A provider that looks suitable in a product demonstration can still create problems around unsupported wallets, delayed webhooks, unclear refunds, restricted regions, custody, or difficult data exports.
Start by defining the payment flows you actually need. Write down whether buyers will pay directly from a non-custodial wallet, use a card or bank transfer through a fiat onramp, pay in several tokens, or complete a gasless NFT checkout. Also document whether the gateway must support primary sales, secondary sales, offers, auctions, creator payouts, royalties, refunds, and administrative reversals.
Use the following comparison dimensions for every provider:
| Area | Questions to ask | Evidence to request |
|---|---|---|
| Networks and assets | Which chains, tokens, stablecoins, contract standards, and test networks are supported? | Current support matrix, integration documentation, and change-notice process |
| Wallet coverage | Does the flow support WalletConnect, browser wallets, mobile wallets, embedded wallets, and account abstraction where required? | Compatibility matrix and tested device or wallet list |
| API and webhooks | Can the marketplace create payment intents, verify transactions, receive status events, and reconcile retries? | API reference, SDKs, webhook schema, authentication model, and sandbox access |
| Settlement | When and in what asset does the merchant receive funds? How are network fees, conversion, and reserves handled? | Settlement schedule, sample reports, fee definitions, and exception policy |
| Custody | Who controls private keys during checkout, settlement, and payout? | Architecture description, key-management controls, and account-recovery procedures |
| Risk and compliance | What onboarding, transaction monitoring, identity checks, sanctions screening, and account restrictions apply? | Compliance overview, escalation process, supported regions, and customer responsibilities |
| Operations | What uptime commitments, support channels, incident notices, and service credits are available? | Service terms, status history if available, support policy, and escalation contacts |
| Exit and portability | Can you export transactions, customer records, payout data, and configuration if the relationship ends? | Data-export format, retention terms, termination process, and migration assistance |
Do not treat a long chain list as proof of fit. The relevant question is whether the provider supports your exact contract behavior, settlement requirements, wallet audience, and operating regions with documented controls.
Checklist by scenario
For a new NFT marketplace
- Map the complete purchase sequence: quote creation, wallet connection, approval, mint or transfer, confirmation, fulfillment, and receipt.
- Confirm whether the gateway can distinguish a valid on-chain payment from a transaction that is pending, replaced, reverted, underpaid, or sent to the wrong address.
- Ask how the system handles network congestion, token decimals, expired quotes, duplicate submissions, and chain reorganizations.
- Require test credentials and a sandbox that mirrors production authentication, webhook signatures, and error responses.
- Check whether your marketplace can remain operational if the gateway is unavailable, including how pending orders are reconciled after recovery.
For contract-specific requirements, pair gateway review with a smart contract payment integration checklist and test every failure path before launch.
For an established marketplace adding chains or tokens
- Compare the provider’s network support with your existing indexing, custody, analytics, and payout systems.
- Verify whether the same API objects and webhook events work across chains or whether each network has separate behavior.
- Assess liquidity and conversion handling for each accepted asset rather than assuming that all tokens settle identically.
- Set a deprecation and migration requirement for APIs, SDKs, smart-contract adapters, and supported wallets.
A multi-chain NFT payments support matrix can help product and engineering teams separate essential networks from future expansion options.
For creator stores and managed commerce
- Decide whether creators receive funds directly, through a platform-controlled account, or through a custodial wallet for creators.
- Define payout ownership, approval roles, beneficiary changes, failed payouts, tax-record access, and account recovery.
- Confirm how royalties, marketplace fees, refunds, chargebacks, and promotional discounts appear in statements.
- Ask whether the provider supports branded or embedded wallet flows without obscuring custody and recovery responsibilities.
Use the NFT merchant onboarding workflow to document responsibilities from wallet setup through the first successful payout.
For fiat-enabled NFT checkout
- List the countries, currencies, payment methods, and buyer verification steps required for launch, then request confirmation for each one.
- Clarify who handles identity checks, payment disputes, refunds, conversion, chargebacks, and restricted transactions.
- Ask whether fiat quotes expire and how the buyer is informed when the crypto amount changes.
- Compare settlement reports with your ledger requirements, including gross amount, fees, conversion rate, blockchain transaction ID, and net payout.
Finance teams should test the reporting flow with a crypto-to-fiat NFT settlement reconciliation template before approving a provider.
What to double-check
Security and custody
Ask for a plain-language architecture review. Identify where keys, signing authority, payment credentials, personal data, and webhook secrets are stored. Confirm role-based access, approval controls, key rotation, audit logs, backup procedures, incident notification, and recovery testing. A non-custodial wallet integration and a custodial wallet model create different responsibilities; do not evaluate them with the same risk assumptions.
API behavior and data ownership
Require stable identifiers for orders, payment intents, wallets, transactions, and payouts. Confirm idempotency behavior, rate limits, pagination, timestamp formats, webhook retries, event ordering, signature verification, and replay protection. Ask how long records remain available and whether you can export raw events as well as normalized reports.
Include versioning and deprecation obligations in the contract. The NFT payment API versioning guide provides a useful set of questions for backward compatibility and webhook changes.
Fees, restrictions, and service terms
Separate every cost into a model your finance team can test: gateway fees, card or bank-rail charges, blockchain gas, conversion spread, payout fees, refunds, reserves, dispute handling, and minimums. Do not rely on a single blended rate. Ask which fees can change, how much notice is provided, and whether fees differ by chain, asset, region, or payment method.
Have compliance and legal reviewers confirm the provider’s onboarding requirements, restricted activities, supported jurisdictions, transaction-monitoring process, and account-freeze procedure. These obligations vary by business model and location, so treat vendor materials as inputs for review rather than a substitute for professional advice.
Proof-of-concept scorecard
Run the same test script with each shortlisted provider. Score each category from zero to five, and record evidence rather than impressions:
- Checkout completion across required wallets and devices: 20 percent
- Transaction accuracy, failure handling, and webhook reliability: 20 percent
- Network, token, contract, and settlement fit: 15 percent
- Security, custody, and access controls: 15 percent
- Reporting, reconciliation, and data portability: 10 percent
- Compliance workflow and regional availability: 10 percent
- Support, service terms, and commercial clarity: 10 percent
Set minimum scores for non-negotiable areas. A high total score should not compensate for a failure in custody, settlement, security, or required regional coverage.
Common mistakes
- Comparing features instead of workflows: A provider may list a wallet or chain but not support the exact purchase, payout, or contract path you need.
- Testing only the happy path: Include rejected transactions, expired quotes, duplicate clicks, dropped webhooks, underpayment, wallet switching, refunds, and delayed confirmations.
- Ignoring the buyer’s device: Desktop browser wallets, mobile deep links, QR flows, embedded wallets, and accessibility requirements need separate tests. Use the mobile and accessibility QA checklist alongside gateway testing.
- Treating settlement as an accounting detail: Reconcile blockchain transaction IDs, gateway events, orders, fees, royalties, and creator payouts before launch.
- Accepting vague uptime language: Define what is measured, which components are covered, how incidents are communicated, and what happens during a prolonged outage.
- Creating avoidable lock-in: Keep your internal order model, customer records, and reporting independent from proprietary identifiers where practical. Require export and migration terms before signing.
When to revisit
Review the gateway before seasonal planning cycles, major product releases, new-market launches, annual renewals, and any expansion to a new chain, token, wallet type, or fiat payment method. Reopen the assessment immediately after a material outage, security incident, regulatory change, pricing revision, acquisition, API deprecation, or change to supported regions.
At each review, repeat a small production-like test: connect the required wallets, create and expire a quote, complete a successful purchase, force a rejected or underpaid transaction, receive and verify webhooks, issue or simulate a refund, and reconcile the resulting settlement. Compare the provider’s current documentation, service terms, security materials, status communications, and fee schedule with the records used in your original approval.
Finally, maintain a one-page decision record naming the owner, approved use cases, excluded use cases, evidence reviewed, open risks, renewal date, and exit plan. That record turns an informal vendor choice into a repeatable procurement control. For broader transaction-risk coverage, link it to your crypto payment monitoring workflow and NFT payment API testing checklist.