BetAPI Solutions

Integration · Transfer wallet

Transfer Wallet Integration

The transfer wallet API is the quickest way onto our catalog: you move funds into a player’s game wallet and back, and there are no callbacks to build.

  • 3commands for money
  • 3commands for reports
  • 0callbacks to build
Transfer wallet API: your platform moves funds into a player’s game wallet and back, and games play from that wallet with no callbacks to your side Your platform main balance Move in Move out Game wallet one per player, own currency Games bets, wins You make every call. We never call you.

Three commands for money

Your platform drives every money movement. Three commands cover the whole life of a player’s game wallet, and each one is a call you make, never a call you have to answer.

  • Create a game wallet

    Open a separate game wallet for a player. This individual wallet API keeps game funds apart from the main account on your platform.

  • Move funds in or out

    Transfer an amount into the game wallet before play and back to your platform afterwards. Amounts are sent to two decimals.

  • Check the balance

    Read what is in the game wallet at any moment, for example before you move the remainder back.

Each player wallet has its own currency.

The flow is simple to reason about. When a player opens a game, your platform moves the amount they want to play with into their game wallet. Bets and wins happen against that wallet on our side, and no spin starts on an unconfirmed balance. When the player leaves, you check the balance and move it back to the main account. At no point does the game side reach into your platform, so there is no endpoint to expose, secure and keep online around the clock.

Every command is signed with HMAC-SHA256 and accepted only from the IP addresses on your allowlist. Each transaction ID is applied once, so a command retried after a network error cannot move the same funds twice. Fees are a share of GGR drawn from your prepaid balance; see casino API pricing

Three commands for reports

The same API that moves the money also tells you what happened to it, from a daily total down to a single spin.

  • Daily totals

    Bet and win totals for each day, ready to reconcile against your own ledger.

  • Player sessions

    A player’s game sessions for a date range, so support can see when and where they played.

  • Spin-by-spin log

    Every bet and win inside one session, for the disputes where detail matters.

Report requests cover the last 10 days.

Because report requests reach back over a rolling window, it makes sense to pull the daily totals once a day and store them in your own systems. That gives finance a permanent record to match against transfers in and out, and it keeps the session and spin-by-spin requests free for the cases that need them: a player asking about a round, or a support agent checking a session before answering a ticket.

When a transfer wallet casino makes sense

The transfer model trades one shared balance for a much smaller build. Whether that trade is right depends on what you run and who builds it.

Good fit

Transfer wallet

  • A single-product casino.
  • A team without capacity for callbacks.

Consider seamless instead

Seamless wallet

  • Casino and sportsbook on one balance.
  • Players who should never move money between wallets.

How the seamless wallet works

We recommend most operators start on seamless; you can switch models later.

With a seamless wallet the game side asks your wallet for the balance and sends every bet, win and rollback to you, so your developers build and run those endpoints. With a transfer wallet you only send commands, which is why it gets a small team live with less work. The cost is that the player’s money sits in two places while they play. For a casino with one product that is rarely a problem; for a brand that wants slots and sports betting on one balance, seamless is the better long-term choice.

The catalog, the game launch and the reporting are the same in both models, and so are Stage, Prod and your prepaid balance. See the full casino API integration guide

Transfer wallet FAQ

What is a transfer wallet?

A model where the operator moves funds into a separate game wallet for each player and back again, instead of the provider calling the operator’s wallet.

Do I need a callback endpoint?

No. You make every call; we never call you.

Are requests signed?

Yes, every command carries an HMAC-SHA256 signature.

Which reports are available?

Daily bet/win totals, session lists and spin-by-spin logs for the last 10 days.

Start your transfer wallet integration on Stage

Stage and Prod are separate, each with its own login, keys and IP allowlist. Stage credentials arrive within 24 hours of prepayment, and you move to Prod after acceptance.

Prefer to write? Use the contact form.