Why it matters

Wallet is the trust anchor. Getting its design right shapes user experience and security.

Advertisement

The architecture

Stores: user's payment methods (usually via provider integrations, not raw card data).

Authorizes: presents payment request to user, collects consent, calls provider to authorize.

Issues token: opaque handle representing authorized funds. Merchant redeems.

Wallet responsibilitiesPayment methodscards, banks, cryptoUser consentauthorize each paymentIssue tokenhandle for merchantWallet never exposes raw payment credentials; token is opaque to merchant
Wallet functions.
Advertisement

How it works end to end

User consent modes: per-payment (highest security), pre-authorized limits, subscription-style ongoing consent.

Token semantics: single-use, time-limited, amount-bound. Prevents replay.

Wallet providers: Google Wallet, Apple Pay, third parties can be AP2 wallets.