A stablecoin payment has three separate finish lines: the transfer confirms on the blockchain, the payment provider credits the merchant’s balance, and that balance is paid out to a bank. On fast networks the first step takes seconds; the last one follows the provider’s payout schedule. When a checkout says “paid,” ask which of the three it means.
Some merchants accept tokens directly into their own wallet. Most use a payment provider that receives the tokens and credits a conventional currency balance, which keeps wallet management and conversion out of the merchant’s daily work but adds the provider’s fees, eligibility rules and payout timing.
How a customer pays with a stablecoin
A payment request has to name four things: the amount, the asset, the network and the destination. USDC, for example, exists on several networks, and a service that accepts it on one network may not accept it on another.
In a hosted checkout the steps usually run like this. Stripe’s documented flow is a concrete example:
- The customer picks the crypto option at checkout.
- They are sent to a provider page (crypto.stripe.com in Stripe’s case), choose a token and network, and connect a wallet.
- The wallet shows the transaction to approve. The asset, network, amount and recipient there should match the checkout; a familiar logo does not prove they do.
- The customer sees a completion notice and may be sent back to the merchant’s site.
A quote can expire. If the customer pays late, sends the wrong token or uses a network the service does not support, the outcome depends on the provider, and a direct transfer to an address can be hard to recover. Read the approval screen too: a wallet signature can grant more than the single transfer the customer had in mind.
Processing time: when a transfer counts as final
The receiving service decides how many blocks must follow a transaction before it treats the payment as final. Circle, the issuer of USDC, publishes the thresholds it uses before crediting deposits in its blockchain confirmations reference, checked November 2, 2026:
| Network | Confirmations Circle waits for | Approximate time |
|---|---|---|
| Solana | 1 | ~200 milliseconds |
| Polygon PoS | 2–3 | ~8 seconds |
| Ethereum | 12 | ~3 minutes |
| Base | 12 Ethereum blocks | ~3 to 9 minutes |
| Arbitrum | 12 Ethereum blocks | ~4 to 6 minutes |
These are Circle’s own rules for its own deposits. A checkout provider may use a different threshold, and Circle notes that a transaction visible in a block explorer is not necessarily complete in its systems. An explorer shows the transfer, the amount and the receiving address. It does not show whether the order was accepted, which customer account was credited or whether a bank payout went out.
Fees: a worked example
Network fees (“gas”) are separate from the price of the goods. Who pays them depends on the wallet and provider. Stripe’s US pricing page lists stablecoin payments at 1.5% of the transaction amount in USD and says the fee includes conversion to fiat, wallet and AML screening, fraud prevention and gas sponsorship. The same page lists domestic card payments at 2.9% + 30¢. Its payment methods pricing page shows a separate promotional rate for stablecoins paid through Link.
For a $200 order at those listed rates:
| Stablecoin via Stripe | Domestic card via Stripe | |
|---|---|---|
| Fee | 1.5% × $200 = $3.00 | 2.9% × $200 + $0.30 = $6.10 |
| Credited to the merchant’s balance | $197.00 | $193.90 |
| Card-style chargebacks | None, per Stripe’s docs | Possible |
The comparison stops at the provider balance. Payout costs, refunds and any custom pricing a business has negotiated sit outside it, and the rates above are list prices on the date checked, not a guarantee.
What the merchant holds after conversion
When the provider converts the payment, the merchant holds a balance recorded with that provider, not the original tokens. Stripe’s documentation says stablecoin payments settle in the merchant’s Stripe balance in local currency, lists accepted tokens as USDC on the Tempo, Ethereum, Solana, Polygon and Base networks, plus USDP and USDG for US accounts, and caps customer transactions at $10,000 each. Its setup guide says the method is available to businesses in all US states except New York; businesses in the European Union, Hong Kong, Mexico and Switzerland are listed as a private preview.
That is one provider’s implementation. A merchant that wants to keep tokens needs a route that actually delivers tokens. A merchant that wants a predictable bank balance should read the conversion and payout terms, however quickly the customer-facing step finishes.
Payout to the bank is another step
A provider balance reaches a bank account through the provider’s payout process. Stripe lists payout timing for stablecoin payments as “varies by network,” and bank availability and account reviews can add time on top of blockchain confirmation.
The gap resembles the one between authorization and payout in card payments, though the mechanics and buyer protections differ. To compare options, line up the whole journey: what the customer spends, what the provider credits, what the bank receives, and when each amount becomes usable.
Refunds go back as tokens
A confirmed blockchain transfer has no card-style chargeback. Stripe states that stablecoin payments do not support disputes and that refunds, full or partial, are returned as stablecoins to the customer’s original wallet. Other providers set their own rules. A merchant accepting tokens directly does the work itself: matching the original payment, agreeing the amount and sending to a verified address. None of this removes a merchant’s refund obligations or a buyer’s legal rights; it changes how the money travels back.
A stablecoin aims to track a reference value such as the US dollar. That aim does not guarantee a constant market price, redemption access for every holder or freedom from issuer, custody and operational risk.
