What is PAM
PAM is the module within the operator platform that owns everything about a customer account. The scope includes registration data, KYC and AML status, current balance and bonus balance, transaction history, session state, deposit and loss limits, self-exclusion flags, jurisdictional eligibility, and links to CRM segmentation. Every other system in the operator stack reads from or writes to the PAM.
The PAM is also the operational interface for customer-service teams: account adjustments, manual KYC overrides, limit increases, and account closure all flow through PAM workflows.
Core PAM functions
The standard PAM function set covers: registration and identity management; KYC and AML orchestration with third-party vendors; wallet operations including deposit, withdrawal, and bet-settlement adjustments; bonus balance management in coordination with the bonus engine; limit enforcement for responsible-gambling controls; session and login management; and audit logging for regulatory reporting. Modern PAMs expose every function through documented APIs so that downstream systems can integrate cleanly.
Why PAM matters in B2B
The PAM is the operator’s source of truth for customer accounts. Replacing it is one of the most invasive technology projects an operator can undertake, since every other module depends on PAM data. Vendor selection at the PAM layer typically dominates platform procurement. Gamblers Connect lists PAM vendors and full platform suppliers across the iHub directory. Reliability, regulatory coverage, and integration ergonomics are the dominant procurement criteria.
Frequently asked questions about What Is PAM (Player Account Management)?
No. PAM is the system of record for the customer account. The CRM is the system that designs and orchestrates customer communications. The two integrate closely, with the CRM consuming PAM data to drive segmentation and campaigns.
Some PAMs bundle a basic bonus engine; others integrate with a dedicated bonus engine module. The split depends on the vendor architecture.
Deposit limits, loss limits, time limits, self-exclusion, and reality-check enforcement are typically implemented at the PAM layer because that is the single chokepoint through which every customer action passes.