Model comparison · custody and settlement

Crypto Gateway Models: Custodial vs Non-Custodial

Crypto gateway models differ by who controls funds, who creates the invoice, who converts to fiat, and who holds records. That model choice affects checkout KYC, merchant onboarding, settlement risk, and support work.

Abstract comparison of crypto gateway custody models shown as connected rails without readable artificial text.
Custody and settlement explain more than the “no KYC” label.

What is the central difference between gateway models?

The central difference is custody. A non-custodial gateway helps create or track a payment while funds settle to the merchant wallet. A custodial gateway receives, holds, converts, or pays out funds, which creates a different operational and compliance profile.

This distinction matters because FinCEN’s CVC guidance emphasizes facts and circumstances, not product labels. A tool called a “gateway” can be software in one setup and money movement infrastructure in another.

Model comparison
ModelCentral entity relationBest fitKYC pressureRecord burden
Self-hosted non-custodialSoftware creates invoice; merchant receives fundsTechnical merchants with wallet operationsLower buyer KYC, merchant handles more controlsHigh internal records
Hosted non-custodialProvider hosts checkout; merchant receives fundsMerchants needing easier setupModerate, policy-dependentShared vendor + merchant records
Custodial processorProvider controls funds or payoutsMerchants needing conversion and supportHigher, especially with fiatProvider statements + merchant reconciliation
Exchange-based workaroundExchange account used as payment railUsually not recommendedHighWeak audit trail

When is non-custodial better?

Non-custodial settlement is better when the merchant can operate wallets securely, reconcile transactions, explain refunds, and accept crypto exposure. It reduces counterparty custody risk, but it moves operational responsibility to the merchant.

When is custodial better?

Custodial processing is better when the merchant needs fiat payout, customer support, conversion, hosted statements, and a provider-managed operational layer. The tradeoff is verification, account controls, and dependency on processor policy.

How should a merchant decide?

A merchant should decide by mapping the payment flow: buyer sends asset, invoice expires, provider observes payment, funds settle, records export, refund path opens, and exceptions escalate. If a provider cannot explain each step, the model is not clear enough.

FAQ

Is non-custodial always safer?

No. It reduces custody risk from the provider, but it increases wallet security and reconciliation responsibility for the merchant.

Does fiat payout require more verification?

Usually yes. Fiat payout adds banking rails, which commonly creates more verification, monitoring, and payout review.

Can a hosted gateway still be non-custodial?

Yes, if the provider hosts the invoice layer but settlement goes directly to the merchant wallet.