pain.001 API for sending SEPA payment files
pain.001 is the ISO 20022 Customer Credit Transfer Initiation message used by ERP, accounting, and payroll software to send SEPA payment instructions to a bank. ISECure's File Exchange API transports the file over each bank's Web Services channel through one integration.
What pain.001 contains
A pain.001 file groups credit transfers from the debtor account into payment batches. It carries the debtor, creditor, amount, currency, execution date, and reference or remittance information required by the bank and schema version.
Banks publish their own implementation guidelines and accepted versions. The software creating the payment file remains responsible for producing XML that follows the relevant bank agreement and guideline.
How pain.001 moves through ISECure
Your software creates the bank-approved pain.001 XML file and uploads it through the ISECure API. ISECure handles the bank-specific Web Services connection, message signing, certificates, and file transport. You can retrieve the bank's pain.002 response through the same integration.
- One REST API for every supported Finnish bank
- PKI certificate enrollment, storage, and automatic renewal
- Payment-file delivery using the file type accepted by the bank
- pain.002 response retrieval for processing in your software
What the service does not change
The production ISECure REST API — File Exchange does not create payments, rewrite XML content, or replace bank approval. The separate Processing API can generate exact pain.001.001.09 from a governed payment batch in the test environment, but it does not submit the file to a bank. Bank submission still requires the company's bank agreement and authorization.