Every bank and system relationship, connected once.
SFTP and direct API connectivity for both banks and internal systems — configured, tested, and monitored from one place.
Bank connector & system connector
Two sides of the same connectivity model — connecting out to your banks, and connecting into your own systems.
Bank SFTP
Connect out to a bank's SFTP server, or host your own server-mode endpoint for banks to connect into — both directions supported, with directory-level configuration for incoming and outgoing files.
Bank API
Where a bank exposes a modern API, connect directly — no file exchange required.
System SFTP
SFTP endpoints used to exchange files with internal and ERP systems — the same server-mode or client-mode flexibility as bank connectivity.
System API
API keys and integrations with internal, ERP, and third-party systems.
SFTP and API are what's enabled today for both bank and system connectivity — more connection methods can follow as they're needed.
From configuration to a working connection
-
Configure the connection
Set host, credentials, and per-connection settings for SFTP or API, on either the bank or system side.
-
Test it for real
Run an actual connectivity test against the configured endpoint before relying on it — not a saved form with no verification.
-
Match the format
Incoming statement formats (MT940, MT942, BAI2, CAMT.052/053/054, CSV) and outgoing payment formats are matched automatically to what each side expects — no manual reformatting.
-
Automate the flow
Statements pull in and reconcile automatically; payment files transmit and get tracked through to bank acknowledgment.