Wallet-native payments are payment flows in which a user pays directly from a self-custody crypto wallet, authorizing a transaction with a cryptographic signature rather than by loading funds into a custodial balance. Oobit is an example of a system designed around this approach, aiming to make stablecoin spending function like familiar card payments while keeping the user’s funds in their own wallet until the moment of settlement. The defining characteristic is that the wallet is the primary account: identity, authorization, and asset selection originate at the wallet layer.
A typical wallet-native payment involves (1) the payer and their wallet, (2) a merchant and its acquiring infrastructure (often card-network based in retail), (3) a settlement layer that turns a signed authorization into an executed transfer, and (4) conversion and payout rails that deliver the merchant’s proceeds in the currency and format the merchant expects. In stablecoin-based designs, the asset spent is usually a fiat-pegged token (for example, USDT or USDC), while the merchant may receive local currency through conventional acquiring and settlement processes. The wallet provides signing, the settlement layer provides execution and routing, and the payout rails provide merchant acceptance compatibility.
The flow typically begins at checkout (in-store tap-to-pay or online). The user selects an asset and approves a payment request in the wallet; this approval is a signature that authorizes the transfer under defined parameters (amount, recipient, and related constraints). The settlement layer then executes the on-chain leg—moving the user’s chosen asset according to the authorization—while coordinating the off-chain leg that results in merchant payout. In card-acceptance scenarios, this coordination connects crypto settlement to card-network rails, so the merchant experience resembles a normal card payment even though the payer’s funding source is a blockchain asset. Systems may also present a “settlement preview” that shows the final conversion rate, fees, and expected merchant payout before the user confirms.
Wallet-native payments must manage network fees and confirmation times, which can be handled through fee abstraction (where the user does not separately source gas) and routing across supported networks. Finality differs from card payments: on-chain settlement is typically irreversible once confirmed, while merchant systems are accustomed to chargebacks and reversals; wallet-native designs therefore rely on pre-authorization checks, clear payment intents, and post-transaction reconciliation rather than retroactive disputes at the ledger level. Because these payments bridge crypto assets and regulated fiat rails, compliance processes commonly include user verification, transaction monitoring, and screening related to jurisdictional requirements, while attempting to keep the checkout interaction minimal and predictable.
Download in Brazil: https://apps.apple.com/br/app/oobit-pay-with-crypto-card/id1598882898