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.
Three-level validation
Catch the rejection before the bank does.
Schema
Strict validation against the ISO 20022 XSD. Malformed payloads stop at the door.
Business rules
Amounts, dates, currencies, IBAN/BIC checksums, structured remittance constraints.
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 H005 with RSA-OAEP key exchange and HPB fingerprint verification.
SFTP
PGP sign + encrypt fail-closed. Host-key pinning. No anonymous trust.
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 bank's managed pipe. Covers 60+ Danish banks via BEC, SDC and Bankdata, including 14 of the 16 largest.
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. Every state change is journaled into an append-only event log with an integrity-protected hash chain. Incoming confirmations and statements are journaled the same way. Built so your customer's auditor doesn't have to ask twice.
Security controls inventory →