Integrations

Connects to the payment infrastructure you already operate

Pre-built connectors for PSPs, acquirers, banking statement feeds, and ERP export formats. If your stack isn't on the list, our integration team builds custom connectors — typically in two to four weeks.

Pre-built connectors

Connector availability for your specific PSP and acquirer stack is confirmed during the scoping call. Most pre-built connectors go live within one to two hours of credential setup.

PSPs & Payment Gateways
AcqPay International
Clearstream EM
VoltSettle
NeoPay Gateway
PegasusPay
Acquiring Banks & Local Rails
BancoPay Brazil
NigeriaAcquire
IndonesiaSettle
MexicoNet PSP
KenyaFinPay
Banking & Treasury Feeds
BankLink API
TreasuryStream
CashPositionFeed
MT940 Import
SWIFT gpi listener
ERP & Accounting
Aeris ERP
LedgerSync
NetSuite-compatible export
SAP IDOC format
QuickBooks Online API

Custom connectors for enterprise

If your PSP or acquirer isn't on the pre-built list, Txnworks' integration team builds a custom connector against your exact settlement file format — including normalization to the canonical transaction model, FX rate mapping, and tolerance rule configuration. The connector is tested against a sample of your live data before production cutover.

REST API SFTP/CSV ISO 20022 XML SWIFT MT940/942 Proprietary PSP
Talk to our integration team
Typical Custom Connector Timeline
Week 1
Format analysis — review sample files, map fields to canonical model, document edge cases
Week 2
Connector build — normalization logic, FX rate mapping, tolerance rule configuration
Week 3
Testing with live data sample — match rate validation, edge case review with your ops team
Week 4
Production deployment — monitoring for first 72h, match rate sign-off

Not sure if your stack is covered?

Tell us your PSP and acquirer stack. We'll confirm connector availability before your scoping call — and flag any custom work needed before you commit.