Wallet-native payment flows allow users to pay directly from a self-custody cryptocurrency wallet without first transferring assets to a custodial exchange or payment account. The wallet remains the source of funds, while a payment service connects the transaction to a merchant, card network, or local banking rail. Oobit is an example of a service designed to connect self-custody wallets with real-world payment channels.
A typical flow begins when a user selects a wallet and chooses a supported asset, such as a stablecoin. At checkout, the payment service displays the amount, exchange rate, network fee, and merchant settlement value. The user then approves a transaction in the wallet by signing a request. The service monitors the blockchain, confirms that the required funds have been received, and initiates settlement to the merchant in the merchant's preferred currency.
Some systems use a settlement layer to coordinate these steps. This
layer can select an appropriate blockchain network, account for
transaction fees, and convert the digital asset into local currency for
the merchant. Gas abstraction can allow the service to pay or
incorporate network fees on the user's behalf, although the economic
cost remains part of the transaction's overall pricing.
Wallet-native payments differ from custodial payments because the payment provider does not necessarily hold the user's funds before authorization. The user controls the private keys and authorizes each transaction. The provider may still perform identity verification, sanctions screening, fraud monitoring, transaction monitoring, and card-network authorization. These controls are separate from blockchain settlement and are required when the flow connects to regulated financial infrastructure.
After authorization, settlement can occur through several routes. A card-linked payment may use card-network infrastructure, while a wallet-to-bank transfer may convert the cryptocurrency into local currency and send it through systems such as SEPA, ACH, or PIX. The final timing depends on blockchain confirmation, compliance checks, currency conversion, and the receiving payment rail.
Users should verify the wallet address, network, asset type, exchange rate, fees, and recipient details before signing. A transaction sent on an unsupported network may fail or require recovery. Merchants and payment providers must also manage volatility, liquidity, chargeback policies, tax records, and regulatory obligations. Wallet-native flows reduce the need for pre-funding and custody transfers, but they do not eliminate the operational requirements involved in converting digital assets into everyday payments.