Guide

Seamless wallet vs transfer wallet, explained

Where the player's balance lives decides more than you would expect: bonusing, reporting, player experience and how much your team builds. Here is the difference, plainly.

The two models

When a casino platform connects to a content provider, someone has to decide where the player's money sits while they play. There are two answers, and they define the two wallet models. In a transfer wallet arrangement, funds move out of the operator's wallet into a separate balance on the provider's side before play, and back afterwards. In a seamless wallet arrangement there is one balance, held by the operator, and the provider settles every bet and win against it in real time.

How a transfer wallet works

The transfer model is the older of the two. The player, or the platform on their behalf, moves an amount into a game balance, plays against that balance, then transfers what is left back. It is simple for the provider, because they only need to track their own ledger during play.

The costs sit with everyone else. The player sees two balances and has to manage the split. Funds parked in a game balance are invisible to the rest of the casino, so a player with money stranded in one provider's balance looks broke to every other game in the lobby. And every transfer is a transaction that can fail, time out or need reconciling.

How a seamless wallet works

In the seamless model the operator's wallet is the only wallet. The provider sends a debit request when the player bets and a credit request when they win, and the operator's platform answers in real time. The player sees one balance everywhere, in the sportsbook, the slots and the live tables, and it is always current.

The name describes the player's experience: they move between games and providers without ever thinking about where their money is, because it never moves anywhere.

Why seamless became the standard

Three reasons, all operational.

Bonusing. Bonus funds, wagering requirements and real-money balances live in one ledger, so promotions work identically across every provider. Under a transfer model, bonus logic breaks at the wallet boundary.
Reporting. One ledger means one source of truth for player activity, liability and settlement. No end-of-day reconciliation between wallets that briefly disagree.
Player experience. No stranded funds, no top-up prompts mid-session, no second balance to explain to support.

This is why aggregation runs on seamless wallets: an operator connecting to dozens of studios through a game aggregator cannot reasonably run a transfer balance per studio.

What each asks of your team

Seamless puts a real, but well-understood, piece of work on the operator's side: your platform exposes wallet endpoints, typically debit, credit and rollback, and answers them quickly and idempotently. Every mature platform has this interface; most were built for it. Transfer asks less of your wallet and more of everything around it, because the fund-movement flows, their failure states and their reconciliation become yours to operate forever.

If you are scoping this work, the integration guide covers what each of our APIs needs from a tech team and the realistic timelines.

How this maps to our APIs

Vivo Gaming integrates operators through two APIs, described in full on the technology page. Data Feed API keeps everything on your side: your engine, your UI and your wallet, while we stream live HD video and game results into your casino. Seamless API is the turnkey route, with wallet and transaction sync running on Vivo Gaming infrastructure in real time, aggregator-ready from day one. Which one fits depends on how much of the stack you want to run, and the integration team scopes it in a single call.

Common questions

Which wallet model is better for bonusing?

Seamless. Bonus funds, wagering requirements and real-money balances sit in one ledger on the operator's side, so promotions behave the same across every provider. Transfer wallets split the ledger, and bonus logic tends to break at that boundary.

Is a transfer wallet ever the right choice?

Rarely, and usually only as a stopgap: a platform that cannot yet expose wallet endpoints can sometimes go live sooner on a transfer arrangement. It is worth treating as temporary, because the operational costs of a second balance grow with volume.

What does a seamless wallet integration require from an operator?

Your platform exposes wallet endpoints, typically debit, credit and rollback, and answers them quickly and idempotently. Most mature casino platforms already have this interface, which is one reason integration timelines are measured in days to weeks rather than months.