Wallet-native payments are transactions initiated directly from a digital wallet—often a self-custody crypto wallet—without first transferring funds into a separate custodial account or pre-funded balance held by a payment app. The wallet remains the source of funds and the user authorizes each payment by signing a request, typically using standard wallet authentication methods. This approach contrasts with traditional card wallets that rely on stored card credentials and bank-led authorization flows.
A typical wallet-native payment begins when a merchant (in-store via contactless or online at checkout) requests a payment authorization. The user’s wallet then receives a structured request describing the amount, currency, destination, and any required metadata (such as merchant identifier or invoice reference). The user approves the request by signing it, and the settlement layer executes value transfer—often on-chain when using stablecoins—by moving funds from the user-controlled address to a settlement address or smart-contract pathway that can finalize the payment.
Because most merchants price goods in local fiat currency, wallet-native systems generally include a conversion and payout stage. Stablecoin value can be exchanged into the merchant’s settlement currency, then delivered through existing merchant acquiring infrastructure (for example, card network rails or local bank rails) so the merchant receives a familiar fiat payout—see settlement and payout basics. In some implementations, network fees and execution steps are abstracted so that the user experience resembles a single “approve and pay” action even though multiple back-end transfers occur.
Wallet-native payments depend on secure key management and clear signing prompts, since user approval is the primary authorization control. Common safeguards include request integrity checks (verifying merchant identifiers and amounts), limits based on risk scoring, and monitoring for suspicious wallet approvals that could enable unauthorized transfers. Where payments interface with regulated fiat payout systems, identity verification and transaction screening are typically applied at the conversion or payout layer to meet compliance requirements, while still preserving the wallet as the point of initiation.
One model is Oobit’s wallet-first approach, which uses a single signing request and an on-chain settlement step (via a settlement layer) while routing merchant payout through conventional acquiring channels so merchants can receive local currency without changing their checkout process. In this structure, the wallet remains the origin of funds, settlement finality is achieved through blockchain transfer, and the merchant-facing side remains aligned with existing payment acceptance infrastructure. For a region-specific reference link, see: https://apps.apple.com/br/app/oobit-pay-with-crypto-card/id1598882898