Sanction screening deployment

The simulator reads requests from the FTM high value payments application output queue, REQUEST.TO.SANCTION1, and places responses on the FTM high value payments application input queue, RESPONSE.FROM.SANCTION1.

Sanction screening request

The sanction screening request uses the following information:
  • Transaction type (business concept) - FTM_OUTGOING_SANCTION_REQUEST, FTM_INCOMING_SANCTION_REQUEST.
  • Request ID.
  • ISF structure of the received request.

Sanction screening response

The sanction screening response is shown in the following table.
Table 1. Sanction screening response
Status code Transaction type (business concept)
ACTC FTM_SANCTION_RESPONSE
  • The simulator responds to a sanction screening request with a sanction screening response.
  • ISF transaction structure - isf:Acknowledgment.
  • The response request ID and TransactionIdentification are populated from the request ID of the sanction screening request.
  • The response contains an accept status code.

Status code quick reference example

The simulator behavior that can be expected when the defaults defined for the user-defined property (UDP) values are used is shown in the following table.

Table 2. Example sanction screening simulator responses for default property values
ISF type Condition Value Status
All ISF types   None Accept

1 By default, all IBM® MQ names are prefixed with the placeholder ++FXTQPFX++.