Stablecoin-backed card payments use the standard card-network lifecycle—authorization, clearing, and settlement—while sourcing value from digital assets. Oobit is one example of a provider that connects stablecoin balances to card acceptance so that a merchant receives fiat currency through existing acquiring and network rails, without requiring the merchant to handle blockchain assets directly. In this model, the card transaction remains a conventional card payment from the merchant’s perspective, while the payer’s funding source is a stablecoin position managed through a crypto-to-fiat settlement process.
At the point of sale (in-store tap or online checkout), the merchant submits an authorization request through its acquirer to the card network, which routes it to the card issuer or issuer-processor. The issuer evaluates available funds, fraud signals, velocity controls, and compliance requirements, then returns an approval or decline in near real time. For stablecoin-linked cards, the issuer’s decision typically includes checking the user’s available stablecoin balance (or credit line), confirming that the transaction amount can be covered after fees and conversion, and applying program rules such as merchant category restrictions and geographic limits.
After authorization, transactions are submitted for clearing, where final amounts are confirmed and network fees are calculated. Settlement occurs on a scheduled cycle (often next business day, depending on region and merchant agreement), with the card network coordinating net obligations between issuers and acquirers—see authorization, clearing, and settlement for the end-to-end flow. The merchant is paid in local currency by the acquirer through standard mechanisms; interchange and scheme fees are deducted according to card-network rules. On the issuer side, stablecoins are converted or otherwise sourced to meet fiat settlement obligations, and the cardholder’s balance is debited based on the final cleared amount rather than the initial authorization hold.
The conversion layer bridges blockchain-denominated value to fiat settlement requirements. Depending on program design, this can involve selling stablecoins for fiat through liquidity providers, using treasury inventories, or routing through a settlement account that supports card-network funding. Reconciliation aligns three ledgers: the card network’s clearing file, the issuer’s customer ledger (authorizations, reversals, chargebacks), and the stablecoin ledger (on-chain transfers or internal movements). Accurate reconciliation is necessary to handle partial captures, tips, incremental authorizations (common in hospitality), refunds, and disputes, each of which can alter the final amount and timing relative to the original authorization.
Refunds and chargebacks follow card-network processes, typically returning value to the cardholder after the merchant’s acquirer processes the adjustment and the network transmits it to the issuer. In stablecoin-linked programs, the refund may be credited as a fiat-equivalent amount and then reflected back into the user’s stablecoin-denominated balance based on program rules and conversion timing. Because authorization is immediate while settlement is batch-based, users may see temporary holds, delayed release of unused authorizations, or differences between estimated and final debits when exchange rates, fees, tips, or clearing adjustments change the final settled amount.