• After parsing the incoming Customer Payment Status Report (pain.002) message is matched with the original pain.001 message using the following matching criteria:
  • Original Payment Information Identification received in the incoming message is matched with Payment Information Identification of pain.001 message.
  • Original UETR received in the incoming message is matched with UETR of outbound pain.001 message.

• If the pain.002 message matching fails, then:
  • The pain.002 record transaction status under Processing Details Tab of Inbound Customer Payment Status Report View Detailed (PSDCPSRV) screen is marked as 'Processed'.
  • The pain.002 record Matching status under Processing Details Tab of Inbound Customer Payment Status Report View Detailed (PSDCPSRV) screen is marked as 'Unmatched'.
  • Process status of the uploaded pain.002 is 'Processed' in incoming browser (PMSINBRW).
  • Message Status of the uploaded pain.002 is updated as 'Repair' in incoming browser (PMSINBRW).

• If the pain.002 message matches with original pain.001 message then:
  • The pain.002 record transaction status under Processing Details Tab of Inbound Customer Payment Status Report View Detailed (PSDCPSRV) screen is marked as 'Processed'.
  • The pain.002 record Matching status under Processing Details Tab of Inbound Customer Payment Status Report View Detailed (PSDCPSRV) screen is marked as 'Matched'.
  • The Process status of the uploaded pain.002 is 'Processed' in incoming browser (PMSINBRW).
  • The incoming pain.002 message get linked with outgoing pain.001 (i.e., Generated Reference field is updated with Reference number of outgoing pain.001 message).