Guide · Accounts
The operator owns the player. Studios own games.
Identity documents, the account balance and the self-exclusion list belong to the operator. Game studios and the aggregator need a player id to run a round. They do not need the passport scan.
7 min readUpdated By the Turnkeyxgaming team
Share an id, not a dossier
Send a stable player id, a currency, a country signal you have decided is relevant, and the session. Do not send document images, card numbers or passwords into a game launch. A studio that asks for them is asking for something this integration is not designed to pass, and you should refuse. KYC status can be a yes or no you act on before launch. The documents stay in your KYC system.
Balance lives in your wallet. A studio-side balance is a transfer-wallet design, which this integration does not use. If a report from a studio shows a balance, treat it as their view of unsettled rounds, not as a second ledger your finance team should pay out from. The seamless wallet entry definition is the one the callbacks implement.
A subject-access request about the account is yours: identity, limits and the wallet history. A question about one round can go to the studio as a technical record, with the round id, not the passport. The privacy notice on this website describes this website. KYC status may travel as a yes or no you act on before launch. The images stay in the KYC store. A studio that asks for them is asking for a payload this integration refuses.
What crosses the launch, and what stays behind
The studio needs enough to run a round. The dossier that proved the player is allowed to play stays on your side of the launch call.
| Data | Who keeps it | On the launch? |
|---|---|---|
| Passport images, card numbers, passwords | You, in the KYC store or the PSP. Never in a game ticket. | No. Refuse a studio that asks for them. |
| A stable player id, currency, session, and a country signal you chose to send | You generate the id. The studio sees the id. | Yes. That is the round's identity. |
| Balance | Your wallet. The callback response is the figure. | The response, not a balance the studio stores and pays from. |
| Self-exclusion and limits | Your platform, checked before launch and on the debit. | No profile field for the studio to edit. A yes or no you already enforced. |
Boundaries worth enforcing
- 01
Id only
Launch with a player id and a session. Leave documents in the KYC store.
- 02
You hold the balance
The wallet response is the balance. Do not reconcile payouts from a studio balance figure.
- 03
Exclusion stays home
Self-exclusion is checked by you before launch. It is not a studio profile field.
A studio balance figure is not a second ledger
This integration is seamless. If a studio report shows a balance, read it as their view of rounds not yet settled. Finance pays from your wallet. Reconciling withdrawals against that report will pay money the callback never confirmed.
One disputed round, four desks
A player writes in: the game took the stake and paid nothing. Four desks can answer parts of that. Support holds the account and the conversation. The wallet holds the debit and any credit, keyed by round id. The integration holds the launch and the callback with timestamps. The studio holds the round record, which says what the reels, wheel or hand did.
The order that works: support attaches the round id from the player's history. The wallet is read for the pair of entries against that id. If the pair is complete and matches what the player sees, the case is about the game rather than the money, and it goes to the studio as a technical query quoting the round id and the time. If the pair is incomplete, it stays inside your own systems until you know which side is missing.
The step that goes wrong is the handover. An agent who forwards the whole case to a studio account manager has sent a name, an address, a deposit history and a complaint to a company that needed one identifier. The studio's answer will quote the round. Reaching it should not require a player file to leave the platform that owns it.
Four requests about the same player, four different owners
| Request | Who answers | What travels with it |
|---|---|---|
| Subject access request about the account | You | The account, wallet history and limits, assembled inside your systems |
| Dispute about one round's outcome | The studio, as a technical query | The round id, the time and the game id, with no identity documents |
| Regulator enquiry about a brand | The licence holder, with input on game records | Whatever the enquiry names, gathered by the entity that must answer it |
| Question about a studio's own RNG record | The studio and its lab | The build and the round, not the customer |
FAQ
Questions operators ask
Who answers a subject-access request about game play?
You answer about the player, the account and the wallet history. Studios can be asked about a specific round's technical record. The privacy notice on this site covers this website, not your players' accounts.
Should finance pay a withdrawal from a balance printed on a studio report?
No. That figure is the studio's view of rounds not yet settled. Pay from your wallet. A payout against the studio number will not match the callbacks, because this integration does not keep a second ledger.
Can the studio hold a copy of KYC so they can block a player themselves?
No. Exclusion is checked by you before launch and on the debit. Passing document images so a studio can build a parallel account creates a dossier outside the system that owns the player, and this integration has no field for it.
The studio's support form asks for a player email. What do we send instead?
The round id and the time it was played, which is what their record is keyed on. If the form will not accept an identifier, raise it through the account manager rather than filling the field. A studio that cannot look up a round without a customer record has a process problem you are about to solve by sending data you should not.
When we close an account, what does the studio still hold?
The rounds they generated, keyed to the player id you sent and whatever else the integration passes. Ask what they retain and for how long, put the answer in the contract, and check that your own deletion process does not assume a copy never left. The player id is the only handle you gave them, so it is the handle to trace.
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.
- Malta Gaming Authority
Licensing and player-protection rules for Malta-licensed operators.
www.mga.org.mt
- UK Gambling Commission
Remote gambling and software technical standards.
www.gamblingcommission.gov.uk
Keep reading
Related pages
- GlossarySeamless walletA seamless wallet keeps the balance on the operator's ledger and posts every bet and win as a live callback, per round, in the session currency.Read
- Product · WalletWalletBalance, bet, win and rollback on one seamless wallet: idempotent transaction ids shared by casino games and sportsbook alike.Read
- LegalPrivacyHow this website handles personal data from the contact form and messaging channels, including how long enquiries are kept.Read
- Guide · Safer gamblingDeposit limitsDeposit, loss and session limits are enforced on the player account before a game launches, not separately inside each studio.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.