A wallet balance is a projection of underlying movements. If those movements cannot be reconciled with provider events and account records, the precision of the number on screen offers little operational assurance.
Executive summary
A Player Account Management (PAM) workflow should distinguish payment attempts, provider transactions, ledger postings and the balance presented to an operator. These are related records, not interchangeable counters. Reliable reconciliation requires stable identifiers, controlled state transitions and explicit treatment of delayed or repeated events.
The reference approach below focuses on engineering checks and operational ownership. It does not assert that the Bounty PAM+ demonstration proves a particular ledger architecture. Use the existing back-office screens as a starting point for evaluating how much underlying evidence a deployment exposes.
1. Define the transaction and state boundaries
Preserve attempts without counting them as money
In the existing illustrative player-service example, three unsuccessful e-wallet attempts precede one successful RON 10,000 card payment. The successful deposited amount is RON 10,000. Summing attempted amounts would report RON 40,000 and create a false operational conclusion.
Identify which record represents an attempt and which represents an accepted financial movement. Keep the provider transaction reference, internal account reference and event identifier distinct. A retry may concern the same transaction without creating a new economic event.
- Define legal state transitions and who can initiate each transition.
- Separate pending authorisation, completed settlement and reversal where applicable.
- Preserve original currency and the rate used for reporting conversion.
- Record event time, receipt time and processing time independently.
Reconcile each balance component
For a defined ledger, opening balance plus signed movements should equal closing balance. Apply that identity to the correct currency and balance type. Cash, restricted funds and promotional balances may have different movement rules. Do not merge them into one total and expect the result to explain every account state.
When provider settlement timing differs from ledger posting, record the reconciling item and its age. A timing difference is not automatically an error, but it should not remain an unexplained residual indefinitely.