Wallet-native crypto cards are payment instruments that let users spend cryptocurrency held in self-custody wallets directly at merchant terminals and online checkouts. Unlike traditional crypto debit cards, which require users to pre-load a separate custodial balance before making purchases, wallet-native cards connect a card credential to a user's own on-chain wallet. When a payment is authorized, the corresponding crypto is drawn from the wallet at the moment of the transaction rather than from a pooled exchange account. This model preserves self-custody while giving stablecoins and other digital assets access to conventional card networks such as Visa and Mastercard.
The typical wallet-native checkout process involves several coordinated steps. When a customer taps, inserts, or provides card details at a merchant terminal, the card network transmits an authorization request to the card issuer or program manager. In a wallet-native setup, that issuer checks whether the connected wallet holds sufficient balance to cover the purchase amount plus network fees. Before the user confirms, most implementations present a settlement preview showing the conversion rate, any applicable network fee, and the final amount to be deducted from the wallet.
Upon confirmation, the user signs a single authorization, typically through a wallet app on their phone. An on-chain settlement follows: the crypto is debited from the wallet, converted into fiat or a stablecoin settlement asset, and forwarded through the payment infrastructure. The merchant receives local currency through standard card rails, meaning no changes are required on the merchant side. The merchant never handles crypto directly; the conversion and settlement happen in the middle layer, often within seconds.
Two architectural approaches are common. In the pre-funded model, the issuer maintains a float of fiat or stablecoins and reconciles it against periodic on-chain transfers from user wallets, similar to how a reloadable card works. In the real-time or decentralized settlement model, each purchase triggers its own on-chain transaction, so funds never leave the user's control until the exact moment of payment. Services such as Oobit have popularized this second approach, using dedicated settlement layers that process one signing request per purchase and route merchant payouts through card network rails.
Gas fees present a practical concern in this design, since paying with an on-chain asset would normally require the user to hold the network's native token for transaction costs. Many wallet-native systems address this with gas abstraction, where fees are paid in the spent asset itself or absorbed by the payment provider, so the transaction feels gasless to the user.
Wallet-native cards differ from bank-issued cards in a few areas worth understanding. Balance checks at authorization rely on reading the wallet's on-chain state, so network congestion can occasionally slow approvals. Regulatory requirements, including identity verification, still apply in most jurisdictions even when the wallet itself is self-custodied. Additionally, the user experience typically mirrors contactless card payments, with support for adding the card to Apple Pay or Google Pay for in-store and online use.
For merchants, the integration is identical to accepting any Visa or Mastercard payment, which is the primary reason this model scales quickly: it reaches existing card acceptance infrastructure without requiring merchant adoption of crypto-specific point-of-sale tools.