How it works
- 1
Send canonical JSON
One payment instruction shape for every bank. BankConnector validates it (structure, generic rules, the bank's rules, the payment type's rules), applies the customer's saved bank settings, converts it to the pain.001 flavour the target bank expects, and queues it for delivery.
- 2
Delivered over the bank's own channel
EBICS, SFTP, or the bank's own web service (Danske Bank, Nordea, Bank Connect, OP), under the customer's own bank agreement and keys.
- 3
Results come back normalised
The bank's status reports (pain.002) and statements (camt.052, camt.053, camt.054) arrive in one shape, through the API and through webhooks signed with HMAC-SHA256.
- 4
Retries are safe
The messageId is the payment's identity: sending the same instruction again returns the original answer instead of making a second payment.
How your customers fit in
Each of your customers is its own company in BankConnector, with its own bank agreements, users, approval policy and API keys, isolated from every other company. A company comes into being when its own people sign up, and an API key belongs to one company and cannot reach another, so your product works with each customer's key on that customer's behalf.
The payments leave the customer's own bank account, signed with the customer's own keys. BankConnector moves the instruction, never the money, and holds no funds.
Approvals and security
Every payment is governed by the customer's approval policy, and by default every payment needs approving before it is sent. Approvers who use two-factor authentication confirm each approval with a fresh code, and the customer's admins can require it for everyone. Controls, documents and how the platform is assessed are on the security page.
Try it
The sandbox is free and unlimited: a first payment takes about five minutes with the getting-started guide. The API is described in OpenAPI 3.1 in the developer docs, and 351 banks in 55 countries are on the list of supported banks.
What it costs
Embedding is priced for your volume and the way you sell to your customers, so there is no public price list: tell us about your product and we put together a proposal.
More questions
Does the money pass through BankConnector or through our product?
No. Payments leave the customer's own bank account under the customer's own bank agreement. BankConnector moves the instruction, never the money, and is not a bank.
Do we need to write ISO 20022 XML?
No. You send a bank-agnostic JSON instruction; BankConnector produces the pain.001 each bank expects and reads the pain.002 and camt files back into one shape.
Host-to-host or open banking?
BankConnector uses the banks' host-to-host channels, which are made for payment runs and statements every day. Open banking (PSD2) APIs were built for apps that read accounts and start single payments, with access a person has to renew at intervals.