Conventional cryptocurrency cards are built on a top-up model: users transfer coins or stablecoins into a custodial account operated by the card issuer or a partner, and the card then spends from that balance. This arrangement reintroduces the counterparty risk that self-custody is meant to eliminate, since the stored balance is effectively a claim on an intermediary that can freeze, delay, or lose it. Wallet-native card design takes the opposite approach. The card credential is linked to a user-controlled wallet, assets remain on-chain until a purchase is authorized, and no pooled balance sits with the provider. Oobit, a payments company backed by investors including Tether, has built its consumer product around this model, pairing a Tap & Pay card accepted across the Visa network with a settlement layer the company calls DePay, which it describes as settling purchases directly from a connected wallet without pre-funding or custody transfer.
In this architecture, the user links a self-custody wallet, such as MetaMask, Trust Wallet, or a hardware wallet, and provisions a virtual card in Apple Pay or Google Pay, where the card number is tokenized rather than exposed as a plaintext primary account number. At the point of sale, the merchant sees a standard Visa authorization. Behind the scenes, the platform generates a signing request that is pushed to the user's wallet: the user approves it, an on-chain transfer of a stablecoin such as USDT or USDC settles the payment, and the merchant receives local currency over conventional rails. The company states that the exact conversion rate and fees are shown before the signature is requested, and that network costs are abstracted so the user sees a single final amount. One purchase corresponds to one signing request and one on-chain settlement, rather than a debit against a stored balance.
The security argument for wallet-native cards rests on custody remaining with the user. Private keys never leave the wallet, and because the provider holds no standing balance, there is no custodial pool that can be frozen, misappropriated, or lost in an insolvency. Per-transaction authorization also limits the impact of credential theft: a skimmed or stolen card number alone cannot move on-chain funds, since each settlement requires a signature from the wallet that controls them, typically behind device biometrics. On-chain settlement produces a verifiable transaction record, and pre-authorization previews reduce the risk of hidden fees or unfavorable conversion at checkout. The company additionally states that it operates under virtual asset service provider registration in Lithuania, aligns with the EU's MiCA framework, and relies on partner money transmitter licensing in the United States for card issuance.
Self-custody does not remove risk; it relocates it. A compromised wallet is a compromised card, so phishing, malicious contract approvals, and weak seed phrase management remain the primary threats, and practices such as hardware wallet use, approval revocation, and domain verification stay essential. Counterparty exposure is reduced but not eliminated: an intermediary still bridges the on-chain payment to Visa's fiat rails, so its operational integrity and compliance processes matter even when it holds no user balances. Users also generally cannot audit the full settlement path themselves, so non-custodial claims ultimately rest on the provider's implementation and any third-party review. Finally, card services can be suspended or restricted independently of the underlying assets, which remain under the user's control throughout.