Processing API

Prepare and validate bank payment files

Processing API helps your software prepare bank payment files through a controlled workflow before the real bank agreement and production certificates are ready. It checks the payment details, finalizes a version, and lets your application download the exact same file for local signing.

Beta
  • ProductionRegistration required · Paid subscription required · Standard onboarding

Product stage and access

Processing API is in Beta. Nordea Corporate Access payment-file profiles are Nordea validated for Finland, Sweden, Norway and Denmark. OP and Danske Bank Finland SEPA payment-file profiles are available; their bank validation is in progress. Säästöpankki, Oma Säästöpankki and Ålandsbanken Finland SEPA payment-file profiles and the POP Pankki and Aktia pain.001.001.03 profiles are available; their bank validation has not started. Processing API is available only in production for separately onboarded subscribers. The test service has been retired. Verification of Payee (VoP) is not part of the current production release.

Pricing (Beta)

Priced like Bank Connectivity: 18 €/month base fee per integrator, 2 €/month per end customer (minimum 10 customer licenses), 200 € one-time production onboarding. Onboarding is waived for existing Bank Connectivity customers until 31 December 2026. Annual billing, VAT added on top.

How a payment file is prepared

  1. Choose the payment-file format for the bank and country within the user's access rights.

  2. Create a payment batch and add or correct its payments.

  3. Validate the payment details and finalize the version used to generate XML.

  4. Generate and download the file for that finalized version. The current technical output is ISO 20022 pain.001.001.09, and the TypeScript SDK verifies that the downloaded file has not changed.

Choose test or production after signing

  1. Processing API

    Prepares and generates the checked payment file.

  2. Customer application

    Verifies and signs the downloaded file under the customer's control.

  3. Choose destination

    Use the same File Exchange API with Bank Simulator now and a separately qualified real-bank destination later.

Test path · Bank Simulator

Upload the signed synthetic file to bank simulator through a separate File Exchange session, then retrieve pain.002, camt.054, and the updated camt.053.

The historical Processing-to-Simulator example requires the retired test service. The current generation example uploads nothing. The File Exchange simulator is a separate service.

Production path · Bank Connectivity

Upload the signed file to a supported bank only after the customer has separate Bank Connectivity access, a bank agreement, production credentials, and a qualified connection.

Where Processing API's responsibility ends

  • Processing API and Bank Connectivity use separate sign-in sessions.
  • Bank Connectivity separately handles bank certificates and bank-file listing, download, and upload.
  • The customer's private signing key stays in their own application. Processing API never receives the key and does not submit a payment to a bank.
  • Generating a file does not approve a payment. Upload requires the PGP signatures enforced by File Exchange.

API documentation

Read the operation reference, authentication guide and TypeScript examples. Both APIs use the existing ISECure registration and login, followed by a separate Processing session.

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