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

Matching with Inbound Payments

    • For gSRP requests, Field 121 UETR of Incoming message is matched with the UETR of the Inbound transaction
    • For non-gSRP MT n92 requests, Field 21 of the incoming message with the Inbound transaction source reference and sender of the MT n92 request with the Inbound transaction sender bank value
  • Once the Incoming MT n92/gSRP request message is successfully matched, then system does below things
    • 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 asl SYSTEM and maker/checker timestamps against the Cancellation Request message
    • A recall request record is logged to show under ‘Exception’ screen of Inbound Transaction view screen.
  • If the matched Inbound transaction status is in Progress (or) transaction status is Exception and in any external queue, the cancellation request is logged in a cross border inbound queue cancellation request table which is referred during inbound processing key steps. The list of external queues considered are:
    • Sanction Check
    • EAC
    • External Exchange Rate
    • External Pricing
  • Cancellation processing for an Inbound transaction is done based on the transaction status and queue code

Parent topic: Inbound Cancellation Request Processing