Wallet Checkout

Overview

A wallet checkout presents a merchant payment request to a compatible cryptocurrency wallet. The customer may connect through a browser extension, mobile deep link, QR handoff, or wallet-selection component, then reviews and signs the transaction inside the wallet. The checkout coordinates the user experience but should never obtain the customer’s private key or seed phrase.

The server, not the browser, should remain authoritative for the order, quoted amount, accepted asset, network, destination, and expiration. Client-supplied values can be altered. The checkout creates a payment attempt linked to the cart and passes the exact request to the wallet, often through a payment URI, provider SDK, or protocol message.

Wallet approval and blockchain payment are separate events. A customer can reject the request, switch networks, sign a different amount, submit a transaction that later reverts, or close the interface after broadcasting. The merchant therefore calculates or receives the transaction identifier and validates canonical execution through its own nodes or payment provider.

A good crypto checkout shows the merchant, amount, asset, network, fees, destination, and remaining quote time before authorization. It handles unsupported wallets, wrong-network state, stale quotes, rejected signatures, provider timeouts, and return navigation without labeling any of those states as payment success.

Operational records should bind customer session, cart version, payment request, wallet connection, selected route, transaction, order, and final fulfillment decision. Callbacks and redirects are hints, not settlement evidence. Retries must be idempotent so reconnecting a wallet or reopening the checkout does not create a second order or duplicate credit.

Wallet checkout differs from QR checkout by emphasizing an interactive wallet connection or handoff. Both require the same independent payment confirmation controls after authorization.