Operations Guide · 2026

Casino API reporting: how to reconcile GGR, rounds and wallet every day

Every spin through a casino API leaves two records: the provider’s round and your wallet transaction. When they agree, reporting is easy. When they do not, someone is paying out or being invoiced on numbers nobody can explain. This is how to set up a daily reconciliation that catches differences while they are still small.

The short version

  • Reconcile daily, per provider and per currency, not once a month.
  • Match on transaction ID, not on totals.
  • GGR = bets − wins, calculated on the same basis on both sides.
  • Track open rounds: bets without a result are the usual source of gaps.
  • Keep raw callbacks for as long as your licence requires.

Two ledgers, one truth

The provider records rounds: who bet, how much, what they won. Your wallet records money: every debit and credit with its transaction ID. Reconciliation is proving that the two describe the same activity, line by line.

Through the IGP casino API, rounds, bets, wins, bonus contribution and jackpot events arrive in one normalised stream across all providers, so there is one format to reconcile against your wallet ledger each day instead of one per studio.

The numbers to track

Metric How it is calculated What a gap usually means
Turnover Sum of all bets Missing or duplicated debits
Wins Sum of all credits from rounds Missing credits or late settlements
GGR Turnover minus wins Different bonus or jackpot treatment
Open rounds Bets with no result at the cut-off Timeouts or rounds settled next day
Rollbacks Reversed transactions Retries or cancelled rounds
Actual RTP Wins divided by turnover Normal variance, or a mapping error if the gap is large and persistent

Actual RTP over a day or a week will differ from a game’s theoretical RTP; that is how probability works. Investigate only large gaps that persist across many rounds, and check the game mapping first.

Where mismatches come from

  • Timeouts and retries counted twice on one side. Idempotent wallet calls prevent it.
  • Rollbacks after settlement that one report includes and the other does not.
  • Currency rounding when amounts convert or use different decimal places.
  • Cut-off times in different time zones.
  • Free rounds counted as real bets in one report and not in the other.

Most of these are caught before launch by the tests in our integration checklist.

A daily routine that works

  1. Pull yesterday’s provider data and your wallet ledger with the same UTC cut-off.
  2. Match transaction IDs; list everything that appears on one side only.
  3. Explain open rounds and rollbacks first; they clear most differences.
  4. Compare turnover, wins and GGR per provider and currency.
  5. Escalate what is left to the provider the same day, with transaction IDs.

Frequently asked questions

Gross gaming revenue: total bets minus total wins over a period. Agree in writing how bonus bets, bonus wins and jackpot contributions are treated, because both sides must calculate it the same way.

Usually because of timing and retries: a cut-off at a different hour, rounds still open at the cut-off, retried calls counted twice on one side, or rollbacks applied after the report was taken.

One agreed time zone for both sides, usually UTC. A report cut at local midnight against one cut at UTC midnight will never match.

One stream to reconcile

150+ providers and 18,000+ games through one integration, with every round in one normalised format for daily reconciliation.

See the casino API →