1. Cross Border User Guide
  2. SWIFT gpi
  3. gpi Tracker Enquiry by UETR
  4. gpi Tracker Enquiry by UETR
  5. Transaction Type Processing

Transaction Type Processing

  • The system performs the below validation for the transaction type 'Outbound':
    • UETR value is present in one of the outbound transactions.
    • The source of the outbound transaction is the same as the source value given in the service request.
    • The debit account of the original transaction is the same as the account given in the service request.
    • In case any of the above-listed validations fail, then the Enquiry Service request gets rejected and an error code/description is sent in the response.
  • The system performs the below validation for the transaction type 'Inbound':
    • UETR length is 36 characters and as per for the UETR format ([a-f0-9]{8}-[a-f0- 9]{4}-4[a-f0-9]{3}-[89ab][a-f0-9]{3}-[a-f0-9]{12}).
    • UETR value is not present in one of the outbound transactions.
    • UETR value is not present in one of the Inbound transactions.
    • In case any of the validations fail, the Enquiry request gets rejected.
  • In the received response, the system looks for the below-listed data:
    • Any payment event record with Tracker Event Type as ‘CTPT’.
    • In the ‘CTPT’ event type record, the Creditor Account value is present.
  • If Creditor Account value is present, the system performs below listed validations:

    - Creditor Account IBAN value is not blank and the IBAN value is the same as IBAN of the Account Number given in the request (or) Creditor Account Identification value is not blank and the value is same as the Account Number given in the request.

  • If any of the above validations fail, then the response to the enquiry request from the channel shows an error code/error description.
  • After successful validations of the gpi Tracker API response, Oracle Banking Payments frame the response message to be sent to the channels.

Parent topic: gpi Tracker Enquiry by UETR