Consumer Wallet

Overview

Consumer wallets prioritize everyday usability through mobile, web, browser, or hardware interfaces. They may support payment cards, bank value, crypto assets, tokens, identity credentials, or several categories together. Custody can remain with the user or be delegated to a provider.

Features such as simple recovery, contact-based transfers, transaction previews, biometric access, and fee abstraction can make complex systems easier to use. They can also obscure important distinctions between confirmed and pending funds, asset ownership, network choice, and who can recover or freeze an account.

Evaluation should cover supported value types, key control, backup and recovery, fees, privacy, transaction limits, interoperability, and provider exit. Users should keep high-value reserves separate when the wallet is routinely connected to websites or used on a general-purpose device.

Material risks for Consumer Wallet include credential compromise, malicious destinations, unsupported assets, wrong-network transfers, stale balances, compromised software, provider outage, privacy leakage, and inaccessible recovery material. For Consumer Wallet, controls should reflect value, automation, reversibility, and whether the organization or a third party controls signing.

Records for Consumer Wallet should preserve account and address identifiers, asset and network identity, policy version, requester, approvers, signed payload or transaction reference, fees, timestamps, status history, confirmations, exceptions, and final balance and accounting effects. For Consumer Wallet, corrections must remain linked rather than overwrite the original event.

Production ownership for Consumer Wallet should identify the user or legal entity, supported assets and networks, address model, custody boundary, signing authority, recovery method, and systems permitted to request or observe transactions. For Consumer Wallet, these fields determine who can act and which evidence is authoritative.