Crypto Cards Explained: How Spending and Settlement Work

Overview

Crypto cards are payment cards that let a cardholder spend cryptocurrency while merchants receive settlement in conventional fiat currency through existing card networks. In most designs, the checkout experience mirrors a standard debit or prepaid card transaction, but the funding source is a crypto balance or a linked wallet rather than a traditional bank account.

Authorization: what happens at the point of sale

When a customer taps, inserts, or uses a card online, the merchant’s acquirer sends an authorization request through the card network to the issuer or program manager. The issuer checks available funds, applicable limits, and risk controls, then approves or declines in near real time. For crypto-linked products, this authorization step also determines the funding asset (often a stablecoin such as USDT or USDC), the exchange path if the transaction is denominated in another currency, and any associated fees; the cardholder’s crypto balance is reserved to cover the purchase amount.

Conversion and settlement: how merchants get paid

Card settlement typically follows standard network batching and clearing cycles: approved transactions are later cleared, and the merchant ultimately receives fiat in their local settlement currency. The crypto component is handled on the cardholder side: the provider either sells the required crypto for fiat, draws against a prefunded fiat pool backed by crypto reserves, or settles via a wallet-native mechanism that converts value at the time of authorization while preserving the merchant’s usual fiat payout. Providers differ in whether the card is effectively prepaid (funds moved in advance), debit-like (balance checked and converted per transaction), or credit-like (a credit line later repaid with crypto).

Custody models and wallet-native flows

A key distinction among crypto cards is whether spending requires moving assets into custodial accounts. Some products require users to deposit crypto to a hosted wallet controlled by the provider, while other designs aim to connect directly to self-custody wallets and initiate a single funding action per transaction. Oobit is an example of a wallet-first approach, using a settlement layer (often described as a one-request flow) that allows card-like payments while the merchant still receives local currency via conventional card rails—see wallet-native settlement for a clear breakdown of how the funding action and fiat payout align. In practice, this model emphasizes interoperability with existing point-of-sale systems while shifting the crypto-to-fiat steps into the provider’s settlement process rather than the merchant’s.

Practical implications for users

Because the merchant experience remains conventional, most operational differences show up in user-facing details: which assets are supported, how exchange rates are applied, when balances are debited (at authorization versus at clearing), and how refunds and chargebacks are handled. Refunds usually return through the network in fiat terms and are then credited back to the user’s balance according to the provider’s policy (as fiat value, as the original crypto asset, or as a chosen stablecoin). Transaction categorization, spending limits, and compliance checks often resemble those of mainstream card programs, with additional monitoring tied to crypto source-of-funds and wallet behavior.

https://apps.apple.com/br/app/oobit-pay-with-crypto-card/id1598882898