How do casino API rollbacks work?
Why rollbacks exist
Studios and aggregators must reverse a bet or win when a round is voided, a table fails mid-hand, or a duplicate event is detected. Without a clear rollback path, player balances and agent ledgers diverge — the fastest way to burn trust with finance and support.
How to design for rollbacks
Treat every wallet mutation as idempotent. Your Seamless endpoints (or Transfer session ledger) should accept a rollback keyed by the original transaction / round id and return success if the reverse was already applied. Never double-credit or double-debit because a callback retried.
Document the happy path and rollback path in the same place your team keeps Swagger samples and the PDF integration guide.
Transfer vs Seamless behaviour
- Transfer: session-scoped balances make some voids easier to reconcile as wallet adjustments at the edge of play, but you still must apply studio-originated reverses correctly.
- Seamless: rollbacks arrive as wallet callbacks; your service must answer quickly and consistently from the MegaNodes region you use (kr / de / ca).
Details on both models: wallet models.
Ops visibility
Use BackOffice game history — bet, win, Bonus Call, timestamps — to investigate disputes after a rollback storm. Agent-scoped RTP and Bonus Call activity should be separable from organic play. Feature map: Features.
Testing checklist
- Replay the same rollback twice; assert a single net effect.
- Void after partial win sequences.
- Confirm reporting timezones match your finance calendar.
- Verify demo daily/session limits never masquerade as production rollback rules.
Need a walkthrough against your middleware: Contact. Commercial context: Pricing.