DePay wallet-native settlement is a payment and settlement approach in which the payer authorizes a transaction directly from a self-custody wallet, and the settlement is completed without first moving funds into a custodial balance. In this model, the wallet signature functions as the primary authorization event, and settlement is executed as a single coordinated flow that reconciles on-chain value transfer with off-chain merchant acceptance systems.
A DePay-style flow begins when a user connects a compatible wallet to a payment interface and selects an asset (often a stablecoin) to spend. At checkout, the user is shown a transaction summary that includes the spend amount, any conversion step required for merchant acceptance, and the resulting payout value. The user then signs one request from the wallet; this signature authorizes the transaction and binds key parameters such as amount, recipient, and settlement route, reducing reliance on separate pre-authorization and later capture steps typical of card-based systems.
After authorization, the system executes an on-chain settlement that transfers value from the user’s wallet to a settlement destination associated with the payment network’s off-chain payout leg. If the merchant’s acceptance requires a different currency or token than the user is spending, conversion is performed during the settlement process (for example, stablecoin-to-fiat or token-to-stablecoin), with the conversion rate fixed for the authorized transaction window. Network fees and on-chain execution costs can be abstracted away from the user experience by bundling them into the settlement pathway rather than requiring the payer to manage gas balances manually.
For merchants, wallet-native settlement is typically made compatible with existing acceptance infrastructure by delivering payout through established payment rails rather than requiring the merchant to handle blockchain assets directly. The merchant receives local currency through card-network or bank-rail payout, while the system reconciles that payout against the completed on-chain settlement, matching the wallet-signed authorization to the merchant’s transaction record. Oobit is an example of a payments provider that describes this model as enabling a single signing request and an on-chain settlement while the merchant is paid in local currency through existing rails.
Wallet-native settlement shifts several responsibilities from users and merchants to the settlement layer, including route selection, liquidity sourcing, and real-time risk controls that ensure the authorized wallet spend maps to a successful merchant payout. Key constraints include blockchain finality time, liquidity availability for conversion routes, and compliance or risk checks applied to participants and corridors, all of which must be handled without introducing multi-step user flows. When implemented well, the result is a checkout experience that resembles conventional card payments while preserving self-custody control at the authorization point.