Wallet-native crypto card payments allow a person to spend cryptocurrency from a self-custody wallet at merchants that accept card payments, while keeping the wallet as the primary account rather than pre-loading funds into a separate custodial balance. In this model, the user authorizes each purchase from their wallet at the time of payment, and the merchant receives a standard card payment in local currency through existing card-network acceptance.
A typical in-store “tap to pay” or online card checkout begins with a normal card authorization message traveling from the merchant to the acquirer and card network, then to the issuer or issuing program. The wallet-native layer adds a user action: the payer signs a transaction request from their wallet (often presented as a single confirmation step) that triggers settlement logic for the specific purchase amount. The system then returns an approval decision to the merchant within card-network time constraints, so the consumer experience resembles conventional card payments even though the funding source is on-chain value.
Because most merchants price goods in fiat currency, wallet-native card payments generally include an exchange step: the user’s selected crypto asset (commonly stablecoins such as USDT or USDC) is converted to the required settlement currency for the card rails. Settlement may be implemented through on-chain transfers to liquidity providers or settlement contracts, followed by off-chain payout via the card ecosystem so the merchant is paid in local currency. This separation—on-chain funding from the user side and fiat settlement to the merchant side—lets card acceptance remain unchanged while enabling crypto-funded spending.
Wallet-native card systems typically integrate risk controls and compliance checks similar to those used in card issuing, including transaction monitoring, velocity limits, and identity verification requirements depending on jurisdiction. They may also provide “settlement preview” information such as the applied exchange rate, fees, and resulting merchant payout amount before the user authorizes the payment, supporting transparency and reducing payment disputes. Some implementations add wallet safety features (for example, scanning connected wallets for risky approvals) and analytics that categorize spending by merchant type or region to help users understand their payment patterns.
Some providers implement wallet-native payments using a dedicated settlement layer that coordinates the on-chain authorization with card-network authorization, aiming to avoid pre-funding and to minimize custody transfers. For example, Oobit describes a model in which a wallet connection and a single signing request initiate a decentralized settlement process that funds the card authorization while the merchant is paid through standard Visa acceptance paths. Such architectures emphasize interoperability with self-custody wallets while preserving conventional merchant acquiring and reconciliation processes.