Solutions

Payment reconciliation for sportsbooks and betting operators.

Betting traffic peaks around events, and a provider failure in that window costs the most. Reconora reconciles every deposit against provider callbacks and statements, shows provider incidents by the hour and separates provider failures from player and bank declines — so your payments team acts on facts, not complaints.

When the match starts, the provider fails

On one measured day, a single provider reached 22.2% technical failures within one hour against its usual zero. Without an hourly view, that hour shows up as player complaints and a vague dip in conversion.

Sportsbook deposits are fast and bunched. Players top up minutes before kick-off, at half-time and before a big race. A provider that slows down or fails in that window can cost deposits at the moment they matter most. The failure is also easy to misread. A rise in declines can mean a provider incident, a bank tightening its rules, or players hitting their own limits. Each needs a different response, and only one of them is the provider’s fault. Reconora separates them, so the payments team knows which provider to call and what to say.

What you get

  • Provider health by the hour — technical failures only; player and bank declines excluded.
  • Declines in one language — 113 provider codes mapped to 22 reasons; 8.7% of declines were the provider’s fault, 6.9% were fixable by the merchant.
  • Stuck deposits found — payments with no final status, reversed outcomes and settlements without a record, each with a reason.
  • Facts for the account-manager call — a dossier per provider with benchmarks and evidence.

The decline figures come from one anonymised merchant day and are not an industry benchmark. On that day, 42.5% of declines could not be attributed to either side from the data alone, and Reconora says so rather than guessing. Every decline reason keeps a link to the provider’s original code.

The provider dossier brings these figures together for one provider: its hourly failures, its decline reasons, its statement coverage and the payments in the discrepancy queue that concern it. Account managers respond to dates, hours and payment references more readily than to a general complaint about conversion. The dossier gives the payments team exactly that, with the evidence behind each line. Provider intelligence

A day in the life

The scenario below is synthetic and illustrative. A sportsbook takes deposits through Provider A to Provider L, in CUR-1 and CUR-2. On Saturday a major match kicks off in the evening. In the hour before kick-off, Provider D starts returning timeouts. Some deposits are retried through Provider G and succeed. Others are left with no final status. Players complain in chat, and the conversion chart shows a dip, but nobody can say which provider caused it.

On Sunday morning the Reconora result shows Provider D’s technical failure rate for each hour of Saturday, with the incident hour clearly marked. Player and bank declines are excluded from that figure. The discrepancy queue lists the deposits that never received a final status, and two payments where Provider D’s statement later shows success while the log shows a failure. Those are reversed outcomes: players charged, not credited. The payments team opens the provider dossier, sees the evidence by hour and row, and takes it into the Monday call with Provider D’s account manager.

Peaks, fast deposits and retries

Betting payments have a shape of their own. Volume arrives in waves around events. Players retry quickly when a deposit fails, often through a different method. A single attempt can therefore produce several log lines, several callbacks and, sometimes, two successful charges where the player wanted one. Providers also resend the same notification during load, so repeated messages must be counted once, not twice. On one anonymised merchant day, 401,255 repeated observations of the same facts were folded rather than counted again. Late events push deposits across midnight, onto the day edge, where the statement for the next day will carry them. Reconora marks those as awaiting, not as missing. The multi-provider reconciliation guide explains how many providers and formats are brought into one model.

What to check first

  1. Hourly failures by provider. Look at event days, not average days. Incidents hide inside daily totals.
  2. Deposits with no final status. On one anonymised merchant day there were 14,191 payments with no final status.
  3. Reversed outcomes after peaks. Check payments declined in the log but successful in the statement for the event hours.
  4. Statement-only payments after retries. Look for statement lines with no counterpart in your log during event hours.
  5. Statement coverage. Confirm every provider and currency sends a statement; on the same day 26 providers sent none.

A free one-day pilot runs these checks on one of your own event days.

No customer 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 receives only the anonymised package and returns the result in the same codes. Only you hold the table to decode it, and your security team can read the module’s full source code first. Nothing in the pilot requires access to your production systems or an API integration: one day of log exports and provider statements is enough to start. Security

Questions

Can we see incidents in real time?
Today Reconora works on daily packages, so incidents are visible the next morning with exact hours.
Do you replace our payment orchestrator?
No. Reconora reads what your orchestrator logs; routing stays where it is.
Can you tell a provider failure from a player’s bank declining?
Yes, where the data allows. Provider codes are mapped to one set of reasons, and technical failures are separated from player and bank declines. Declines that cannot be attributed are shown as unproven, not guessed.
Do you reconcile payouts of winnings?
Not today. Reconora reconciles deposits and payments against provider callbacks and statements. Payout reconciliation is outside the current product.

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