Product

One API in. Valid bank payments out.

BankConnector ingests one canonical JSON, validates it three ways, translates it into the bank's expected ISO 20022 dialect, and delivers it over the channel that bank requires, signed, encrypted, and acknowledged.

ISO 20022

pain.001 generation across every supported bank dialect.

ISO 20022 is a standard. Every bank's interpretation is not. We maintain a per-bank profile that knows which fields are required, which formats are accepted, and which combinations will be silently rejected. You write JSON. We emit XML the bank will actually take.

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/BIC checksums, 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.

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. Built so your customer's auditor doesn't have to ask twice.

Security controls inventory →