Concepts
Wallet & Merchant Isolation
Overview
Each member has one wallet per tenant. Wallet balances are isolated between tenants.
A member enrolled under multiple partners has separate balances for each partner.
Isolation Examples
| Scenario | Behavior |
|---|---|
| Member enrolled at Partner A and B | Two independent wallets |
| Member earns cashback at Partner A | Only Partner A wallet increases |
| Member redeems voucher at Partner B | Only Partner B wallet is affected |
| Wallet becomes negative after cancellation | Only that tenant wallet is impacted |
Access Control
Cross-tenant wallet access is not allowed and returns 403 Forbidden.
For balance retrieval routes and payloads, use the API Reference.
Key Points
- Wallet isolation is enforced by API key tenant scope
personalCodeuniqueness is tenant-scoped, not global- Wallet tracks
balanceandtotalReservedindependently
See Also
- Consumer Identity: Personal codes and balance fields
- Loyalty Program: Points and cashback behavior
- Vouchers: Reserved balance mechanics
Last modified on