Where merchant funds arrive

Settlement depends on the gateway model you select.

The checkout screen does not determine who holds the money. Provider custody, conversion and settlement settings do. We document the destination before implementation.

Fiat settlement

An eligible processor receives the crypto and credits a provider balance or sends a bank payout under its settlement schedule.

Custodial crypto balance

The provider credits cryptocurrency or stablecoins to the merchant account for later withdrawal, transfer or conversion.

Merchant wallet

A non-custodial setup sends payment to a merchant-controlled wallet, transferring wallet security and recovery responsibility to the merchant.

Compare gateway and settlement models

Server-side control

Do not fulfil an order because the browser returned to a success page.

A customer redirect can be closed, forged or arrive before final confirmation. The backend should verify the signed webhook, retrieve the payment from the provider when appropriate and process repeated events idempotently.

Release ruleFulfil only after your server records the agreed authoritative status.
  1. 01
    Created

    Payment request exists, but no valid transfer has been confirmed.

  2. 02
    Pending

    A transfer was detected and is awaiting the provider’s required status.

  3. 03
    Confirmed or complete

    The agreed fulfilment trigger has been reached.

  4. 04
    Expired or failed

    Keep the order unpaid and issue a new request when needed.

  5. 05
    Exception

    Route a wrong amount, duplicate event or refund to a controlled review workflow.

Provider research

Compare checkout models and settlement destinations first.

Our updated guide explains hosted and self-hosted crypto payment gateways, the complete transaction lifecycle, and whether funds reach a provider balance, eligible bank account or merchant-controlled wallet.

Read the crypto gateway guide