One player, One wallet
BLUE PAM keeps the player’s account, wallet, history, limits and bonuses in one profile — across web, mobile app, terminal and retail.
3Live markets
5 000 000+Transactions per day
600 000+Player accounts in BLUE PAM
1Wallet for sportsbook and casino
Players never have to start over.
Online and retail work as one continuous player journey.
Web and mobile app
Balance, bonuses, limits and history stay the same across devices.
Retail and online profile
Once identified, the player uses the same account and balance in retail as they do online.
Casino and betting
Players use the same balance across sportsbook and casino — no need to move funds between products.
PLAYER JOURNEY
Deposits, gameplay, bonuses and withdrawals stay connected to the same profile.
The account is created once
The player creates an account once, on the web, on mobile, or at a retail terminal. You configure the form and consents per market.
The same account, no matter where the player started.
You know who's behind the account
An ID document, a selfie, and a check against official registers. Player Account Management (PAM) tracks verification status and flags whose document is about to expire.
Verification status determines both limits and payout.
One wallet for everything
One wallet for every product: real and bonus balance, multiple currencies, and a history of every movement.
Every movement has a status, an author, and a traceable record.
The player never switches wallets
Casino, sportsbook and retail all draw on the same balance. The player switches nothing and moves nothing.
Other parts of the platform supply the content, the account stays one.
Rules that can't be worked around
Bonus rules and deposit or time limits apply the same way on web, mobile, and terminal.
A limit set on mobile also applies at the retail terminal.
Payout and an auditable trail
Payout follows a verification and risk check. Reports for your operations and the regulator come from the same data.
One data source for operations, finance, and compliance.
One player profile for every team.
Each team works with the part of the profile they need — from identity and balances to bonuses, audit and reporting.
No switching between systems
Support doesn't open three systems to answer one question. Contact details, verification status, balances, recent activity, and open requests all sit in one place.
Money, in real time
Deposits, withdrawals, corrections, and reversals in one view. Filter by method, status, or risk score, and see exactly where the money got stuck.
A campaign without a development ticket
Marketing sets the conditions, values, and validity on its own. PAM makes sure a bonus never lands where it shouldn't and can't be claimed twice.
You know who's behind the account
Verification isn't a one-time action, it's a status that keeps changing. PAM knows whose document is about to expire, who's stuck mid-process, and who needs to be checked again.
Limits nobody can work around
Limits aren't a front-end setting a player can dodge by switching channels. They're enforced at account level, so they apply everywhere.
Reports built on the same data
Operational reports, the financial close, and regulatory filings all draw from a single source. Nobody has to reconcile numbers from three exports that contradict each other.
Who saw what, who changed what
Role-based permissions and a record that can't be overwritten. In an audit or an internal dispute, you know exactly what happened and who's behind it.
Built to grow
PAM holds the accounts, the money, and the rules. Without payments or content, though, it has nothing to manage, so part of the platform belongs to it from day one, and you add the rest as you grow.
COREAccounts, wallet, bonuses, limits, back office and audit
The core you get in every deployment. The other parts of the platform connect to it based on what you run.
Payment methods and payouts
Viewarrow_forwardFOUNDATION
Identity verification and KYC
Viewarrow_forwardBY PRODUCT
Casino content
Viewarrow_forwardBY PRODUCT
Odds and match coverage
Viewarrow_forwardAS NEEDED
Retail points and self-service
Viewarrow_forwardAS NEEDED
Campaigns and communication
Viewarrow_forwardAS NEEDED
Loyalty and card
Viewarrow_forwardAS NEEDED
Prediction and player protection
Viewarrow_forwardCompliance is built into the core.
Controls, audit trails, limits and sensitive operations are built directly into BLUE PAM.
Checks against the register of excluded persons
At registration and at every login. If a player is on the register, the account stays out of reach.
Sanctions lists and PEP
Screening at entry and then on an ongoing basis, not just once when the account is opened.
Evidence for suspicious transaction reports
Thresholds, flagged cases, and transaction history in a single export.
An audit log nobody can rewrite
Who changed a limit, account status, or balance, when, and from which IP. Even viewing it leaves a record.
Dual approval for sensitive operations
A manual balance correction or lifting an exclusion can't be triggered by one person alone.
Data retention and deletion
Retention periods per market and an auditable deletion once they expire.
3× ISO certified
Less manual work, more visibility
Operations teams manage on their own, channels stop contradicting each other, and you launch a new market faster.
A player who doesn't get lost between channels
The account, the balance and the history are one. Online and retail finally talk about the same person.
Teams manage without a developer
Support, risk and marketing have their own tools. A routine change doesn't end up in the development backlog.
Faster entry into a new market
You configure the market rules. No new code and no new project is written for them.
Evidence when you're inspected
Reports and the audit trail over the same data your operations team works with.
Player protection with no workarounds
Limits and exclusions apply at account level, so they apply the same way across every channel.
One partner for the whole core
One contract and one phone number when something needs solving.
What operators ask us most
Can we buy BLUE PAM on its own?add
PAM is the backbone of BLUE Platform, so we don't supply it as a standalone component for a third-party system. It's part of every deployment, and the rest of the platform connects to it based on what you run.
So what are we actually deciding?add
The scope. You always get the core: accounts, wallet, bonuses, limits, back office, and audit. You choose which products and channels you launch on top of it, and in what order you add them.
Can PAM handle multiple brands and markets?add
Yes. Brands, currencies, languages, and market-specific rules are a matter of configuration, not another installation. Operations teams see only the brands they're authorized for.
How are limits and self-exclusion enforced?add
At account level, not inside individual applications. A limit set on mobile also applies on the web and at the terminal, and a player can't dodge it by switching channels.
What does the regulator see?add
Reports and the audit trail draw on the same data your operations team works with. Every account change has an author, a timestamp, and a reason, so answering an inspection never means digging things up by hand.
Where is PAM deployed?add
Wherever you need it — in your own infrastructure or in an environment you choose, including requirements on which jurisdiction the data sits in.
We'll show you on your own operation
Write to us and we'll get back to you within 24 hours.