1. Cross Border User Guide
  2. Straight-Through Processing
  3. STP of Inbound Messages
  4. External Validations for Advisory Messages

External Validations for Advisory Messages

Incoming SWIFT message Upload changes

For Advisory messages, an external validation is done in the STP layer of incoming SWIFT upload processing. This external validation is done just before deriving payment transaction type [After STP rule validations/Cover match processing]. A hook is given in this place of incoming SWIFT upload processing.

Below are the expected things from the external validation hook result.

External validation should return both Execution Result and Validation Result.

Execution result can be 'S-Success' or 'F-Failed'.

If the Hook processing failed and the Execution Result is received as 'Failed', the Return transaction will be logged into Business Override Queue with the below Error Code ‘PXADVM-01’.

If the advisory message validation is executed successfully, the Validation Result can be one of the following:
  • A-Approved: The Incoming message upload processing will proceed further - Payment transaction type will get resolved, Network Resolution if required…etc.
  • R-Rejected: Auto cancellation of the incoming SWIFT message will get triggered [Cancellation processing detailed in subsequent section].
  • O-Override Queue: The Incoming SWIFT message will be moved to Business Override Queue with a pre-defined Error code and the Error description. Error Description will be appended with the external validation Error Code ‘PX-ADVM-02’
The following field values are provided in the hook request for Advisory messages external validations:
  • DCN
  • Message Reference Number (Field 20)
  • Host Code
  • Branch Code
  • SWIFT Message Type [MT 103/202/205]
  • Account with institution details [Field 57 all lines]
  • Beneficiary Institution details [Field 58 all lines]
  • Beneficiary Customer [Field 59 all lines]
  • Sender Bank
The following fields are expected as response:
  • Execution Result
  • Validation Result
  • Error Code
  • Error Description

Note:

All the parameters sent in the Request will be part of the Response too.

Advisory Messages for Business Override Queue Changes (PQSOVRQU)

When the Incoming SWIFT message is moved to BO queue, below changes are done.
  • Payment Type is set as 'Cross Border'.
  • Transaction Type is set as 'Incoming'.
  • Source Code is set for Incoming SWIFT by referring the source maintenance (PMDSORCE).
  • Network code is set as Cross Border payment type network code.
  • Source Reference Number is populated with Message reference Number (Field 20).
  • Queue Action is INIT

Cancellation Processing for Advisory Messages

Below are the key processing steps for the auto cancellation of Advisory messages external validation.

Incoming message is sent for Sanctions Screening.

  • Source code is picked up - Incoming SWIFT flag is checked - from source code maintenance (PMDSORCE).
  • Sanction check system is picked against SWIFT network code from Sanction check mapping (PMDNWMNT & PMDSCMAP).

If the Sanction screening result is not Seized, then

- Transaction status in Incoming SWIFT payment view is updated as 'Cancelled'

If the Sanction screening result is Seized, then

- Transaction status in Incoming SWIFT payment view is updated as 'Seizure'

Note:

  • No Sanction seizure entry will get posted.
  • No gpi/Universal confirmation message will get generated and sent out.

Queue action is logged against queue action BO_AUTO_CANCEL if the cancellation is triggered due to reject response (Verification Result field value is 'R') from extension layer.

The factory-shipped Error code and description is updated in Incoming SWIFT payment view (PSDIVIEW).

Parent topic: STP of Inbound Messages