Player Account Management

A player account management system (PAM) is the system of record in an iGaming operation — it holds player identities, balances, KYC status, segments and responsible-gaming limits, and every other product connects to it. Casino, sportsbook and CRM are consumers of the PAM; the PAM is where the player actually exists.

This is why replacing a PAM is the hardest migration in iGaming, and why the choice matters more than the feature list suggests.

What it holds

Identity and verification — registration, document handling, KYC status and re-verification cycles.

Balances — one balance per player, spanning every vertical, held here rather than duplicated per product.

Segmentation — behavioural and value segments available to every other module, so a segment defined once works in the bonus engine, the CMS and reporting.

Responsible gambling — deposit, loss, session and wager limits, self-exclusion and cooling-off, enforced at the account layer where they cannot be bypassed by a product that forgot to check.

Compliance and audit — a full audit trail of account changes, limit changes and verification events.

Why the responsible gambling point matters

Limits enforced per product will eventually fail. A player who has self-excluded needs to be excluded everywhere, immediately, including in whatever vertical you launch next year. Enforcing that at the account layer is the difference between a control and a control that mostly works.

Regulators increasingly test this specifically.

Frequently asked questions

What is a PAM in iGaming?

PAM stands for player account management: the platform layer that owns player accounts, wallets, KYC, segmentation and regulatory limits. Casino, sportsbook and CRM systems connect to it. It is the system of record for the player.

Is a PAM the same as a casino platform?

No. A casino platform runs the game lobby and content integrations. A PAM owns the player. Some vendors bundle them, which is convenient until you want to change one without the other.

Can I run Pixup Play’s PAM with my existing casino?

Yes. The PAM runs standalone and exposes an API that other products connect to, including platforms you already operate.

What does migrating a PAM involve?

Moving player records, balances, KYC status and limit history without interrupting play or losing audit continuity. It is the most demanding migration in iGaming, which is why it is worth scoping properly rather than estimating.

Does the PAM support multiple brands?

Yes. Brands share the platform while keeping separate player pools, or share pools where regulation permits — configuration rather than separate deployments.