30.1.1 Reject Payment Status Report (pain.002)

This topic describes about Reject Payment Status Report (pain.002).

A Reject Customer Payment Status Report (pain.002) is generated for inbound MT101 (pain.001) transactions in the following scenarios.

Table 30-1 Reject Payment Status Report (pain.002)

Scenarios	MT101 Transaction Statu	Out Transaction Status	Remarks
Manual Cancellation of MT101 from Business Override (BO) queue	Cancelled	NA	Reject Reason code captured during MT101 cancel user action is populated in pain.002 message
Manual Cancellation of MT101 from Sanctions Check (SC) queue	Cancelled	NA	Reject Reason code captured during MT101 cancel user action is populated in pain.002 message
Auto Cancellation of MT101 from Sanctions Check (SC) queue	Cancelled	NA	Reject Reason code will be derived using Generic Wires ISO Reason Code (PSDRJTRM) mapping
Manual Cancellation of MT101 from Network Resolution (NR) queue	Cancelled	NA	Reject Reason code captured during MT101 cancel user action is populated in pain.002 message
Manual Cancellation of Outbound transaction generated by pain.001	Processed	Cancelled	Reject Reason code will be derived using the existing Pain.002 Reason Code Mapping (PMDPNRJT) maintenance
Auto Cancellation of Outbound transaction generated by pain.001	Processed	Cancelled	Reject Reason code will be derived using Generic Wires ISO Reason Code (PSDRJTRM) mapping

Auto Cancellation from Exception Queue for MT101

The Generic Wires ISO Reason Code Mapping (PSDRJTRM) is used to populate the reject code in the Customer Payment Status Report (pain.002) message.

Note:

If no reject reason code mapping is found, the default reason code MS03 is used.