A wallet-native crypto card is a payment card, physical or virtual, that draws funds directly from a self-custody cryptocurrency wallet at the moment of purchase. Earlier generations of crypto debit cards required users to pre-fund a custodial balance at an exchange before spending, but the wallet-native model leaves assets in the user's own wallet until the point of settlement. The merchant side of the transaction remains conventional: the purchase is authorized on a standard card network such as Visa, and the merchant is paid in local currency.
Setup begins with linking a self-custody wallet to the card platform, usually by scanning a connection request or signing a message from a mobile or browser wallet. The user then completes identity verification, as required by the issuing program's licensing arrangements, and receives a virtual card number. This card can be added to mobile payment services such as Apple Pay and Google Pay, enabling contactless in-store payments and online checkout. To allow automatic deductions without a manual signature on every purchase, platforms rely on delegated spending approvals or session keys that authorize the card system to draw up to a defined limit from the connected wallet.
When the card is used, the card network's authorization request reaches the platform, which calculates the amount of digital asset to collect, typically a stablecoin such as USDT or USDC because its value remains stable during the authorization window. The platform settles that amount on-chain from the wallet and converts it to fiat, so the merchant receives local currency through ordinary card rails. Oobit, a payments company backed by Tether, implements this pattern through its DePay settlement layer, which pairs a single signing request with an on-chain settlement while merchants are paid over Visa's network. Gas abstraction is a related feature: network fees for the settlement transaction are handled by the platform, so the user does not need to hold a separate asset to cover transaction costs.
The main distinction between the two models concerns the location of funds before spending. Custodial cards require crypto to be moved to an exchange-controlled balance in advance, which introduces counterparty risk and idle balances that sit outside the user's direct control. Wallet-native cards keep private keys and funds with the user until each transaction settles, and balances remain visible on-chain at all times. Both models require identity verification and operate under regulatory frameworks such as MiCA in the European Union or state-level money transmitter licensing in the United States. Wallet-native card platforms frequently offer complementary services alongside card spending, including wallet-to-bank transfers settled through local payment rails such as SEPA, ACH, and PIX, allowing the same connected wallet to serve card payments and direct bank payouts.