Merchant Wallet

Overview

A merchant wallet can receive customer payments, support unique deposit addresses, hold operating balances, issue refunds, fund payouts, or route assets to treasury. It may be self-custodial, provider-hosted, or integrated through a crypto payment gateway.

Payment receipt and usable settlement are not the same. The wallet must distinguish asset, network, order, confirmation status, available balance, fees, and ownership. Using one address for many orders can complicate attribution, while keeping excessive value in an online wallet increases exposure.

Merchants should define wallet purpose, custody, accepted routes, confirmation policy, refund authority, sweep rules, fee reserves, and reconciliation. Transaction references must connect orders, blockchain activity, provider records, and accounting. Access should follow business roles, with continuity plans for lost signers, provider outages, and key compromise.

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

Records for Merchant 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 Merchant Wallet, corrections must remain linked rather than overwrite the original event.

Merchant Wallet should be distinguished from the asset balance and from the application that displays it. For example, a customer-facing success message does not prove that the intended transaction executed on the correct network; operations should verify execution and reconcile the result before irreversible fulfillment.