Digital Wallet
A reference use case for wallet balances, transfers, and merchant settlement flows on Parix.
Digital wallets are a strong match when your bottleneck is concurrent balance movement rather than simple CRUD storage.
The common failure mode is a Postgres-backed wallet stack that accumulates row locks, retry logic, and dedup systems as active wallet counts grow.
Where this pattern fits
Use this shape when you need to:
- keep customer and merchant balances consistent under high write concurrency
- process top-ups, peer transfers, withdrawals, and settlement movements atomically
- prevent double-spend behavior without building your own ledger infrastructure
- keep a clear history of value movement for support and reconciliation
Typical flow
- Model each wallet, reserve account, and settlement account as TigerBeetle-backed entities.
- Post balance-changing operations through a gateway-controlled write path.
- Expose read models in your product UI for balances, history, and operational investigation.
- Use the platform's backups, logs, and metrics surfaces to operate the system.
Why Parix fits
The current product is already shaped around managed ledger infrastructure:
- gateway-only access to TigerBeetle operations
- provider-hosted clusters on AWS and GCP
- operator surfaces for configuration, backups, logs, and metrics
That lets a wallet product focus on user and merchant workflows instead of running the ledger stack itself.
Product signal already present in the repo
The marketing site already calls out the wallet pattern directly: teams that outgrow Postgres-ledger designs hit hot-account contention, while TigerBeetle removes the queueing ceiling for transfer-heavy workloads.