MT n92 / gSRP Request Message Generation

MT n92 message generation

If the outbound transaction is identified as ‘non-gpi’ message, then system automatically generates MT 192/MT 292 as per standard format.

If the outbound transaction is identified as ‘non-gpi’ message, then system automatically generates MT 192/MT 292 as per standard format.
Receiver of the message is populated same as the receiver of the original outbound transaction payment message
Field 20 sender reference number is populated with cancellation request reference
Field 21 related reference number is populated with outbound transaction reference
Field 11S with the outbound payment message type and message date
Field 79 with the ‘Narrative (79) Line 1’ field, Narrative lines 2 to 35 field values if given by user
Copy of the original payment message is populated if the flag ‘Copy of at least the Mandatory Fields of the Original Message is checked

Note:

As per the existing functionality, the optional fields also gets populated.

gSRP Request message generation

If the outbound transaction is identified as ‘gpi’ message, then system generates gSRP request as MT 192 message or MT 199 message based on the ‘gSRP Request Message Type’ gpi Host preference (PXDGPIPF).

Message type is MT 192 if the ‘gSRP Request Message Type’ selected is 192 It is MT 199 if the preference is selected as MT 199.
Receiver of the message is Tracker BIC (TRCKCHZZ) value populated in gpi Host preference (PXDGPIPF)
Field 111 is populated with the service type identifier (002) value maintained for gSRP in gpi Static Preference maintenance.
Field 121 is populated with the UETR of the outbound transaction
Field 20 sender reference number is populated with cancellation request reference
Field 21 related reference number is populated with outbound transaction reference
Field 11S with the outbound payment message type and message date if the ‘gSRP Request message type’ is MT 192.
Field 79 with the ‘Narrative (79) Line 1’ value given by user in the Transaction Cancellation request message.

RMA/RMA+ validation is done for gSRP request messages also. Validation is done based on the gSRP request message type, Branch default BIC, Tracker BIC and message generation date

Cancellation status is marked as ‘Exception’. Error code & error reason gets updated.
No gSRP request is generated

Sanction Check

gSRP request messages undergoes Sanctions Check processing. The processing is same as done for the normal MT n92/MT n99 messages.

Note:

For Customer transfer with cover transaction, the gSRP/MT n92 request message is generated only for the customer transfer
The successfully generated request messages can be viewed from the ‘Recall Messages’ screen of Outbound Cross Border Payments View (PXDOVIEW)

Recall Request Log

After successful generation of MT n92/gSRP Request message, the recall request is logged for the Outbound transaction.

Recall Reference – Field 20 of n92/gSRP request
Recall Date – Date on which n92/gSRP request sent out
Recall Reason Code – Reason Code selected for n92/gSRP request
Recall Reason – Value given in ‘Narrative (79) Line 1’ field after the Reason code by user.