Seamless wallet
A seamless wallet keeps the single authoritative player balance on the operator's side, and the game supplier calls the operator for every balance check, bet, win and rollback.
The alternative, a transfer wallet, moves funds into a per-provider sub-wallet before play and back again afterwards. That creates stranded balances, transfer failures and a poor player experience, which is why almost all modern integrations are seamless.
Seamless puts real requirements on the operator endpoint. It must respond quickly, be idempotent per transaction ID so retries never double-charge, and return a clear success or failure status — because a rejected call must not be treated as a settled round.
AS Tech API signs every callback with HMAC-SHA256 over the exact raw request body, retries with backoff, logs both sides of every call, and excludes rejected callbacks from transactions and from GGR.
- One balance, no per-provider sub-wallets or transfers
- Idempotent on transaction ID so retries are safe
- HMAC-SHA256 signature over the raw body, verified before parsing
- Explicit success or failure status on every response
Frequently asked questions
How fast must my wallet endpoint respond?
Keep responses inside a few seconds. AS Tech API allows up to seven seconds before a callback is treated as timed out and retried.
What happens if my wallet rejects a bet?
The round is refused upstream, no transaction is recorded and no commission is charged. A rejection must never be recorded as a settled bet.