pain.002 ISO 20022 message
Published on
12/09/2025
Updated on
12/09/2025
Reading time
3 min
pain.002 ISO 20022 message: Definition
The message pain.002 (Customer Payment Status Report) is an ISO 20022 standard format for status reports about payment orders. It informs the client if a transaction was accepted, rejected or partially processed. This message serves as central feedback in electronic payment transactions between the customer and the bank.
With the introduction of Verification of Payee (VOP), the pain.002 message gets another meaning.
pain.002 ISO 20022 message: Scope
The pain.001 ISO 20022 message in XML-format is used internationally as part of the ISO 20022 standard to return a status report about a payment order. It is divided into multiple parts. The first part is the “Group Header”, contains general information like the message id and the bank of the client.
After that, the section “Original Group Information and Status” contains information about the original message, like its format (e.g. pain.001 or pain.008) and for example the number of its transactions. It is followed by seperate sections for every debtor/initiator with the name “Original Payment Information and Status”, which lists the status and the number of transactions which the debtor originally initiated. These sections contain details about every transaction that was not successful.
pain.002 ISO 20022 message: Usage
SEPA Credit Transfer (SCT): After transactions in the SCT-format (pain.001) are submitted, the status report often follows as pain.002. If the transaction is rejected, the bank can translate the original clearing message (e. g. pacs.004) to pain.002.
SEPA Direct Debit (SDD): For direct debits in the pain.008 format, pain.002 is used to send status reports and rejections to the submitter. In this case, the rejection can take place on clearing level, e. g. as pacs.002 and be translated to pain.002 afterwards.
usage in SEPA SDD
SCT Instant: For real-time payments in the TIPS environment or in the RT1 environment, the immediate feedback usually has the format pacs.002. This format can be converted to pain.002 for the exchange between bank an customer to display the status in banking internal systems or online banking portals.
Verification of Payee (VOP):
From October 2025, another use for this message will be Verification Of Payee (VOP) (by standard and real time SEPA transactions). The results of the name-IBAN-check (VOP matching) will be transmitted in it.
The pain.002 message will be returned as a response to a pain.001 message to the bank of the debtor by a RVM (Routing and/or Verification Mechanism). Every transaction included in the message represents a VOP response and contains its status/matching result.
In a pain.002 message which contains VOP responses, the number of associated transactions for every response status is listed in the section “Original Group Information and Status”. In case of VOP, an unsuccessful transaction which is listed in the section “Original Payment Information and Status” means a machting result not equal to “Match”. If the result is a close match, the correct name of the requested account owner is added to the transaction details.
usage in VOP
R-Transactions: Returns, cancellations, recalls or rejections of payments (clearing messages like pacs.004 or pacs.007) can also be converted to pain.002 for the exchange between bank and customer.
Bulk payments: For bulk transactions or mass payments, the bank can provide the status of every single transaction with pain.002.
Usage in the SWIFT environment
Pain.002 is also used in global payment transactions, especially when companies send payments to their banks over SWIFT FileAct or SWIFTNet. Here, the message serves as a confirmation of the acceptance of the payment or as rejection by th ebank and complements messages for communication between banks like pacs.002.