A $4.50 coffee and a $200 hotel hold, followed from tap to merchant payout: authorization, clearing, T+1 settlement, and how USDC becomes fiat at checkout.
A stablecoin card transaction runs in four steps: authorization at checkout, which takes seconds; clearing, when the merchant confirms the final amount; settlement between the network and the issuer, usually the next business day; and payout to the merchant in local currency. The stablecoin is checked and reserved at authorization and converted to fiat by settlement.
The four steps are the same as any card. What changes is where the money behind the card sits, and when it turns from USDC or USDT into dollars, euros, or reais.
This guide follows two real-world purchases end to end: a $4.50 coffee that settles cleanly, and a $200 hotel hold where the final bill comes in higher. If you need the basics first, start with what a stablecoin-backed card is. For the issuing side of the business, see what stablecoin card issuing is.
Key takeaways
Each step has one job and one owner. Authorization asks "can this card pay?", clearing fixes the final number, settlement moves money between institutions, and payout pays the merchant.
A few definitions used below:
| Step | When | Who acts | What happens to the stablecoin |
|---|---|---|---|
| Authorization | Seconds, at checkout | Issuer processor and program | Balance checked, amount converted at current rate, hold placed |
| Clearing | Usually same day (T+0) | Merchant and acquirer submit final amount | Hold adjusted up or down to the final amount |
| Settlement | Usually next business day (T+1) | Card network and issuer | Program converts to fiat, or settles in USDC where supported |
| Merchant payout | Acquirer's normal schedule | Acquirer | None; merchant receives local currency |
A $4.50 coffee settles exactly like a normal debit purchase, with one extra conversion step. The amount at authorization and at clearing is the same, so the hold simply turns into a final debit.
For a USD card spending USDC, the conversion is close to one to one. The cost shows up in the program's spread and fees, not in currency risk.
A hotel authorizes an estimate, then charges a different final amount. The program has to adjust the hold at clearing, and it needs enough stablecoin balance to cover any increase.
If the final bill is lower, say $180, the program releases the unused $20 of the hold back to the balance. Fuel pumps and restaurants with tips follow the same pattern with smaller numbers.
| Purchase | Authorized | Final | Hold change at clearing |
|---|---|---|---|
| Coffee | $4.50 | $4.50 | None |
| Hotel, higher bill | $200.00 | $236.40 | +$36.40 reserved |
| Hotel, lower bill | $200.00 | $180.00 | $20.00 released |
| Restaurant with tip | $50.00 | $58.00 | +$8.00 reserved |
These numbers are illustrative.
Custodial programs check an internal ledger. Self-custodial programs check a balance and an allowance onchain. Both have to answer inside the few seconds a card authorization allows.
Ledger check. In a custodial program, the provider holds the stablecoins in its own wallets and keeps a ledger of what each cardholder owns. The authorization reads that ledger and writes a hold. It is fast and simple, and the cardholder trusts the provider with the funds.
Onchain check. In a self-custodial program, the stablecoins stay in a wallet the cardholder controls. Gnosis Pay, for example, gives each user a Safe smart account with a spending allowance enforced by a Roles Module, per its documentation. The card can spend up to that allowance. A Delay Module adds a 3-minute hold on non-card transactions out of the account.
neobankbeat's stablecoin cards explainer puts the trade-off simply: the wallet may be permissionless, but the card rails still require the cardholder to be identified.
At checkout the stablecoin is reserved, not yet sold. The conversion that pays for the purchase usually happens at settlement, when the program funds what it owes the network.
There are two models for that funding step today.
Model 1: convert, then settle in fiat. The program sells stablecoins for fiat through a liquidity partner and pays the network over bank rails, like any other issuer. Most programs work this way.
Model 2: settle with the network in a stablecoin. The issuer pays Visa directly in USDC, and Visa handles the conversion on its side. Visa announced on December 16, 2025 that US issuer and acquirer partners could settle in USDC, with Cross River Bank and Lead Bank as initial participants settling over Solana. On April 29, 2026, Visa said the pilot supported nine blockchains and had reached a $7 billion annualized settlement run rate, up 50% from the previous quarter.
That $7 billion is settlement activity between institutions. It is a different measure from card spending and should never be added to card volume.
No. The card network timeline is identical. The difference sits inside the program: when it converts, what rate it uses, and how much liquidity it keeps ready.
| Moment | Bank debit card | Stablecoin card |
|---|---|---|
| Checkout | Bank checks deposit balance | Program checks stablecoin balance and converts at current rate |
| Same day | Clearing, hold adjusted | Clearing, stablecoin hold adjusted |
| T+1 | Bank settles with network in fiat | Program converts stablecoins and settles in fiat, or settles in USDC |
| Merchant payout | Local currency | Local currency |
A stablecoin card program needs fiat ready every settlement day and a reliable rate every time it converts. That makes conversion and payout liquidity part of the card's daily operations.
Three operational questions decide whether a program runs smoothly:
BlindPay is a stablecoin API for global payments that covers those money movements around the card. Its payout quotes lock the rate and fees before the stablecoins move, and payouts convert USDC or USDT into local currency over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO/COBO), with no pre-funding. How live quotes work for on- and off-ramp liquidity explains why a locked quote matters when rates move between authorization and settlement.
Most problems come from the gap between the authorized amount and the final one, or from the balance changing during that gap. Programs design their hold rules around these cases.
For card payments, chargebacks follow card network rules. Onchain stablecoin transfers have no chargeback at all, which are stablecoin payments reversible covers in detail.
Treat the card network timeline as fixed and design the stablecoin side around it. Your program's real work is the hold logic, the conversion rate, and having settlement cash ready every business day.
If you run a card program or wallet and need the conversion and local payout legs handled through one API, start with the free development instance in the BlindPay payout quickstart.
Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24/7 treasury, bill pay, and PSP payouts.
AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.
The three roles behind every card program, stablecoin cards included: what each one does, who carries liability, and what to ask a provider.