Skip to content

PSP operations

Payment Reconciliation for PSPs: Acquirer to Merchant

A PSP sits between two sets of money. Acquirers pay it for its merchants' card payments, and it pays merchants their share. Reconciliation proves the two sides agree. Every payment the gateway processed should be settled by an acquirer and arrive in the bank, and every merchant should get the right amount.

When reconciliation runs daily, small errors stay small. When it runs at month end, a missing settlement or a fee charged at the wrong rate has already repeated for weeks. This page covers payment reconciliation for PSPs from the acquirer file to the merchant payout.

The three matches in payment reconciliation for PSPs

PSP reconciliation is really three matching jobs, each comparing two records of the same money. A break in any one of them means money is missing, late or misallocated.

Match Compares A break usually means
Transactions to acquirer reports The gateway's captured payments against each acquirer's settlement file A payment captured but not settled, or settled twice
Acquirer reports to bank Settlement amounts in the files against deposits in your bank account A late, short or missing deposit
Merchant payouts to ledger What each merchant was paid against what the ledger says it was owed A fee, reserve or refund applied wrongly

Many PSPs add a fourth check on fees. That's where the acquirer's charges are tested against the contract, and it's the check that finds margin.

Fee reconciliation against acquirer contracts

An acquirer's settlement file lists what it deducted, from interchange and scheme fees to its own markup. Fee reconciliation recalculates the markup from the contract and compares it with what was charged, transaction by transaction or in daily totals.

Here's a hypothetical example. In a month, a PSP settles $1,000,000 through an acquirer whose contract sets a markup of 0.20%, so the expected markup is $1,000,000 x 0.20% = $2,000. The acquirer's file shows $2,350 charged, a $350 gap. The cause might be a wrong rate on one card type, a fee the contract doesn't list, or transactions put in the wrong category, and each needs a different fix.

A fee reconciliation platform for acquirers and PSPs does this calculation every day, so a $350 monthly gap is found in its first week rather than at the quarterly review.

Reconciliation across several acquirers and currencies

Each extra acquirer adds a file format, a payout schedule and a set of fee lines. Each extra currency adds an exchange rate, often applied on a different day from the payment. The setup below keeps that manageable.

  1. Load every acquirer's settlement file into one normalized format.
  2. Give every payment attempt one internal ID that follows it through retries, routing and settlement.
  3. Record the exchange rate, its source and its date for every currency conversion.
  4. Match on the internal ID first and on amount and date only as a fallback.
  5. Allow for timing, since a payment captured today may settle two or three business days later.
  6. Send everything unmatched to an exceptions queue with an owner and a deadline.

The second step does most of the work. Without one ID across acquirers, a payment that was declined by the first acquirer and approved by the second looks like two payments, and the reconciliation shows a break that isn't real.

Common reconciliation breaks

Most breaks have ordinary causes. Naming them speeds up the exceptions queue. Timing differences are the most frequent, because a payment captured late on Friday may not appear in the acquirer's file until Tuesday, and the gap then looks like a missing settlement for two full business days until the file catches up.

Partial captures and refunds spread over several days come next, along with chargebacks that are later reversed. Currency differences show up when the rate applied at settlement differs from the one shown at checkout. Real losses, such as a settlement that never arrives, are rarer, which is exactly why they're easy to miss in a queue full of timing breaks.

Reconciliation software for payment acquirers and PSPs

Our platform matches transactions across providers automatically and tracks settlement without manual work. Each payment attempt carries a single internal ID that survives retries and links the provider response, fees, settlement and your ledger.

On the merchant side, the merchant management system reconciles payouts against processed volume, so the settlement each merchant receives traces back to its transactions. Reports from every provider come into one dashboard, and exports go to your accounting system.

Questions

What is payment reconciliation for PSPs?

Matching a PSP's processed transactions against acquirer settlement files, those files against bank deposits, and merchant payouts against the ledger, so every amount is accounted for.

How often should a PSP reconcile?

Daily, at least for the transaction and bank matches. Monthly reconciliation lets errors repeat for weeks before anyone sees them.

What is fee reconciliation?

Recalculating the fees an acquirer should have charged under its contract and comparing them with the fees it actually deducted, to find wrong rates or unexpected charges.

Which reconciliation setup suits several acquirers and currencies?

One normalized format for all acquirer files, one internal ID per payment attempt across acquirers, recorded exchange rates with dates, and an exceptions queue for anything that doesn't match.

See reconciliation on the platform

Bring a settlement file from one of your acquirers, and we'll show how it's matched on the platform.