Connect any software to hundreds of banks.
Pay suppliers, approve the payments and reconcile your bank statements from inside your own ERP, without opening online banking. BankConnector connects it to your banks in the background.
230 banks in 17 countries, ISO 20022 native
Inside your own system
Everything happens in the ERP you already use.
You pay suppliers, approve the payments and reconcile your bank statements inside your own ERP or accounting system. You never have to open online banking for it. BankConnector does its work in the background.
Your ERP system
Where you already work
Works in the background
Its web app is for the one-time setup
- Danske Bank
- Nordea
- DNB
- HSBC
Your banks
Where the payments are made
Pay suppliers
Validate the payment journal and send it to the bank. The bank's answer comes back on every line.
Approve with two-factor authentication
Approvers see who gets paid and how much, and approve right where they work. In the Uniconta add-on every approval takes a code from an app on their phone; elsewhere it does whenever they use two-factor or you require it.
Statements arrive by themselves
Bank statements come into your ERP automatically and are matched to your open invoices.
No online banking login, no payment files to upload.
You use the BankConnector web app for the setup you do once: connecting your banks, setting the approval rules and adding the users.
What you ship
Six capabilities, one integration.
Send payments
Get money out the door at every supported bank from one integration. One JSON in, valid bank-ready payment out.
Real-time confirmation
Know the moment a payment is accepted or rejected by the bank, instead of finding out at tomorrow's reconciliation.
Cashflow visibility
See incoming payments and balances as they land. Daily by default, live where the bank supports it.
Three-level validation
Schema, business rules, bank-specific quirks. Catch the rejection before the bank does.
Secure channels
EBICS, SFTP, Danske Bank Webservice, Nordea CA Webservice, OP Webservice, Bank Connect. Certificate pinning, signed and encrypted end-to-end.
Audit trail
Append-only events, HMAC hash chain, maker-checker workflow. Built for the auditor before they ask.
How it works, for developers
Send one payment. We handle the rest.
Send canonical JSON. One shape, regardless of which bank it's going to.
We convert it to the bank's exact ISO 20022 format and pick the channel.
It's delivered over the bank connection, after approval.
Status and statements come back, normalised, in real time.
Which are you
Build on our API, or use it straight inside your ERP.
ERP add-on
You use Uniconta
Pay suppliers and approve the payments without online banking, right inside Uniconta.
Pay from Uniconta →ERP add-on
You're a Uniconta partner
Say yes to every customer who asks about their bank, and give them first-class bank integration.
For Uniconta partners →API
You build software
Build bank payments into your product under your own name, for all your customers and their banks.
For software vendors →API
You run your own system
One API instead of a project per bank: connect your own systems to all your banks.
Connect your system →Security & Compliance
The questions your CTO is going to ask.
Do you ever hold our customers' money?
No. Payments leave from the customer's own bank account, signed with the customer's own keys. We move the instruction, never the funds.
What happens if you get breached?
Sensitive fields are encrypted per-record, and database access is locked down per customer. A breach of our infrastructure does not expose another customer's data, and it does not by itself let anyone move money, since releasing a payment still requires approval.
Can someone send a payment without approval?
No. Approvals are enforced server-side and fail-closed. If the approval flow is unreachable, the payment does not leave, full stop.
Will an auditor be happy?
Yes. Every action is written to an append-only journal that can be verified end-to-end. You can hand the log to an internal or external auditor without preparing it first.
Where does our data live, and who can see it?
Inside EU infrastructure, isolated per customer. Our staff cannot read customer payment data in the clear, and access to production is gated, logged, and reviewed.
Are you a regulated entity we need to file paperwork on?
No. We are not a bank and not a PSD2 AISP/PISP. You stay in your existing regulatory posture; we are a technology vendor under your standard supplier process.
Ready when you are.
Software platform?
Talk to us →Want to build against it?
Try the sandbox →Just exploring the banks and formats?
Coverage and guides →