iGaming platforms

What a player account management system holds, and what it doesn’t

Fingers touching colourful charts on a tablet display

What a PAM is

A player account management system, or PAM, is the core system of an online gambling operation. It is where a player’s account lives: registration, identity checks, the wallet, deposits and withdrawals, limits and self-exclusion status. Games and payments connect to it.

What a PAM typically holds

  • Accounts and identity status, including verification progress
  • Wallet balances and transactions, such as deposits, withdrawals, bets and wins
  • Bonuses, with their state and wagering progress
  • Responsible gambling settings, such as limits and exclusions
  • Account history for support and audit

What a PAM usually leaves out

  • Detail from game providers, beyond what is passed through
  • Payment provider performance, such as success rates by provider
  • Marketing and CRM context, such as campaigns and consent
  • A joined view across brands and other systems
  • Reconciled, agreed KPIs that match finance

This is why reporting from a PAM alone gets strained once an operator has several providers, several brands or more than one PAM.

Why the gap matters

Two teams can pull a number from the PAM and from a payment provider and find that they differ for good reasons: timing, fees, failed attempts. Without a layer that joins and reconciles them, those differences become arguments. See Data reconciliation for iGaming.

When you change PAM

A PAM migration is one of the riskiest moves an operator makes. What to plan for:

  1. History. Decide how much account and transaction history moves, and where the rest is kept.
  2. Balances. Every balance and total must reconcile before and after the cut-over.
  3. Limits and exclusions. These must carry over exactly.
  4. Running both. Keeping the old and new PAM side by side in one model lets you compare daily.
  5. Reports. Regulatory and finance reports must produce the same figures on the new system.

Our guide to a data warehouse migration strategy and project plan covers the stages, and the migration page explains how we approach it.

How Dejta+ helps

Dejta+ can hold old and new PAM data side by side in one model, with totals reconciled to source and raw history kept. Our team has led PAM and data platform migrations, and we offer that experience on request, priced separately. Read more about our team.

Common questions

Can we report from the PAM alone?

For simple operational views, yes. For anything that joins payments, game providers, marketing and several brands, a PAM on its own falls short, because each of those lives in another system.

Do you migrate PAMs?

Our team has led PAM and data platform migrations. We offer that experience as a service, on request and priced separately from the platform packages.

Talk to us about your data.

Tell us what you run today and what you want to change. We’ll reply within two working days.

Book a demo

  • We’ll reply within two working days.
  • Start with a pilot: the fee is credited against your first invoice if you continue, and your first month is free.

We’ll use these details only to reply to your request, and keep them for seven days.