Sports data and settlement

The sportsbook consumes the paid Odds-API.io feed from the backend. Partners use the existing Aggregator API, sessions and wallet callbacks; they do not need a supplier key.

Prices and settlement

Bet365 is the primary source. Other selected bookmakers are observations. Full market replacements remove withdrawn lines; disconnected or stale source state blocks acceptance. Prices and event state are checked again after the wallet debit. A failed acceptance reverses that debit using the original transaction identity.

Only complete, explicitly final grades settle supported markets. A repeated result does not create a second credit. A lost credit response retries the same wallet transaction. Material corrections and loss of finality block further financial effects until staff reviews the exact evidence revision.

Live handicaps with unresolved grading semantics and markets outside the supported registry remain unavailable. Missing events, missing grades and transport errors are not interpreted as losses or refunds. Bet Builder requires a validated joint pricing model and remains unavailable for these supplier selections.

Operator integration

1. Create the client through the Aggregator API and install the separate sandbox and production wallet secrets.
2. Activate the client after both wallet endpoints pass validation.
3. Create sessions from your backend and launch the iframe with its single-use launch token.
4. Complete the wallet certification matrix before real-money go-live.

Aggregator activation proves configuration and wallet reachability; it does not certify every financial scenario or production infrastructure. Keep the supplier key out of browser code. See the go-live checklist.