Sanction screening interface
The sanction screening interface implements the integration points for the system that hosts the sanction screening services of the bank.
FTM for High Value Payments defines an ISF format for the Sanction Screening Request and Sanction Screening Response messages that are used to interface with the sanction screening service. The default mapper implementation passes these ISF messages as-is. The supplied simulator is compatible with the ISF messages only. It is expected that customer-specific mappers are most likely needed to integrate with the real sanction screening service of the bank.
The sanction screening interface supports the following operations:
| Operation | Direction | Description | Format |
|---|---|---|---|
| Sanction Screening Request | Out | Request for a sanction screening check. | ISF CreditTransfer |
| Sanction Screening Response | In | Response indicating no sanction applies. | ISF Acknowledgment |
| Sanction Screening Reject Response | In | Response indicating a sanction was found and the payment should not proceed. | ISF Acknowledgment |
| Sanction Screening Pending Response | In | Response indicating the sanction screening is delayed and a final result is expected later. | ISF Acknowledgment |
By default, the sanction screening interface is implemented using two logical FTM channels, each using an IBM® MQ transport.
Correlation is configured on the FTM
Sanction Screening Provider service participant as Correlate with UID of request
transmission (IN_TXN_ACK_MQ2) At the IBM MQ level, FTM for High Value Payments sends a common ID on MsgId and CorrelId and the service must reply with either value on the CorrelId in the
response.
FTM channel: Sanction screening request
| Queue name | Operations |
|---|---|
| REQUEST.TO.SANCTION1 |
|
FTM channel: Sanction screening response
| Queue name | Operations |
|---|---|
| RESPONSE.FROM.SANCTION1 |
|
1 By default, all IBM MQ names are prefixed with the placeholder ++FXTQPFX++.