# ISECure Banking API

> ISECure provides a hosted banking-integration API for Finnish corporate bank connections. It connects software products to banks through the corporate Web Services channel and removes bank-by-bank integration, certificate, and key-management work from product teams.

ISECure Oy (Helsinki, Finland) is used by Finnish accounting and ERP software products; bank traffic for thousands of Finnish companies runs through the service. The product offers a REST API for bank file upload, listing, and download, with OpenAPI documentation and test API access for developer evaluation, plus reliable SFTP/S3 synchronization for file-based workflows that do not use direct REST integration.

Security and operations: private key storage uses AWS KMS encryption in a PCI DSS level system, and the service is hosted separately from the customer software team to reduce exposure and compliance scope. PKI certificate enrollment, renewals, and import/export/storage are handled by ISECure, file materials can require PGP signatures, and bank traffic goes through a hardened interface for sensitive financial operations.

Supported bank connectivity: Nordea, OP, Danske Bank, S-Pankki/LähiTapiola, and Ålandsbanken directly; Handelsbanken, Aktia, POP Bank, Savings Bank, and OmaSP through Samlink and Crosskey connections.

Implementation note: ISECure does not filter or process bank file types as product-specific materials. Bank files pass through the service; bank agreements, credentials, and certificates are still required.

Pricing: the base fee is 18 €/month plus bank-account licenses at 2 €/account/month, sold in packages of 10 accounts. Production onboarding for a new customer is a one-time 200 €. Billing is annual and VAT is added to prices.

## Pages

- [Home (English)](https://www.isecure.fi/en/): product overview, supported banks, pricing, and FAQ
- [Home (Finnish)](https://www.isecure.fi/): Finnish-language product overview
- [Home (Swedish)](https://www.isecure.fi/se/): Swedish-language product overview
- [Products](https://www.isecure.fi/en/products/): current products with exact stage and customer access
- [Bank Simulator](https://www.isecure.fi/en/bank-simulator/): Beta test-environment enrollment, initial camt.053 download, signed pain.001 upload, and synthetic pain.002/camt.054/updated-camt.053 feedback; registration, a paid subscription, and an access request are required
- [Processing API](https://www.isecure.fi/en/processing-api/): separate Experimental payment workflow in the ISECure test environment for creating, approving, generating, and downloading exact pain.001; registration, a paid subscription, and an access request are required
- [ISO 20022 message guide](https://www.isecure.fi/en/iso-20022/): comparison of pain.001, pain.002, camt.053, and camt.054 in bank integrations
- [Bank integration for software products](https://www.isecure.fi/en/pankkiyhteys/): adding Finnish bank connectivity to a software product, build vs. buy
- [Finnish bank Web Services channel](https://www.isecure.fi/en/web-services/): how the corporate Web Services (WS) channel works
- [Nordea bank connectivity](https://www.isecure.fi/en/nordea/): connecting software to Nordea's corporate Web Services channel
- [OP bank connectivity](https://www.isecure.fi/en/op/): connecting software to OP's corporate Web Services channel
- [camt.053 bank statements](https://www.isecure.fi/en/camt-053/): machine-readable ISO 20022 statements
- [pain.001 payment files](https://www.isecure.fi/en/pain-001/): SEPA payment initiation file delivery
- [pain.002 payment status](https://www.isecure.fi/en/pain-002/): bank payment-status response retrieval
- [camt.054 notifications](https://www.isecure.fi/en/camt-054/): debit and credit notification retrieval
- [About](https://www.isecure.fi/en/about/): company information

## API documentation

- [ISECure REST API — File Exchange documentation](https://www.isecure.fi/wsapi_v2/): production API reference for authentication, certificates, bank file upload, listing, and download
- [OpenAPI specification](https://www.isecure.fi/wsapi_v2.json): machine-readable OpenAPI 2.0 description of the REST API

## Test before bank onboarding

An integrator can start while the real bank agreement and production certificates are still in progress. Processing API prepares and releases exact pain.001.001.09 bytes through a separate session; the customer's application verifies and signs those bytes locally; Bank Simulator accepts the signed synthetic file through the existing File Exchange API and returns synthetic feedback. Bank Simulator runs through the exact real-bank connection API: when onboarding is ready, that same File Exchange API contract targets a separately configured and qualified real-bank connection, while the simulator remains available for testing.

The current Processing and Bank Simulator examples run separately and do not correlate feedback automatically or retry an uncertain upload. The current simulator account, opening balance, and deterministic default scenario are fixed; customers cannot yet configure simulated banks, accounts, WebServices authorizations, scenarios, faults, or virtual time. Simulator evidence is not real-bank acceptance, settlement, channel qualification, or production support.

## SDKs and tooling

- [TypeScript SDK](https://github.com/isecurefi/isecure-ts-client): official TypeScript client library

- [Python SDK (Beta)](https://github.com/isecurefi/isecure-py-client): Python client library; see its README for current API coverage.

The PHP SDK and the `wscli` command-line tool are also available.

## Contact

- [Sales](mailto:sales@isecure.fi): sales enquiries
- [Technical support](mailto:support@isecure.fi): implementation and support
- [Phone](tel:+358404835507): +358 40 483 5507

## Optional

- [Privacy policy (Finnish)](https://www.isecure.fi/privacy/)
- [Privacy policy (English)](https://www.isecure.fi/en/privacy/)
- [Privacy policy (Swedish)](https://www.isecure.fi/se/privacy/)

- [Processing API reference](https://www.isecure.fi/apis/processing/): Experimental payment-file workflow in the test environment; shared ISECure identity, separate Processing session, OpenAPI 3.1 and TypeScript examples
- [Bank Simulator API reference](https://www.isecure.fi/apis/bank-simulator/): Experimental synthetic workspace, account, scenario and run control; separate from File Exchange file transfers