Transfer Wallet
An older integration pattern where a game provider keeps its own separate balance, so the player must transfer funds from the operator wallet into the provider before playing and back out afterwards.
Definition
In a transfer wallet model, the game provider maintains a wallet of its own, distinct from the operator's main balance. Before a player can wager on that provider's games, funds are moved from the operator wallet into the provider wallet; when they finish, the remaining balance is transferred back. This decouples gameplay from the operator wallet during a session, reducing per-bet API traffic, but it creates a clumsier experience, the risk of stranded balances if a transfer-back fails, and extra reconciliation work. It was common in early integrations and still appears with some legacy providers or in markets with specific constraints, but most modern operators prefer seamless wallets for a single continuous balance.
Worked example
A player wants to try Provider Y's games and clicks Play; the platform moves 50 from the main wallet into Provider Y's wallet. They play, finish with 62, and the system transfers 62 back to the main wallet. If that transfer-back fails, the 62 is temporarily stranded in the provider wallet until reconciliation resolves it.
Why it matters
For learners, it explains why some older sites made you move money into a game and why a balance could get stuck. For professionals, knowing the trade-offs, per-bet traffic versus experience, stranded funds and reconciliation, informs integration choices and helps diagnose balance discrepancies with legacy providers.