The important question is what happens when an account changes state. A restriction recorded in one interface has limited value if another channel continues accepting activity from stale information.
Assign an authoritative record
| Account property | Decision to document |
|---|---|
| Identity and verification | Which service records the decision and any later change? |
| Access and restrictions | Which channels must check the current state before allowing an action? |
| Limits and exclusions | How are effective dates and changes applied across products? |
| Consent and preferences | Which system stores the applicable choice and history? |
| Financial balance | Which ledger authorizes and records money movements? |
The PAM may own a property or receive it from another system. Make that boundary explicit, including what happens when the authoritative service is unavailable.
Test a change while a player is active
- Start a session.
- Apply a restriction.
- Attempt a relevant action from another channel.
Check the expected rejection, player message and audit record. Repeat with a delayed update so the team can see how stale information is handled.
Also test duplicate registration, a failed balance update and an authorized correction. The records should identify the account, event, original state, resulting state and decision reason. Agree the required propagation behavior in the scope rather than assuming a particular delay is acceptable.
Choose integration or replacement
Extend the existing account system when it can remain the authoritative source and the missing workflow can be addressed through a defined interface. Consider replacement when the required state model or control cannot be supported reliably by that approach.
A replacement needs mapping for identities, verification evidence, limits, consent and history. Define duplicate resolution and what remains in an accessible archive. Use a migration plan with reconciliation and rollback criteria before scheduling cutover.
Send your current account and wallet architecture. Include the state changes that fail today and the channels that must obey them.