What is pain.002? A payment status report

pain.002 is the ISO 20022 Customer Payment Status Report. A bank uses it to report whether a pain.001 payment file was received, accepted for processing, or rejected. ISECure's File Exchange API retrieves the response made available by the bank.

pain.002, pain002, or pain 002?

The spellings pain.002, pain002, and pain 002 refer to the same ISO 20022 Customer Payment Status Report message family. A complete identifier also names the schema version, such as pain.002.001.10. The bank guideline and agreement determine the version and exact status codes in use.

What pain.002 tells you

A report can apply to the complete file, a payment batch, or an individual transaction. It contains the status and, when supplied, a reason code. Common states describe reception, processing, acceptance, or rejection, but availability and detail vary by bank and file.

pain.002 is not a bank-account transaction or a universal final confirmation that the creditor account has been credited. Your application must interpret the status according to the bank guideline and your payment workflow.

Retrieval through one bank integration

ISECure handles the bank's Web Services connection, certificates, and file retrieval. Your software lists and downloads pain.002 files through the REST API, SDK, or file synchronization, then reconciles them with the original pain.001 file.

  • Management of bank-specific connections and certificates
  • Listing and downloading new response files
  • Raw ISO 20022 XML for your own status logic
  • The same integration pattern across Finnish banks

Status is not a real-time promise

A response is available when the bank creates and publishes the file. ISECure does not change the bank's status or promise continuous real-time tracking. The bank agreement defines file types and response schedules.

Frequently asked questions

What is a pain.002 message?

pain.002 is the ISO 20022 Customer Payment Status Report. A bank uses it to report whether a pain.001 payment file was received, accepted for processing, or rejected.

What is the difference between pain.001 and pain.002?

pain.001 is the payment initiation file your software sends to the bank. pain.002 is the bank's status response to that file, batch, or transaction.

Does pain.002 confirm that the payment was made?

No. It reports the processing status and, when supplied, a reason code. It is not a final confirmation that the creditor account has been credited; your application must interpret the status according to the bank guideline.

What does pain.002.001.10 mean?

pain.002 names the message family and 001.10 the schema version. The bank guideline and agreement determine the version and status codes in use.

Make payment tracking dependable

Tell us your pain.001 and pain.002 versions and banks. We will help bring response retrieval into the same integration.

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