Create a quote
Your server sends the order amount and currency. The provider returns a time-bound crypto amount and payment session.
Reviewed 8 September 2026 · Merchant guide
Compare provider-hosted checkout with self-hosted processing, understand payment confirmation and settlement, and choose an integration that your finance and support teams can operate.

Quick answer
A gateway is not simply a wallet address. It connects an order to a quoted amount, supported asset and network, payment destination, expiry time, blockchain or provider status, merchant ledger and refund process. The most suitable provider is the one that supports your legal entity, customers, desired settlement and technical workflow.
How crypto payment gateways work
Your server sends the order amount and currency. The provider returns a time-bound crypto amount and payment session.
The customer selects the supported asset and correct network, then authorises a transfer from a compatible wallet.
The transfer is broadcast. Status may move through detected, pending and confirmed states depending on the network and provider.
A signed webhook tells your backend about the event. Your server verifies the signature and retrieves the authoritative payment status.
Only the agreed confirmed or complete status should release inventory, access, booking or service fulfilment.
The value reaches a provider merchant balance, eligible bank account, custodial wallet or merchant-controlled wallet according to the selected model.
Where does the money reach?
The processor receives the crypto, applies its conversion and settlement rules, and credits an eligible fiat balance or bank payout.
The provider credits crypto or stablecoins to the merchant’s account. The provider controls custody until withdrawal or transfer.
A non-custodial setup sends funds to a wallet controlled by the merchant. This increases control and the merchant’s security responsibility.
Gateway shortlist
This is a use-case comparison, not a security certification or permanent ranking. Features, availability and pricing change; verify the linked official documentation and complete merchant onboarding before development.
| Provider | Useful starting fit | Checkout model | Where funds reach | Important note |
|---|---|---|---|---|
| Coinbase | Platforms and businesses using Coinbase checkout or stablecoin payment APIs | Hosted or API-led | Coinbase Business/custodial account, USDC or supported fiat flow depending on product and eligibility | Product access and settlement options vary by business type and market. |
| Stripe stablecoin payments | Eligible Stripe businesses wanting crypto alongside an existing Stripe checkout | Stripe-hosted or Stripe UI | Completed supported stablecoin payments settle to the merchant’s Stripe balance in USD | Stripe currently documents merchant availability restrictions; verify your country and account. |
| BitPay | Merchants wanting provider-managed invoices and configurable settlement | Hosted invoice, plugins or API | Configured bank account, crypto wallet or an eligible combination | Merchant approval, settlement currency and supported assets depend on account settings. |
| BTCPay Server | Teams able to operate self-hosted, non-custodial Bitcoin infrastructure | Self-hosted invoices and integrations | Directly to wallets controlled by the merchant | The merchant owns hosting, node/wallet configuration, security, monitoring and recovery. |
Selection checklist
Confirm supported business country, customer locations, prohibited activities, KYB/KYC and compliance obligations.
Keep API secrets server-side, verify webhook signatures, use idempotency and retrieve authoritative status before fulfilment.
Display the exact token, contract and network. A correct asset sent on the wrong network may be unrecoverable.
Design expired quotes, delayed payments, underpayments, overpayments, duplicate events and refund approval before launch.
Confirm where funds arrive, conversion timing, fees, payout schedule, transaction exports and reconciliation ownership.
Assign monitoring, incident response, provider access, wallet backup, key rotation and customer-support responsibility.
Frequently asked questions
There is no universal winner. The right choice depends on merchant eligibility, countries, supported assets and networks, custody preference, fiat or crypto settlement, ecommerce platform, refunds, reporting and operational capability.
With a custodial processor, it normally reaches a provider-controlled payment address and is credited to the merchant account before settlement. With a non-custodial system, it may go directly to a wallet controlled by the merchant.
Some providers offer fiat settlement for eligible merchants and countries. Others settle only in cryptocurrency or directly to a merchant wallet. Verify the exact product and account before integration.
A wallet broadcast is not always final payment evidence. The application should wait for the provider’s authoritative status or the agreed number of blockchain confirmations before fulfilment.
Blockchain transfers are generally not reversed like card chargebacks. A merchant refund is normally a new outbound transaction and must follow the provider’s workflow and internal approval controls.
Need implementation help?