Payment reconciliation for cross-border merchants

Reconcile every cross-border payment. Recover what's leaking.

Txnworks matches authorizations against local settlement rails in real time — flagging the FX mismatches, delayed remittances, and missing credits that cost emerging-market merchants 3–5% in silent revenue.

Abstract visualization of cross-border payment settlement flows between market corridors — glowing network nodes representing Brazil, Mexico, Nigeria, Indonesia, and Philippines with teal and cobalt flow lines on deep navy background

Your PSP dashboard shows accepted. Your bank shows less.

3–5%
Silent revenue leakage
in cross-border corridors
$28B+
Annual cross-border discrepancy
(industry estimate)
72h
Average lag before
manual detection

From raw data to resolved exceptions in minutes

Step 1

Ingest

Connect PSP, acquirer, and bank feeds via API or SFTP. CSV, ISO 20022 XML, and proprietary PSP formats all supported. Median setup: 2 hours per source.

Step 2

Match

Real-time four-way matching: authorization × capture × settlement × bank credit. Corridor-specific tolerance rules handle local rail behavior from Pix to M-Pesa.

Step 3

Alert

Instant exception flagging with root-cause classification — FX mismatch, settlement delay, missing credit — and suggested resolution actions, ranked by financial impact.

A reconciliation engine built for the complexity of emerging markets

Four-way matching

Authorization, capture, settlement, and bank credit matched in one pass

30+ local rail support

Pix, SPEI, NIP/NIBSS, GPN/Snap, M-Pesa, UPI, InstaPay, PSE — settlement rules built in, not bolted on

Real-time exception alerts

Mismatches flagged within 90 seconds of settlement file receipt

FX variance tracking

Authorized-vs-settled FX rate deviation tracked per transaction

Waterfall reporting

Authorized → captured → settled → credited waterfall by corridor

Trusted by payment ops teams at cross-border merchants

We were losing track of settlement timing differences across five PSPs in three markets. Txnworks collapsed that into a single exception queue — our team handles the same volume with a third of the manual work.

Sofia Reyes
Head of Payment Operations · Veloxa Commerce

The FX mismatch flagging alone paid back the cost in the first month. We found a systematic 0.2% rate deviation in our Brazilian corridor that nobody had caught.

David Okafor
VP Treasury · Meridian Marketplace

Plugs into the payment stack you already run

AcqPay International
Clearstream EM
VoltSettle
NeoPay Gateway
BankLink API
Aeris ERP
LedgerSync
TreasuryStream
MT940 Import

Ready to close your reconciliation gap?

Request access and our team will map your corridors, PSPs, and exception volume in a 30-minute scoping call.