For end customers
Connect your own banks. Into your own systems.
Direct host-to-host connectivity to your banks, through one API. No bank-by-bank integration projects. Your team handles the setup once, and we walk you through every step for every bank.
Built for teams who can integrate an API.
If your team can call a REST API, you can run BankConnector yourselves. You connect directly to your own banks, under your own credentials, with full control over accounts, approvals, and data.
Bank setup
Every bank has its own process. We know all of them.
Some banks need just a user ID and an activation code. Others need signed documents, key exchanges, and a specific email to a specific team. When you set up a bank connection in BankConnector, you get step-by-step instructions written for that bank, not generic documentation.
Bank-specific, not generic
Instructions tailored to your exact bank and connection type. What to do, what to send, and who to send it to.
Keys handled for you
PGP and SSH key generation happens inside the platform. You get the public keys ready to send, we keep the rest safe.
Live once the bank confirms
Once the bank registers your keys, typically a few days, your connection is active and your first payment can go.
The payment loop
Send a payment. Know what happened. Close the books.
01
Send
Your payment is submitted to the bank over your direct host-to-host channel.
02
Confirm
The bank sends back an acceptance or rejection. You know immediately, not at tomorrow's reconciliation.
03
Notify
Intraday notifications arrive as transactions clear through the day.
04
Reconcile
End-of-day statement pulled automatically and matched to your outbound payments.
Rejections come back with the bank's reason. See them in the platform, receive them via webhook, or poll for new files, whichever fits your workflow.
Controls
Approval workflows your finance team will actually trust.
Payments don't move without the right sign-off. Configure the rules once. They're enforced server-side on every payment, not just in the interface.
Maker-checker
The person who submits a payment cannot be the same person who approves it.
Amount limits
Set per-payment and per-batch thresholds. Anything above requires additional sign-off.
Multi-level approval
Require more than one approver above certain amounts. Configure the chain to match your internal controls.
Fail-closed
If the approval flow is unreachable, the payment does not leave. There is no override path.
Support
You won't be doing this alone.
The platform guides you through every step of your bank setup. The docs cover every endpoint. And when you want a person, we are here: during the key exchange, on your first live payment, or six months in.
Talk to us →Try it against a simulated bank, right now.
No signup. No credit card. Provision a sandbox and send a payment in a few minutes.