Bank Connectivity

Finnish bank Web Services through one API

The Web Services channel is the Finnish banks' standard for corporate file traffic: retrieving statements and sending payment files. This guide covers how it works and what integrating it requires.

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

Exact stage and access

Use requires the customer's bank agreements. Exact bank and file support depends on the agreement and qualified profile.

Contact us

What the Web Services channel is

The WS channel is a SOAP-based interface offered by banks, through which a company's software retrieves machine-readable statements and sends payment files. It replaces older batch-transfer methods and is used by all major Finnish banks.

The messaging is signed and encrypted, based on PKI certificates issued by the bank. The files are mostly in ISO 20022 format: statements as camt.053, payments as pain.001, and payment feedback as pain.002.

What integration requires

Adopting a WS connection requires a Web Services agreement with the bank and a certificate application. The software must build and sign WS messages, manage keys and certificate renewal, and process ISO 20022 files.

This is a significant implementation effort per bank — and it must be repeated for each bank, because there are bank-specific differences in the connections.

  • Web Services agreement and certificates with the bank
  • Building, signing, and encrypting WS messages
  • Managing the lifecycle of keys and certificates
  • Processing ISO 20022 files (camt.053, pain.001/002)

How ISECure simplifies this

ISECure offers the WS channel as a single REST API. We handle message signing, certificates, key management, and bank-specific differences, so your software only makes simple REST calls. One integration covers the Finnish banks we support.

Service boundaries

  • The service does not replace the customer's bank agreement or bank-granted authority.
  • The File Exchange API transports files; it does not change their financial content.

Capabilities and direction

DirectionCapability
Both directionsBank filesList and download bank-provided files and upload authorized files within the customer's bank agreement.
InputCertificatesEnroll and renew bank-connection certificates through the existing API.

Frequently asked questions

Is the REST API a separate banking product?

No. The REST API is how the Bank Connectivity product is used for bank-file exchange.

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