Platform
PAM (Player Account Management)
Player Account Management
Definition
The core platform layer holding the player account, balance, transaction history, KYC state, and bonus liabilities. The technical heart of any operator.
Why it matters
The PAM is the most critical and most expensive piece of operator technology. It holds the player's identity and verification state, the wallet balance and transaction history, the bonus liabilities and wagering progress, the responsible gambling controls, the AML risk profile, the loyalty program state, and the linkages to every product the player interacts with. Every deposit, withdrawal, bet, win, bonus, and account event flows through the PAM. The system runs continuously; any outage is total operator outage.
The PAM market is dominated by a handful of major platform providers (Playtech, OpenBet, SBTech now part of DraftKings, GiG, Soft2Bet, Aspire Global, and others) alongside the in-house platforms operated by the largest groups. Switching PAM platforms is a multi-year program because of data migration complexity, integration rework with all suppliers, retraining of operational teams, and risk to player experience during cutover. Platform selection decisions are among the most consequential commercial choices an operator makes, with implications stretching out for 5 to 10 years.
Frequently asked questions
Can operators build their own PAM?
The largest groups do. Mid-sized operators almost always license. The build-or-buy decision turns on scale, ambition for technology differentiation, and engineering capacity. In-house PAMs cost tens of millions to build and tens more to maintain; below scale thresholds, licensed PAM is more efficient.
Why are PAM migrations so difficult?
Multiple reasons. The PAM is integrated with dozens of suppliers (game studios, PSPs, KYC vendors, CRM, BI tools), each of which needs to be re-integrated against the new platform. Player data must migrate without loss. Bonus liabilities, ongoing wagers, and pending withdrawals all need careful handling. Operational teams need retraining on new back-office workflows. The typical migration runs 12 to 24 months for a major operator.