Guide · Integration
The cashier link has to return to the same session
Low-balance buttons inside a game are only as good as the URL you passed at launch. A generic homepage URL makes the player log in again and lose the game they were in.
7 min readUpdated By the Turnkeyxgaming team
Return to the game, not to marketing
Pass a cashier URL that knows the brand, the player session and the game to resume. When the deposit succeeds, send them back to a fresh launch of that game, not to a bookmarked launch URL that has expired. When the deposit fails or the player cancels, send them back anyway. Stranding them on a receipt page is how a simple top-up becomes a lost session.
Multi-brand platforms get this wrong by sharing one cashier host and forgetting the brand id. The player deposits onto the wrong wallet and the original game still shows zero. Put the brand in the URL and check it. Deep-link schemes for apps need the same two hops: out to the cashier, back to a new launch.
Pass the game id and a return token that can request a fresh launch, not the launch URL that is already in the player's hand. That URL will be expired by the time the payment provider redirects home. On success, the new launch must read the balance after the credit, not a cache from when the game was opened. On cancel or failure, return to the same game anyway. A receipt with no path back is how a declined card becomes a lost session.
The two hops the low-balance button has to survive
Out to a cashier that knows the brand and the player. Back to a new launch of the same game. Test both outcomes, not only the happy deposit.
- The cashier URL carries brand, player session and the game to resume. A generic homepage drops the context.
- A successful deposit returns through a fresh launch. The new session sees the credited balance.
- Cancel and failure return to that game as well. The player is not left on a receipt.
- An expired launch URL is never the return address. The return token asks for a new one.
- On a shared cashier host, the credit hits the brand that opened the game. Check it with two brands, not one.
Test the low-balance button
- 01
Success path
Deposit, return, and confirm a new launch sees the new balance.
- 02
Cancel path
Cancel the deposit and confirm the player is back at the game, not on a dead page.
- 03
Right brand
On a multi-brand host, confirm the credit hit the brand that launched the game.
Card details stay in the cashier
The game client needs a way out and a way back. It does not need the card number, and a webview that asks for one is the wrong product. Keep the payment page on your PSP's surface.
Mobile flow
The return path on a phone, hop by hop
On mobile the cashier is usually a separate surface, sometimes a browser tab and sometimes a PSP-hosted page. The game passes a return token with the brand, player session and game id. The cashier sends the player to the PSP, and the PSP returns to the cashier, not to the game. The cashier then exchanges the token for a fresh launch of that game and opens it in the app or the frame the player came from.
Two failure paths need a destination: a cancelled payment and a failed one. Both should return to the game, not to a receipt with no way back. If the return token has expired, the cashier asks for a new launch rather than reusing the URL the player already had. Test the whole sequence on the webview you ship, because a return that works in a desktop browser can still fail when the app loses focus.
Four hops and the parameter each one needs
| Hop | What travels | If it is missing |
|---|---|---|
| Game to cashier | Brand, player session, game id, return token | The player lands in a generic cashier and loses the game |
| Cashier to PSP | Payment session and the return address | The player is stranded on the PSP page |
| PSP back to cashier | Payment result and the return token | The cashier cannot tell a success from a cancellation |
| Cashier to game | A fresh launch request for the same game | An expired launch URL opens a blank frame |
FAQ
Questions operators ask
Should the game client take card details?
No. Card data stays with your PSP and cashier. The game only needs a link out and a way back.
Can the game resume the exact session after a deposit, without a new launch?
Assume the original launch token is dead by the time the redirect returns. Request a new launch of the same game id against the same player and currency. The balance on that launch is the one that includes the deposit.
What if the player has two brands bookmarked on one cashier domain?
The brand id in the URL decides the wallet. Without it, the credit lands on whichever brand the shared session last touched, and the game they came from still shows the old balance.
What if the player does not have the app installed?
The return path needs a web fallback that opens the same game in the browser session. A deep link that fails silently leaves the player on the cashier with a completed deposit and no game, which is the case support will hear about.
Keep reading
Related pages
- Product · PaymentsPaymentsDeposits and withdrawals stay with your payment firms. The aggregator never moves SEPA, cards or USDT and never holds player funds.Read
- Guide · IntegrationLaunch parametersLaunch sets the player, currency, language and the lobby and cashier return URLs. Stop hard-coding those paths per studio.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
- Guide · IntegrationSeveral brandsRun several brands on one integration without sharing catalogues, limits or GGR. The contract is shared; the players are not.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.