Product · Payments
Casino payment API: where payments meet the wallet
Players deposit and withdraw through payment providers; they play through the casino API. Those are two different systems, and keeping them separate is what keeps a seamless wallet clean.
- Deposits and withdrawalsRun by your payment providers
- WalletYour ledger, updated by both systems
- AggregatorDebits and credits only, never card or bank data
What Turnkeyxgaming does not do
The casino API does not process card, bank or crypto payments and does not hold player funds. Payment connections are arranged with your own payment providers, or scoped as part of a turnkey build. Ask sales exactly which payment work a quote includes.
Money flow
How a deposit becomes a bet
- 01
Deposit
The player pays through a casino payment gateway. The PSP confirms the deposit to your casino deposit API.
- 02
Ledger credit
Your platform credits the player's balance after the PSP confirmation.
- 03
Play
Game rounds debit and credit that balance through the wallet contract.
- 04
Withdrawal
Your casino withdrawal API checks KYC and limits, then instructs the PSP to pay out.
Payment methods operators ask about
SEPA casino payments
Euro bank transfers across the SEPA area. Settlement is cheap but not always instant, and instant SEPA availability depends on the banks on both sides.
Open banking casino payments
Account-to-account payments authorised in the player's banking app. They are popular in the UK and growing in the EU, and they reduce card declines.
Crypto casino payments
Allowed only where your licence permits it. You need a crypto PSP that handles conversion, travel-rule data and wallet screening.
Casino USDT payment
Stablecoin deposits avoid price swings during play, but the regulatory treatment of USDT differs by market. Confirm it with counsel and your licence.
Choosing an iGaming payment gateway
This page explains how a casino payment API fits next to the aggregator and which decisions belong to you.
An iGaming payment gateway has to accept gambling merchant category codes, support your markets' local methods and pass your regulator's rules on source of funds. Generic e-commerce gateways often refuse gambling traffic or close accounts later. Ask every candidate whether they hold gambling merchant approval in your licence's jurisdiction.
Technically, a gambling payment API or iGaming payment API talks to your platform, not to the aggregator. Casino payment integration happens in your cashier and back office. That separation is why you can change PSPs without touching a single game.
Paying the aggregator: GGR invoices and crypto top-ups
Some aggregators let operators pre-fund GGR fees, sometimes with a crypto top-up casino aggregator balance. How Turnkeyxgaming invoices are settled is agreed in your contract. This site does not promise a particular settlement method, so ask sales which options apply to your entity and region.
Which system owns which job
A €25 deposit confirmed by the PSP at 19:04 credits your ledger. The player opens a game, and every round after that is a wallet call — the PSP is not involved again until a withdrawal. The two systems meet in exactly one place, your ledger, and the split below decides which team answers which ticket.
The cashier and its PSP own
- Card, bank and crypto capture, and the PCI scope that comes with touching card data
- Deposit authorisation, source-of-funds checks and the settlement timetable into your account
- Withdrawal approval after KYC, plus payout rules such as pay-back-to-source
- Chargebacks, the fees attached to them and the recovery policy for a balance already played
The wallet contract owns
- The supported callback types for a round — balance, debit, credit and rollback — on the seamless wallet. Not every round emits all four
- Idempotency by transaction UUID, so a network retry cannot charge one stake twice
- An audit line for every round, including voids, in the currency of that session
- Nothing that touches a card, an account number or a key of any kind
Selection
Questions that separate a gambling PSP from a generic one
The catalogue integration is quoted at 24–72 hours. The cashier side has no such clock: it runs on the PSP's due diligence and your licence. Put these to every candidate, and treat a hedged answer as the answer.
| Question | Why it decides the launch | Answer that should slow you down |
|---|---|---|
| Do you hold a gambling merchant approval for this licence? | An account closed at week six stops deposits for the whole site | 'We can process it as a normal e-commerce category' |
| What is the settlement timetable for each method? | Cash-flow promises depend on it; T+5 on cards changes what you can offer | A timetable given on a call but missing from the contract |
| Who pays the fees on a refund or chargeback? | A reversal after play also takes back your margin | 'Standard fees apply', with no schedule attached |
| Which methods are live in which market? | A method shown in the cashier that fails at checkout loses the deposit | Coverage quoted for a whole region rather than per market |
| How do you handle a refund against a balance that has already been played? | It decides whether the ledger can go negative, and who recovers it | 'That is between you and the player' |
Refunds unwind deposits; voids unwind rounds
A refund or chargeback is a cashier event: the PSP takes the money back and your ledger is adjusted. The rounds the player already settled stay settled, which is how a balance can go negative — write the recovery policy into your terms before launch. A void is the other case: a wallet event where a round never completes and the stake returns through the rollback call. Support teams conflate the two, and the ticket that follows usually quotes the wrong system. Any balance-blocking or recovery tooling on the aggregator side is confirmed in writing during onboarding.
FAQ
Questions operators ask
Will the casino API see my players' card details?
No. The wallet contract carries player IDs, amounts and currencies only. Card and bank data stay between the player, your cashier and your PSP.
Can you recommend a PSP?
We can share what other operators in your region typically use, but the choice and the contract are yours, and so is the PSP's gambling approval.
Who carries the PCI scope?
It depends on the integration, so treat any categorical answer with suspicion. Card data normally flows through the player's browser to the PSP's hosted fields, which keeps it out of your servers and out of the aggregator entirely. Whether your own environment is in scope, and which self-assessment questionnaire applies, depends on how the cashier is built and how the PSP's fields are configured. The wallet contract carries player ids, amounts and currencies only, so an aggregator that never sees a card number does not add cardholder-data scope by itself. Ask the PSP for its current attestation and confirm final scope with your QSA.
Can a withdrawal be sent back to the deposit method?
That is your cashier's rule and the PSP's capability, not the wallet's. By the time a payout is requested, every round has settled on the wallet; the instruction and the method choice happen in the cashier. Some PSPs require payout to the source method, so check before you promise players a choice.
A deposit is reversed after the balance was played. What moves?
The PSP recovers the money from you, and the ledger is adjusted under your terms. Rounds that already settled are not unwound, so the account may sit in negative balance. That is the moment your published recovery policy matters. Any request to block or restrict the player on the aggregator side is confirmed in writing during onboarding.
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.
- PCI Security Standards Council
PCI DSS scope and payment-card requirements.
www.pcisecuritystandards.org
- UK Gambling Commission
Remote gambling and software technical standards.
www.gamblingcommission.gov.uk
Keep reading
Related pages
- Product · WalletWalletBalance, bet, win and rollback on one seamless wallet: idempotent transaction ids shared by casino games and sportsbook alike.Read
- 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
- PricingPricingPublished rates are 13% of GGR in Asia and 16% elsewhere, all-in. Why a cheaper headline rate often hides the real terms.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.