Seamless Wallet API
SEAMLESS mode — you hold the player wallet. best-system calls your wallet API synchronously, per transaction
The 10 endpoints
| Endpoint | Wallet direction | When it is called |
|---|---|---|
| POST /api/balance | read | Read the balance (no money movement) |
| POST /api/bet | debit | Place a bet |
| POST /api/settle | credit | Pay out winnings |
| POST /api/refund | credit | Cancel a bill, return the stake (REFUND/REJECT) |
| POST /api/reward | credit | Jackpot / bonus |
| POST /api/rollback | debit | Take back an already-paid settle |
| POST /api/void | net | Cancel the whole round (carries a direction field) |
| POST /api/tip | debit | Dealer tip |
| POST /api/cancel-tip | credit | Cancel a tip |
| POST /api/adjust | net | Bet adjustment / fishing (carries a direction field) |
Getting started in 5 steps
- Get credentials + register your callback URL — best-system issues your
api_key/secretand registers yourseamless_callback_urlon the bo screen: Api Management → API Credential - Implement all 10 endpoints in the table above
- Verify the signature on every request —
X-Api-Key+ HMAC over the raw bytes; see Authentication - Make it atomic + idempotent — one batch rolls back as a whole, a re-sent call must never double-charge; see Contract
- Test with the best-system team before go-live — walk through every endpoint, including the retry (idempotency), insufficient-balance and single-state settle cases
Read next
- Authentication — verify
X-Api-Key+ the HMAC signature - Contract — request envelope · response · atomic/idempotency/retry
- Seamless codes — the full result-code catalog