Turnkeyxgaming

Guide · Wallets

Seamless wallet vs transfer wallet

How money moves between your platform and the games is the most important architectural decision in a casino integration. There are two models. This guide compares them on player experience, engineering effort and reconciliation.

7 min readUpdated By the Turnkeyxgaming team

The two models

Seamless wallet

  • The balance lives only in your ledger
  • Every bet and win is a real-time call to your wallet
  • One balance across every game and sport
  • Your wallet must be fast and idempotent

Transfer wallet

  • The player moves funds into a game or provider balance
  • Play happens against that separate balance
  • Funds are transferred back when the session ends
  • Simpler for providers, worse for players and finance

Side by side

SeamlessTransfer
Player experienceOne balance everywhereManual transfers; funds stuck in game balances
EngineeringA fast, idempotent wallet endpointTransfer endpoints plus balance sync
Failure modeRetries and rollbacks per transactionHalf-completed transfers and orphaned balances
ReconciliationEvery round recorded in your ledgerSeparate balances to reconcile with each provider
Responsible gamblingLimits apply to every bet in real timeLimits are harder to enforce inside transferred balances

Why seamless won

Seamless wallets became the default because players expect one balance and regulators expect limits that apply in real time. The cost is engineering discipline: your wallet must respond quickly and handle duplicate requests safely. That cost is paid once, and every studio benefits from it.

Transfer wallets still exist, mostly with older or smaller providers. If a studio you want only supports transfers, ask whether the aggregator can present it seamlessly to you. Often it can.

What the player sees when a transfer stops halfway

A transfer wallet asks the player to move cash into a game balance before play, and to move it back when they finish. If the session ends because the app closed, the network dropped, or the provider timed out, the funds can sit in the game balance with no round in progress. Support then has to find that pot, prove it is the player's, and move it back. Until that happens the cashier shows a smaller balance than the player remembers, and the withdrawal they expected fails.

A seamless debit fails in a narrower way. The stake is either on the operator ledger or it is not, and a retry with the same transaction id must not take it twice. There is no second pot to sweep at the end of the night. That is why finance prefers the model even though the wallet has to answer quickly. If a studio can only transfer, the useful question is whether those transfers can stay inside the aggregator so the player never sees a second balance and your ledger still has one figure to reconcile.

A limit that cannot see the game pot is not applied

Deposit and loss limits have to be able to refuse the next stake. Money that has already been moved into a provider balance is easy to play and hard to stop from the cashier. If you must transfer, say how the limit still reaches that balance. If you cannot say, do not call the control real-time.

€200 into a game balance at 22:41

At 22:41 a player moves €200 from the cashier into a live casino provider's balance. Two hands cost €60 and they close the app at 22:53 without moving the rest back. The provider keeps the session open; at 02:00 its housekeeping job returns €140, but the transfer-out arrives with a reference the provider generated rather than the one the cashier wrote at 22:41. The player logs in at 09:12 to withdraw €380, sees €240, and calls support.

Nothing was stolen and nothing is missing. The €140 sits in a provider balance whose lifetime nobody documented, and the cashier is right about the operator ledger. Support has to find the transfer-out, match it to the transfer-in by player, amount and time window, and post the return. That is twenty minutes for a trained agent, a day for an untrained one, and the same twenty minutes every week for as long as the model stays in use.

The seamless version of that evening is dull. The two hands debit €60 from the operator ledger as they settle, the balance is lower on the way out, and there is no second pot to sweep. If you inherit a provider that only transfers, the work is not finished when the transfer endpoints pass: you need a sweep, an orphan report and a rule for a return reference that does not match yours. The wallet API page lists the callbacks a seamless integration has to answer.

If you cannot avoid transfers, these controls are the model

Each of these exists because a transferred balance is money your cashier cannot see. Skipping one moves the cost to support, where it arrives as a complaint rather than a defect.

  • A nightly sweep listing every provider balance still open, by player, provider and age, sent to someone who acts on it rather than to a shared inbox.
  • A matching rule that tolerates a provider-generated reference, using player, amount and a time window, plus a queue for anything that matches nothing.
  • A statement line the player can read: money left the cashier for this provider at this time, and came back. A smaller balance should be explainable on one screen.
  • A timeout on transfer-in and transfer-out in your own system, with the provider's behaviour confirmed in writing, because a transfer that waits indefinitely is a balance nobody owns.
  • A responsible-gambling check that can still refuse a stake inside the transferred pot, or a written statement that the control ends at the cashier.
  • A support runbook naming where the provider balance lives, who can move it, and how long a return should take before it is escalated.

FAQ

Questions operators ask

Seamless vs transfer wallet: which is better for a new casino?

Seamless, almost always. It gives players one balance, simpler reconciliation and real-time limits. The glossary entry defines it in a sentence.

What should support do if a player closed the app during a transfer?

Find the provider balance, confirm no round is still open, and return the funds to the operator ledger. Leaving the pot until the player logs in again is how withdrawals fail and complaints age.

Can an aggregator hide a studio's transfer wallet from the player?

Often yes: the aggregator performs the transfer and your player still sees one balance. Ask for that explicitly. A studio that insists the player move money in the client is still the transfer model, whatever the contract is called.

Does a transfer wallet change how a bonus is calculated?

It changes where the stake comes from, not what the campaign counts. The complication is that the transferred pot sits outside your ledger while it is in play, so a wagering engine reading only the operator balance misses those rounds until the money returns. If bonuses and transfers coexist, contributions have to be fed from the provider side.

Is a session wallet the same thing as a transfer wallet?

Not necessarily, though the name is used loosely. Some suppliers mean a balance that exists for the length of one game session. The test is whether funds leave your ledger and sit somewhere else. If they do, every control on this page applies whatever the supplier calls the model.

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
  • 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
  • Guide · ArchitectureHow a casino API worksOne casino round traced end to end: catalogue, launch, wallet callbacks, settlement and the report line the next morning.Read
  • IntegrationIntegrationSandbox keys, AES-encrypted wallet callbacks and the four wallet endpoints, then a 24–72 hour go-live once decryption and retries pass.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