AI writes integration code in days. Bank verification still takes months.

One API, all the banks

ISECure is already in production with the supported Finnish banks, so your team doesn't repeat the bank-by-bank verification. Your product sends payment files and fetches statements through one API. We run certificate renewals, keys, and the bank connection in a hardened, PCI DSS level environment, outside your product's security boundary.

Built for software companies: accounting, ERP, invoicing, and finance products that need bank connectivity.

  • 700+ companies use the API directly

Over 10 years of reliable bank connectivity

Fennoa
Briox
Graphia
Hostingpalvelu
Secureaction
Joutsen Rahoitus
Talokeskus
acFakta

From first test file to live bank traffic

Explore all products →

Exchange bank files and manage certificates.

  • Test environmentRegistration required · No subscription required · Open registration
  • ProductionRegistration required · Paid subscription required · Standard onboarding

Prepare, validate and approve payment files for Nordea, OP, Danske Bank, Säästöpankki, Oma Säästöpankki, Ålandsbanken, POP Pankki and Aktia. Verification of Payee (VoP) included for Nordea, OP and Danske Bank.

  • Test environmentRegistration required · Paid subscription required · Request access
  • ProductionRegistration required · Paid subscription required · Standard onboarding

Test bank-file workflows with synthetic accounts and payment feedback. Automate scenarios through the Bank Simulator API.

  • Test environment onlyRegistration required · Paid subscription required · Request access

Get started

First test call in three steps

In the test environment, create a test account, enroll bank simulator, and download the seeded camt.053.001.02 statement before production bank agreements are finalized.

  1. Open the API or install an SDK

    Use the OpenAPI description directly, or start with the TypeScript, Python, C#, or PHP client.

  2. Create a test account

    SDK registration against the test endpoint creates the account and returns the integrator API key for later calls.

  3. Enroll the simulator and download a statement

    Enroll the simulator certificate, log in with the data account, list the NEW camt.053.001.02, and download its returned file reference.

Coverage

Supported banks

ISECure connects the same integration model to banks such as Nordea, OP, Danske Bank, S-Bank/LähiTapiola, and Ålandsbanken, plus Aktia, POP Bank, Savings Bank, and OmaSP through Samlink and Crosskey connections. Bank files pass through the service without file-type-specific filtering or processing.

Aktia logo
Ålandsbanken logo
Danske Bank logo
Nordea logo
OP logo
POP logo
S-Pankki logo
SEB logo
Samlink logo
Crosskey logo

Integration model

Why this is simpler than bank-by-bank integrations

Bank connectivity is more than uploading a file. A production-ready integration needs certificates, bank-specific behavior, account management, permissions, audit trails, error handling, and secure key management.

Launch without months of bank-specific code

Start with the test API, send and retrieve bank files through one model, and add banks without another integration project.

Certificates and keys off the product team

ISECure handles PKI certificate enrollment, renewals, import/export, and KMS-encrypted storage in a PCI DSS level system.

Less exposure and compliance surface

The bank connection runs as a separate hosted service on AWS PCI DSS certified components. Your team does not have to build its own certificate vault, bank-connection monitoring, or high-security interface.

SDKs, OpenAPI, and PGP security

TypeScript, Python, C#, and PHP clients speed up implementation. File material can require PGP signatures, and customer keys can be exported only to the customer's PGP key.

Architecture

What happens in the integration

Developers send and retrieve bank files through the API. ISECure handles bank WS traffic, certificates, key storage, and operational monitoring.

1
Application
3
ISECure WS-Channel API
4
Banks and WS-channel

ISECure Adminv1.0.15

Administration app for integrators

Manage customer accounts, monitor certificate expiry, and see the usage and license figures behind billing. Sign in with your ISECure administrator account.

  • The macOS installer is signed with ISECure Oy's Developer ID and notarised by Apple.
  • The Windows installer is not yet publisher-signed, so Windows may show an unknown publisher warning.
  • Automatic updates on both macOS and Windows are verified with a digital signature.

Application views with synthetic example data. No real customer information. Select an image to enlarge it.

Pricing

Bank Connectivity pricing

A fixed base fee plus per-bank-account licenses. No transaction or volume fees.

From

38 € / month

Includes the base fee and 10 bank account licenses.

Bank connectivity for the price of a broadband line.

  • Free test environment and SDKs
  • All supported banks at the same price
  • Certificate lifecycle and renewals included
  • No transaction or volume fees
Base fee

Fixed monthly fee for the service.

18 € / month
Bank account license

Licenses are sold in packages of 10 accounts.

2 € / account / month
Production onboarding

One-time fee for new customer production onboarding.

200 €

Example: 20 bank accounts = 18 € + 40 € = 58 €/month.

Annual billing · Account licenses in packages of 10 · VAT added on top

FAQ

Frequently asked questions

What do we need for testing and production?

You can start with the test environment, OpenAPI description, and bank simulator. A fresh simulator enrollment creates the first camt.053.001.02 statement for listing and download. Production still requires the bank's corporate agreement, bank credentials, and certificates; ISECure handles the technical API, certificate process, and onboarding.

Which file types are supported?

ISECure does not filter or process bank files by file type. In practice, the same model supports the material allowed by the bank, including pain.001 payments, camt.053 statements, and other bank-specific WS-channel file types.

Can we use the SDK without vendor lock-in?

Yes. The API supports certificate import/export, and the customer's private key can be exported only to the customer's PGP key.

How is certificate renewal handled?

ISECure handles the PKI certificate lifecycle, renewals, and KMS-encrypted storage in a PCI DSS level system, so the product team does not have to build its own certificate vault.

How does pricing work?

The base fee is 18 €/month and bank account licenses are 2 €/account/month. Licenses are sold in packages of 10 accounts. New customer production onboarding is a one-time 200 €. Billing is annual, and VAT is added on top.

Where are data and keys hosted?

The service runs on AWS with PCI DSS certified components. Keys are stored with KMS encryption, and the bank connection runs as a separate hosted service from the customer software team.

Your message

How can we help?

Name is required and can only contain letters
Please enter a valid email address
Message must be at least 10 characters long