Turnkeyxgaming

Glossary

PAM is the player account system

PAM, player account management, is the platform that registers players, stores KYC state, applies limits and usually hosts the cashier. Game aggregation plugs into it. It does not replace it.

3 min readUpdated By the Turnkeyxgaming team

The account system and the game catalogue are different purchases

Turnkey and white-label offers sometimes include a PAM. An API-only integration assumes you already have one. The platform page describes that split. Bonuses live next to the PAM too, because they are rules about the account, not about the slot maths.

If a vendor uses PAM to mean 'the whole casino', ask them to list registration, wallet, bonus, reporting and games separately. Those can be bought apart, and this site sells them apart.

Questions that reveal someone is using PAM to mean everything

Ask whether registration, KYC storage, the cashier, the bonus rules and the game catalogue are one contract or four. If the answer is 'the PAM', you do not yet know what you are buying.

Limits and self-exclusion live here, not in the slot. A studio reality-check timer is not a substitute for the account control your licence expects.

One self-exclusion, a second account, four days

A player self-excludes on 12 March from the account page. The platform flags the account and the flag stops the cashier. On 14 March the same person registers again with a different email address and the same surname, date of birth, device and payment instrument.

A platform that matches on email alone creates a second live account with no exclusion attached. A platform that matches on verified identity or device sees the collision and either blocks registration or carries the flag across. The difference is not whether the product has a self-exclusion feature, since both do. It is the key the match runs on.

This is why the account system is bought separately from the game catalogue. The aggregator knows which rounds a player played and what was staked. It does not know that two player ids belong to one person, and should not be asked to infer it from a shared device fingerprint it never sees.

Which system owns which fact

FactOwnerWhat goes wrong when two systems both hold it
Verified identity and date of birthPAMThe wallet keeps an older copy and lets an unverified account claim a welcome offer
Self-exclusion statePAMA studio's timer is mistaken for the account flag and a second brand stays open
Spendable balanceOperator ledgerA PAM copy drifts by cents and the cashier disputes the game
Round historyAggregator, surfaced by the PAMThe player sees two histories with different ids for one spin
Payment instrumentPSP, tokenisedThe PAM stores a card number it should never have held

Where the PAM boundary blurs

  • Registration, cashier, bonus engine and catalogue are bought as one line, and nobody can say which contract launches a game.
  • Limits are enforced in the lobby client and skipped by the wallet callback that arrives without one.
  • A second product, such as sports, arrives with its own player table and no shared exclusion key.
  • Bonus rules are written into the game integration, so a terms change becomes an engineering release.
  • The export of player records, and its format, is agreed after launch when a leaving date is already being discussed.

FAQ

Questions operators ask

Does the casino API include a PAM?

The API integration assumes your platform holds the account. A PAM is part of the turnkey and white-label conversations, scoped separately.

Who owns the player record if we leave?

That is a contract term, not a feature of the word PAM. Agree the export before you launch. The guide on player ownership is the operational version.

Do we need a PAM if we only take the casino API?

Yes, in some form. The API assumes an account already exists: it debits and credits a player the platform has registered, verified and limited. If you do not have a platform, the turnkey and white-label options include one, and that is a different scope and a different contract from the API integration.

Should game history live in the PAM or with the aggregator?

The aggregator holds the rounds it settles, and the player-facing history has to show them with the ids support will search. Whether the PAM copies the records or queries them on demand is an engineering choice. Two unsynchronised copies with different ids is not a choice, it is a dispute waiting for a busy Saturday.

References

Sources and further reading

Primary regulator, standards or studio documentation behind the technical and regulatory points on this page. External links open in a new tab. Links checked 2026-11-15.

Keep reading

Related pages

  • Solution · PlatformCasino platformPlayer accounts, a back office, a bonus engine and multi-brand support, wired to the game aggregator and the shared wallet.Read
  • Solution · TurnkeyTurnkey casinoA full stack for licensed operators: front end, player accounts, back office, aggregated games and an optional sportsbook.Read
  • Guide · AccountsWho owns the playerThe operator keeps identity, KYC, limits and the balance. Studios receive a player id, never the passport scan behind it.Read
  • Solution · White labelWhite labelYour brand on shared casino infrastructure, with aggregated games, an optional sportsbook and a shorter, licence-dependent path to launch.Read

Get a written quote and sandbox access

Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.

Telegram @turnkeyxhub WhatsApp Email Contact form