Solutions

Payment reconciliation for online casinos and iGaming operators.

iGaming operators take deposits through dozens of local payment methods, and every provider reports differently. Reconora reconciles your log, provider callbacks and statements every day, finds players who were charged but not credited, and gives you an audit trail your licence reviews can rely on — without sending us any player data.

The pain you already know

A player deposits. The provider’s callback says “declined”, so the balance is not credited. The provider’s statement later says “success”. The player sees the charge and writes to support. Support chases the provider; the provider admits the error — and sends no new callback. The correction arrives as a statement line days later.

That pattern has a name: a reversed outcome. On one anonymised merchant day there were 320 such payments, and it is not the only pattern. A deposit can be settled by a provider and never reach your log. A provider can stop sending statements for a currency without anyone noticing. A callback can arrive twice, or not at all. Each case looks small on its own. Across dozens of providers and local payment methods, they add up to player money that hangs, support tickets that repeat, and turnover nobody can confirm.

What Reconora shows the next morning

  • Players charged, not credited — 320 payments on one measured day, each with its evidence.
  • Credited, never paid — 61 payments where you credited the player and the provider never settled.
  • Settled without a record — 317 payments the provider settled that you have no trace of.
  • Turnover you cannot verify — 10.1% of turnover in the reconciliation scope had nothing to reconcile against; 26 providers sent no statement at all.

Every figure above comes from one anonymised merchant day and is not an industry benchmark. Your own day will have its own mix. Each payment in the result ends in one of four outcomes: matched, differs in money, differs in facts, or nothing to reconcile against. Payments still waiting for a final status are shown separately, not as discrepancies.

A day in the life

The scenario below is synthetic and illustrative. A mid-sized casino takes deposits through Provider A to Provider P, in CUR-1 to CUR-4. On Monday evening a player deposits through Provider F, a local bank-transfer-style method. The callback says declined. The player tries again through Provider C, and that deposit succeeds. On Tuesday morning the player writes to support: “I was charged twice and credited once.” Support cannot see Provider F’s side and forwards the ticket to finance.

With Reconora, the Tuesday result already lists payment PAY-4C1E as a reversed outcome: declined in the log, successful in Provider F’s statement. The discrepancy queue shows the log line, the callback and the statement row side by side. Support answers the player the same morning. Finance adds the payment to Provider F’s claim candidates, with the evidence attached. The same result shows that Provider K sent no statement for CUR-3, so its turnover that day is named as unverifiable rather than assumed fine.

Local payment methods, many providers

iGaming operators rarely depend on one provider. Regional card acquirers, e-wallets, vouchers, bank-transfer-style methods and local instant-payment methods each come through their own payment service provider, often behind an orchestrator. Every provider has its own statuses, amount units, time formats and statement layout. On one anonymised merchant day, the data held 96 providers, 1,198 message shapes and 318 raw status values. In the provider map of the same day, 18 providers carried 90% of transactions and 49 carried the remaining 10%. Each provider in that tail has its own format, contract and statement, and each needs checking. Reconora reads each provider in its native format and translates it into one model. Nobody on the provider side has to change anything. Read more in the multi-provider reconciliation guide.

Support gets an answer in seconds

Type the start of a payment ID and see where the payment is and what happened to it — instead of escalating every “where is my deposit?” to finance.

“Where is my deposit?” is a question every iGaming support team knows well. The honest answer often depends on three sources: your log, the provider’s callback and the provider’s statement. Reconora puts all three in one view, with the outcome and the reason. When the statement has not arrived yet, the payment is shown as awaiting, so support does not promise a refund that is not due.

What to check first

  1. Statement coverage. List every provider and currency, and mark which ones send a statement. Gaps here make the rest unverifiable.
  2. Reversed outcomes. Search for payments declined in your log but successful in a statement. These are the players charged but not credited.
  3. Statement-only payments. Look for statement lines with no counterpart in your log.
  4. Payments with no final status. Count deposits that never received a final callback. On one anonymised merchant day there were 14,191.
  5. The long tail. Check the smallest providers first; they are the least watched.

A free one-day pilot answers all five for one of your own days.

An audit trail for your licence

Every package, approval, claim and rule change sits in a tamper-evident log with five separated roles. Audit trail

Licence reviews often ask how player funds are tracked and how discrepancies are resolved. The audit trail records who accepted each package, who approved each rule change and when each claim was raised. Each entry carries the fingerprint of the previous one, so a change after the fact shows as a break in the chain. Reconora does not make any regulatory claim on your behalf; it gives your team the record to show.

No player data leaves your company

Data flow: anonymised inside your perimeter, reconciled by Reconora, decoded back at your siteYour perimeterLogs and statements are anonymised offlineAnonymised artifactsCodes instead of names, e-mails, cards, providersReconoraReconciles logs, callbacks and statementsResult in codesOutcomes, discrepancies, claim candidatesYour perimeterDecoded with your own table — only you can read it

The anonymisation module runs inside your perimeter, offline. Names, e-mails, card numbers, IP addresses and provider names are replaced with codes before anything leaves. Reconora reconciles the anonymised package and returns the result in the same codes. Only you hold the table to decode it. Your security team can read the module’s full source code first.

Security

Questions

We use a payment orchestrator. Does that work?
Yes. Reconora reads your orchestrator’s log, and end providers behind it are reconciled against their own statements.
Our providers use local payment methods with no standard format. Is that a problem?
No. Each provider is read in its native format and translated into one model. On one measured day that was 96 providers and 1,198 message shapes.
Do you handle chargebacks?
Not today. Reconora reconciles deposits and statements; chargebacks are outside the current product.
Do you reconcile withdrawals to players?
Not today. Reconora reconciles deposits and payments against provider callbacks and statements. Payout reconciliation is outside the current product.
How long does the first result take?
About an hour of machine time for one day. On one measured day it took 63.1 minutes from raw files to the first full reconciliation.
Do you need access to our production systems?
No. You export one day of logs and provider statements, anonymise them at your site and hand over the package. No API integration is needed to start.

Try it on one day of your data

One day of your data, reconciled, and the report stays with you whether or not you continue.

Updated