1. Cross Border User Guide
  2. SWIFT gpi
  3. gSRP Cancellation Processing
  4. Inbound Pass-through Cancellation Request Processing
  5. Matching with Outbound Pass-through Payments

Matching with Outbound Pass-through Payments

  • The classification of gSRP request and Non-gSRP request are done based on the message type and Block 3 fields 111 & 121.
  • When the incoming MT n92/gSRP message is not matched with any Inbound Cross Border/RTGS transaction, then the matching is done against Outbound Cross Border/ RTGS pass-through payments based on the Inbound SWIFT Payments view tables. Matching criteria used for gSRP request and non-gSRP messages are different.
    • For gSRP requests, Field 121 UETR of incoming message is matched with the UETR of the Outbound pass-through transaction.
    • For non-gSRP MT n92 requests, Field 21 of the incoming message with the Outbound pass-through transaction source reference and sender of the MT n92 request with the Outbound pass-through transaction sender bank field value.
  • Once the Incoming MT n92/gSRP request message is successfully matched, then system performs the following:
    • Process Status value is updated as ‘Matched’ in the Inbound Cancellation Browser.
    • Queue action log is populated with action as ‘MATCH’ along with maker/checker ids as SYSTEM and maker/checker timestamps against the Cancellation Request message.
    • A recall request record is logged to show under ‘Exception’ screen of outbound Transaction view screen.
  • Cancellation processing of an Outbound pass-through transaction is done based on its transaction status and current queue.

Parent topic: Inbound Pass-through Cancellation Request Processing