Skip to content

FAQ

Who handles registration, CPF, KYC and the cashier?

Section titled “Who handles registration, CPF, KYC and the cashier?”

Your casino platform. OrbiSportbook provides the sportsbook via iframe and connects to your wallet. Player registration, authentication, CPF validation, KYC, deposits and withdrawals stay with your platform and its providers. Players use their existing casino account and balance.

Does kycStatus: verified mean OrbiSportbook verified the player?

Section titled “Does kycStatus: verified mean OrbiSportbook verified the player?”

No. For players created through the integration, it records that identity verification is delegated to the operator. It does not represent a document, CPF or facial check performed by OrbiSportbook. Sessions use your platform’s player ID without requiring or checking CPF, including for the BR profile.

What does the sportsbook’s Deposit button do?

Section titled “What does the sportsbook’s Deposit button do?”

It sends deposit_requested to your page. Open your platform’s cashier, process the deposit there, then call refreshBalance() so the iframe displays the updated wallet balance. OrbiSportbook does not collect the deposit or pay a withdrawal to the player.

Why a launch token and not just the session token?

Section titled “Why a launch token and not just the session token?”

A URL is copied into browser history, server logs, analytics and Referer headers. A launch token found there is useless: it worked once, within two minutes. The long-lived session token never leaves your server and the iframe.

Yes. Mount without launchToken. Prices, live scores and the bet slip work; placing a bet or opening My Bets sends you login_required. After your login, send the new launch token with setLaunchToken(): the iframe is not reloaded and the bet slip is kept.

Do I need to call the platform when the player’s balance changes on my side?

Section titled “Do I need to call the platform when the player’s balance changes on my side?”

No. The sportsbook asks your /balance endpoint when it shows the balance. After a deposit in your cashier, call refreshBalance() so the iframe shows it at once.

None. Book money only from the wallet calls you receive and confirm. Browser events (bet_placed, balance_changed, bet_settled) are for your UI and analytics.

Every settled bet receives exactly one payout: credit, with amount: 0 when it lost. It tells you the bet is closed. See Zero-amount credits.

Stakes are refused while we cannot reach you (the player sees that the sportsbook is temporarily unavailable). Credits and rollbacks are retried with the same txId until you answer, so nothing is lost; make sure you process each txId once.

Why did I receive a rollback for a debit I never saw?

Section titled “Why did I receive a rollback for a debit I never saw?”

Our debit did not reach you, or your answer did not reach us, within 5 seconds. We refused the bet and roll back to be safe. Answer 2xx, remember the ref, and refuse that debit if it ever arrives.

Only through a correction after a resettlement: if a result is corrected and the player was paid too much, we debit the difference (kind: resettle), which you should apply even if the player already spent it.

Yes: add each origin to embedOrigins. Origins are exact: https://www.example.com and https://m.example.com are two entries.

English (en) and Brazilian Portuguese (pt-BR). Pass locale or call setLocale().

Yes, through the theme: every colour, the font, the radius, the density and the layout are tokens you edit in the back office (Theming).

Yes: the sandbox, with simulated matches and play money. See Testing.