Product

Send. Confirm. Reconcile.

One canonical JSON sends a payment at any supported bank. The bank confirms it back in real time, so you can tell your customer it cleared without waiting until tomorrow. Incoming payments and balances flow in the same way, so reconciliation is no longer a next-day problem.

What you get

Money out. Status back. Money in.

Send

Payments leave on the exact format each bank expects. You write one canonical JSON. We emit something the bank will actually take.

Confirm

The bank tells us the moment it has accepted or rejected each payment. You can show your customer a live status, instead of making them wait for the next day's file.

Reconcile

Incoming payments and balances flow back daily, or live where the bank supports it. Bookkeeping and liquidity stay current, not a day behind.

Message families we speak
Payments out
ISO 20022 pain.001
Real-time status back
ISO 20022 pain.002
Daily statements
ISO 20022 camt.053
Intraday statements
ISO 20022 camt.052 (at some banks)

Three-level validation

Catch the rejection before the bank does.

Level 1

Schema

Strict validation against the ISO 20022 XSD. Malformed payloads stop at the door.

Level 2

Business rules

Amounts, dates, currencies, IBAN checksums, BIC formats, structured remittance constraints.

Level 3

Bank-specific

Per-bank quirks: allowed characters, required fields, length caps, format combinations.

Delivery channels

Whatever the bank requires. Hardened.

The same channels carry payments out and bring confirmations and statements back in. One pipe per bank, used in both directions.

EBICS

EBICS 3.0 (H005). Payments are signed with A006 (RSA-PSS), or A005 where a bank requires it. Requests are authenticated with X002, and files are encrypted with E002: AES-128 with an RSA PKCS#1 v1.5 key wrap, as the standard requires. Where a bank publishes its key fingerprints, we check its keys against them.

SFTP

Files are PGP signed and encrypted, and an unencrypted file is refused, unless the bank uses its own signing instead of PGP. The bank's host key is pinned, with no trust on first use.

Danske Bank Webservice

Direct integration with Danske Bank's corporate web service.

Nordea CA Webservice

Direct integration with Nordea Corporate Access.

OP Webservice

Direct integration with OP's corporate web service.

Bank Connect

Signature-verified messages over the web service the Danish data centres Bankdata, BEC and NBS share. We connect 34 Danish banks through it.

Approvals & audit

Maker-checker workflow and an append-only audit trail.

Initiated payments enter a controlled state machine. Approvals are scoped per tenant and per policy. Each step, from submission and every approval to the file sent and the bank's answer, is journaled into an append-only event log with an integrity-protected hash chain. Every incoming confirmation and statement file is logged there as it arrives. Built so your customer's auditor doesn't have to ask twice.

Security controls inventory →

Want to see the API?