Payment Reconciliation for High Risk Merchants in Asia: How to Match Deposits, Payouts and Settlements
Most operators compare payment providers on approval rates, rates and country coverage. Few ask how they will prove, line by line, that every deposit, payout and settlement adds up. Reconciliation is where finance teams spend their time and where small disagreements with a provider turn into frozen balances and long email threads. This guide explains what to match, what usually goes wrong, and what to ask for in writing before you choose a provider for Asia-facing traffic.
Why reconciliation is harder in high risk Asia
A single deposit can touch four systems: your cashier, the provider, a local rail such as UPI, QR or bank transfer, and a bank account that finally receives the money. Each system keeps its own reference and its own clock. On top of that, high risk flows often run through several accounts and several providers, so one operator may need to reconcile many partial settlements per day. If the references do not line up, nobody can say quickly whether a missing amount is a failed payment, a delayed one or a real loss.
The references you need to store
Treat these as mandatory fields in your database for every transaction:
- Your order ID, created before the player pays.
- The provider payment ID, returned when the order is created.
- The rail reference, for example the UPI reference number in India or the bank transfer reference elsewhere.
- The settlement batch ID, once the provider includes the transaction in a payout to you.
- Timestamps for creation, success and settlement, with time zones noted.
Without the rail reference you cannot trace a disputed deposit to the bank. Without the batch ID you cannot tell which payout contained it.
One key does not fit every rail
India is a useful example because people mix up the terms. Cashfree explains that a UTR (Unique Transaction Reference) identifies a bank transfer, that RTGS references are 22 characters long, and that a UPI payment carries a 12 digit numeric reference known as the RRN. Finance teams use these references to match bank statement lines to payment records, and the settlement UTR to match a gateway payout to a bank credit. Terra Insight, writing about UPI settlement reconciliation, goes further and says the UPI reference in the bank narration is the primary match key for UPI credits, and that a UTR is not the right key for those lines.
The practical lesson: do not build one matching rule for everything. Decide per rail which field is the key, and write it down.
| Rail type | Typical matching key | Common trap |
|---|---|---|
| UPI deposit | 12 digit UPI reference, plus amount and date | Using a bank UTR that does not exist for that line |
| Bank transfer (IMPS, NEFT, RTGS) | Bank reference or UTR, plus amount | Payer types a wrong or missing reference |
| QR or wallet deposit | Provider payment ID mapped to the rail reference | Wallet shows success while the provider is still pending |
| Provider payout to you | Settlement batch ID and settlement UTR | Batch total differs from the sum of line items |
For QRIS in Indonesia, VietQR in Vietnam, GCash in the Philippines or bKash in Bangladesh, the field names differ, so ask each provider to show a sample file that maps its reference to the local one.
The usual causes of mismatches
Terra Insight lists causes that apply well beyond UPI. Check them in this order:
- Failed or abandoned payments. Your system shows an attempt but no money arrives. These stay open until the failure is confirmed, so expire pending orders on a fixed schedule instead of leaving them forever.
- Timing. Money may reach the provider on one day and reach you in a batch on the next, so bank dates and transaction dates differ. Reconcile by settlement batch, not by calendar day alone.
- Refunds and reversals. A refund can appear as a separate bank debit, or be netted against a batch credit. Link every refund to the original transaction.
- Fees and rounding. Deductions reduce the settled amount, and small rounding differences can add up across many batches. Ask for fees shown per transaction, not only as a monthly total.
- Duplicate callbacks. If your system credits a player twice because a webhook was delivered twice, your ledger will exceed what the bank received. Make crediting idempotent on the payment ID.
A simple three-step process
Step 1, match at transaction level. Every day, compare your successful orders to the provider's transaction report using the payment ID and amount. Investigate every row that exists on only one side.
Step 2, match at batch level. Compare each provider settlement batch to the bank credit using the settlement reference. The batch total, minus fees and reserve deductions, should equal the credit.
Step 3, age the exceptions. Keep a list of unmatched items with an owner and an age. Anything older than a few days should be escalated to the provider with the references attached.
What to ask a provider before signing
- Can you export a transaction file and a settlement file with the same payment ID in both?
- Is the rail reference (such as the UPI reference) included in the transaction file?
- Are fees and any rolling reserve shown per transaction or per batch, and where?
- How do you report pending, failed and reversed items, and how long until a final status?
- Do you offer an API or status check for payments whose callback never arrived?
- How fast do you answer a reconciliation query, and through which channel?
A provider that answers these clearly, with a sample file, is usually easier to work with when something goes wrong.
FAQ
How often should we reconcile? Match transactions daily and settlement batches whenever a payout arrives. Daily checks keep exceptions small and recent, which makes them far easier to resolve with a provider.
Is a spreadsheet enough? At low volume, yes, if the keys are clean. As volume grows, move to a script or tool that matches by payment ID and flags unmatched rows automatically.
Who is responsible for a mismatch, us or the provider? It depends on the cause and on your contract. That is why the references, timestamps and status history should be agreed in writing, so each side can see the same record.
About BestPay24
BestPay24 is a high risk payment gateway for businesses serving Asian markets. There is no setup fee and no prepayment. If you want to see how transaction and settlement references are reported before you commit, message us on Telegram at @Bestpay24SalesSupport and ask for the details in writing.
Sources: Cashfree (what a UTR number is and how UTR, RRN and settlement UTR are used), Terra Insight (UPI settlement reconciliation).
BestPay24 collects and pays out in twelve Asian countries for betting, casino, forex and digital merchants. No setup fee.
Message @Bestpay24SalesSupportMore articles
Hosted Payment Page vs Direct API vs Payment Links: Choosing an Integration Model for High Risk Merchants in Asia
A buyer guide comparing the three ways to connect a payment provider, what each means for compliance scope, callbacks, reconciliation and launch speed, and which fits a sportsbook, casino or forex broker.
Rolling Reserve vs Fixed T+1 vs USDT Settlement: Comparing Settlement Terms for High Risk Merchants in Asia
A buyer guide to the three settlement structures high risk operators are offered in Asia, how each affects cash flow and reconciliation, and which questions to put to a provider before you sign.
NAPAS 247 vs Standard Clearing for High Risk Payouts in Vietnam
A decision guide for operators paying out in Vietnam: how instant 24/7 transfers differ from standard interbank clearing since the 500 million VND instant cap and the end of automatic splitting, and how to design payouts around it.
Ready to accept local payments in Asia?
Tell us your vertical, countries and volume. You get an offer with rates and settlement terms, usually the same day.