Early access · working name

One API for normalized corporate banking data — with evidence back to the original bank file

ISECure's File Exchange API already handles bank connectivity, certificates, and secure file transfer. This adjacent API solves the next problem: it turns authorized bank files into developer-friendly business resources while preserving exact source lineage.

Request early access The existing File Exchange API remains unchanged.

The integrator's pain

File connectivity is solved — but every bank file still becomes a custom content integration

Once files move, the work isn't over. Every bank file turns into a custom integration: parsing ISO 20022 content, bank-specific profiles, statuses, and exceptions — all interpreted by you.

That ties up developer time and produces brittle, per-bank implementations you have to maintain and audit separately.

How it works

Bank file → normalized data → your application

The API converts supported ISO 20022 content into normalized business resources and attaches evidence to every value: a link back to its source file and ISO 20022 field.

1 Bank file (e.g. camt.053)
2 Normalized data + evidence
3 Your application

What you get

Concrete API outputs

Statements, balances, entries, and transactions as REST/JSON
Business-readable validation errors and exceptions
Payment status and lifecycle when supported by bank evidence
A link from every normalized fact back to its source file and ISO 20022 field
Events/webhooks when new bank data has been processed
TypeScript integration surface

{
  "resource": "statement",
  "account": "FI21 1234 5600 0007 85",
  "currency": "EUR",
  "balances": [
    { "type": "closingBooked", "amount": "10450.00" }
  ],
  "entries": [
    {
      "id": "ntry_8f2a1c",
      "amount": "-1200.00",
      "bookingDate": "2026-07-12",
      "status": "booked",
      "reference": "RF9812345678",
      "evidence": {
        "sourceFile": "camt053_20260712.xml",
        "isoMessage": "camt.053.001.08",
        "path": "/Document/BkToCstmrStmt/Stmt/Ntry[3]"
      }
    }
  ]
}

Illustrative response (provisional). Fields and formats may change during early access.

Why ISECure

Built on existing production connectivity

Production connectivity

The same File Exchange API already carries bank traffic for hundreds of Finnish companies over SEPA Web Services.

Certificate lifecycle

PKI certificate enrollment, automatic renewal, and management are already handled — no separate certificate store.

Secure file handling

Files are processed on AWS PCI DSS level components, separate from your product team.

Evidence preservation

Normalization doesn't discard origin: every value is traceable to its source file and field for audit.

Workflow

Three steps

1

Receive files

Through the existing File Exchange API — connectivity, certificates, and transfer as before.
2

Validate and normalize

Supported ISO 20022 content is parsed and normalized into business resources.
3

Consume data and evidence

Consume the resources and their evidence through the new API in your application.

Early access

For design partners

Shape the resource model and priorities before general availability
Direct line to the team building the service
Early access to the TypeScript integration surface

A suitable design partner

An accounting, ERP, treasury, payment, or financial-integration product
Already integrates, or plans to integrate, with Finnish banks
Willing to give feedback on real use cases

FAQ

Frequently asked

Does this replace bank agreements?

No. You still need your own bank agreements and authorizations. Processing requires the customer's authorization and an appropriate contractual and GDPR basis.

Does it work with the existing File Exchange API?

Yes. The File Exchange API remains unchanged. The new API sits alongside it and processes files you've already received under authorization.

Which banks and messages are supported?

Support is limited during early access, and we don't claim universal bank or ISO 20022 coverage. Tell us the banks and messages you care about and we'll prioritize them.

Is this real-time?

No. The underlying services are file-driven, so data is available once a file has been received and processed — not as a continuous real-time stream.

Who owns the data?

The data is the customer's. We process it under the customer's authorization and a contractual/GDPR basis; we don't use it for anything else.

Does this do bookkeeping?

No. We don't do automatic bookkeeping, accounting entries, or transaction categorization. We provide normalized data and evidence — you make the bookings in your own application.

Join the waitlist

Request early access

Tell us your use case. We'll reach out as early access opens to partners matching the profile.

Your message