For SaaS & ERP vendors
Give your customers their own bank connection, without becoming a payments company.
One API. Every bank your customers use. Your product stays in front, your brand stays on it. First payment in five minutes in the sandbox. A real bank goes live once the key exchange clears.
How it works
You own the customer. We own the banks.
Your customers never leave your product. You call our API, we handle every bank format, channel negotiation, and certificate exchange. One contract with us replaces a bank-by-bank project for every customer you onboard.
300+ banks across 58 countries, already connected
One JSON shape regardless of which bank it's going to
Status and statements back in the same API
Your product
ERP · SaaS · Custom software
BankConnector API
One integration · All banks
Bank networks
EBICS · SFTP · Host-to-host · WebService
Choose your depth
Embedded or self-service. Your call.
Both paths run on the same API and the same bank connections. The difference is who drives the experience.
Option A
API-first
Your product calls our API with platform-scoped keys. You headlessly provision companies and users, submit payments, read statuses and statements. Your customers never see BankConnector. It runs inside your product.
- Full control over the user experience
- M2M authentication with API keys
- Headless company and user provisioning
- Webhooks for every payment event
Option B
Branded portal
Your customers log in at your subdomain. BankConnector runs the full self-service experience under your name: approvals, reconciliation, statements, and user management.
- Your subdomain, your brand name
- Full payment and approval workflow included
- Users manage their own bank connections
- No frontend to build or maintain
The operator layer
See everything happening across all your customers.
Every bank interaction is logged, and every payment is traceable from submission to bank confirmation. Rejections surface as soon as the bank sends them. All of it stays isolated per customer, and visible to you.
Companies
Every customer you onboard in one list. User counts, bank connections, live or onboarding status. Add a company with one API call.
Operator logs
Every bank-channel interaction with timestamp, return code, bytes, and outcome. 90-day retention. The first place to look when something fails.
Rejections
Rejected payments surfaced across all customers. Raw bank response included. Know why a payment failed before your customer asks.
API keys
Issue, rotate, and revoke platform-scoped keys. Rotation is issue-new and revoke-old, with no downtime and no coordination with us.
Webhooks
Subscribe to every payment event. Delivery log, redeliver on failure, rotate the signing secret. HMAC-verified.
Go-live readiness
A checklist and readiness score before you flip to production. Users, approvers, policies and connections are all confirmed before a real payment moves.
The customer experience
A complete banking interface. Nothing to build.
Your customers get a full payment workflow the day they connect their bank. You get none of the support overhead of building it.
Payment submission
Submit individual or batch payments. One JSON shape to every bank.
Approval workflows
Maker-checker enforcement. Nothing moves without the right sign-off.
Statement import
Bank statements pulled automatically. No manual downloads.
Reconciliation
Outbound payments matched to bank confirmations automatically.
User roles
Admin, Approver, Viewer. Set once, enforced everywhere.
Activity log
Every action recorded. Hand it to an auditor without preparation.
Webhook configuration
Your customers can subscribe to their own payment events.
Getting started
First payment in five minutes.
The sandbox needs no signup. Two API calls and you have a provisioned company, a live connection, and a confirmed payment.
Provision
One call to /sandbox/provision. Platform, company, users, and an active bank connection are all created, and the API key is returned.
Send
POST /journal/payments with your payment details. One JSON shape regardless of bank.
Confirm
pain.002 confirmation and camt.053 statement back in around five seconds. Reconciliation closes automatically.
Real banks take longer
A real bank connection requires a key exchange. You send the bank your public keys and they register them on their side. Typically a few days. We walk you through every bank.
120 operations. All documented.
Every endpoint, every error, every field. The docs are live at docs.bankconnector.com, with no signup to read them.
Support
Ship it without becoming a payments support desk.
When a bank rotates a certificate, rejects a payment, or asks for a new document, that lands with us, not your support queue. You integrate once and ship the feature. The bank complexity stays ours, for every bank and every customer you onboard. And when you want a human, we're here.
Talk to us →Offer bank integration as if you built it.
Every bank your customers use, one integration, under your brand. If your product would be stronger with a bank connection inside it, let's talk.