Technology & Integration

Player Account Management (PAM)

Player account management (PAM) is the core iGaming system that holds each player's identity, KYC status, wallet, bonus state and responsible-gambling limits.

What it means

When a regulator asks an operator to prove that a self-excluded player couldn't deposit last Tuesday, the answer comes from one system. Not the games, not the payment gateway, not the CRM. The player account management system, PAM for short, is the record of who the player is, what they hold, what they've been promised and what they're allowed to do. It's the system a gambling licence is really attached to.

An iGaming PAM does four jobs. It holds identity and KYC status. It runs the wallet, meaning every balance, deposit, bet, win and withdrawal. It runs the bonus engine and the wagering ledger behind it. And it enforces responsible-gambling controls: deposit limits, time-outs, self-exclusion. Games plug in through a game aggregator; payments through a PSP or an orchestration layer.

How it works

The PAM is a set of modules around one player record:

Module	What it owns	Talks to
Account and identity	Registration, login, KYC and AML status, document store	KYC vendors, national exclusion registers
Wallet	Real, bonus and locked balances; every transaction; multi-currency ledger	Aggregator wallet callbacks, PSPs
Bonus engine	Offers, eligibility rules, wagering requirements, game weighting, expiry	CRM triggers, game events
Segmentation	Tags by value, risk, market and lifecycle stage	CRM, CDP, VIP tooling
Responsible gambling	Limits, reality checks, cool-offs, exclusion, affordability flags	Regulator registers, front end
Reporting	Regulator returns, GGR and NGR by product and market, audit trail	Data warehouse, finance

The wallet is the part everyone underestimates. With a single-wallet integration, every spin from every studio calls back into the PAM, so a mid-size casino sees a few hundred wallet writes per second at peak. Double-spend protection, idempotent transaction IDs and rollback handling live here, and they're where migrations go wrong.

Bonus state is the second trap. A bonus isn't a number. It's a balance plus a rule set (turnover left, eligible games, max bet, expiry) plus the history of how it got there. Moving that between systems is harder than moving cash.

Why it matters for operators

The PAM is the hardest component to swap, so the choice sets your ceiling for years.

First, lock-in. Every player, balance and compliance record lives there. Switching aggregators is a project. Switching PAM is a platform migration with a regulator watching and a deposit freeze during cut-over.

Second, the modular vs monolith question. A monolithic turnkey bundles PAM, front end, aggregation, bonus and CRM from one vendor. It's fast (weeks, not quarters) and cheap to start. A modular PAM exposes each function over APIs, so you can bring your own front end, bonus engine or CRM. Operators reach for it once they have a product team and want to compete on more than the game list. The honest trade: modular costs more up front and needs engineers on payroll; a monolith is cheaper until the day you want something the vendor doesn't do. Modular PAM systems 2026 goes through who has actually shipped one.

The economics

PAM pricing follows the platform contract. Typical ranges, not vendor quotes:

Model	Typical range	Notes
Revenue share (turnkey incl. PAM)	10-20% of NGR	Often with a monthly minimum of 10-25K EUR
Fixed licence (standalone PAM)	15-50K EUR per month	Scales with markets and active players
Setup and integration	50-250K EUR one-off	Higher for regulated multi-market launches
Per-module add-ons	2-10K EUR per month each	Bonus engine, CRM connectors, affordability checks
Migration project	6-12 months, 200K EUR and up	Wallet and bonus state drive the cost

Revenue share looks cheap at launch and expensive at scale. Operators past roughly 2-3 M EUR of monthly NGR tend to renegotiate toward fixed fees or go modular.

How platforms handle it

Every turnkey vendor has a PAM inside; the question is whether you can get at it. iGamingHub tracks 44 platforms, and only five flag a headless front end, the practical test of whether the PAM is exposed over APIs or welded to the vendor's UI:

EveryMatrix is API-first with a headless front end, revenue share pricing and a 6-15 week launch window. Licences listed include MGA, Denmark, Argentina and Brazil.
GR8 Tech flags headless and API-first too, hybrid pricing, 8-16 weeks to launch and 13 licences including MGA, Gibraltar, the Netherlands, Denmark and Brazil.
Softswiss pairs its PAM with a 40,000-game aggregator and quotes 4-12 weeks; hybrid pricing, licences across MGA, Curacao, ONJN, Kahnawake and Brazil.

For a side-by-side on the two most compared PAMs, see Softswiss vs EveryMatrix. For the selection method itself, how to choose a platform provider.

Common confusions

PAM vs CRM. The CRM sends messages and triggers campaigns. The PAM decides whether the player is eligible for the promised bonus, and books it. The CRM reads from the PAM; it doesn't own player state.

PAM vs wallet. The wallet is one module of the PAM. A standalone wallet service without KYC, limits and bonus state attached is a ledger, not a player account.

PAM vs CDP. A customer data platform copies events out of the PAM for analytics and segmentation. It's downstream and can be rebuilt. The PAM can't.

PAM vs platform. People say "platform" for the whole turnkey stack. The PAM is its core, the piece you keep when you swap games, payments or the front end.