Skip to Content
WalletSeamless WalletOverview

Seamless wallet

The idea of a seamless-wallet approach

  • operators platform and Sportsbook provider use only operators’ wallet
  • operator’s clients place a bet using the money that is present on the operators’ wallet
  • all the betting transactions are performed on the operators’ wallet

Integration schema

Sportsbook FE is the embedded iFrame, or your own frontend built on the Sportsbook API. The three wallet calls on the right are the same either way.

User-flow

The player session must already exist before any wallet call happens. How it is established depends on the product:

  • iFrame — you log the player in on your platform and initialize the iFrame with a validated JWT. See Seamless Login.
  • Your own frontend — you exchange your platform’s token for a Sportsbook session. See Login with token (requires sign-in).

The wallet calls that follow are identical in both cases. The diagram below shows the iFrame case.

Note

User-flow description

  1. player-session - the player is logged in on the operator’s platform and the Sportsbook frontend has an authorized session. In an iFrame integration that means the iFrame was initialized with a validated JWT token — see Seamless Login.

  2. place-bet - the operator’s user tries to place a bet.

    2.1 /place-bet-request - the Sportsbook frontend is sending a request to the Sportsbook BE.

    2.2 processing - Sportsbook BE is validating and processing a bet due to the different risk management settings.

    2.3 /perform-transaction - in case of successful bet processing Sportsbook BE will send a transaction to the operator’s platform BE for user cash debit.

Integration

The client must implement the next endpoints on the side of their platform to guarantee the correct work of a seamless wallet mechanism:

Three rules apply to all of them:

  • Any URL works. You host each endpoint wherever suits your platform — the paths shown on the endpoint pages are only examples.
  • Tell GR8 Tech the URLs. They are configured on the Sportsbook backend, which is the side that calls them.
  • One endpoint per tenant. If you run several Sportsbook brands/tenants, either expose a separate URL per tenant or branch on the X-Brand and X-Operator-Id headers that every request carries.

Request signature

Signing requests is optional and is disabled by default. More information can be found here 

OverviewGet User Balance