Sanction list screening uses data from our partner sanctions.io (API endpoint: https://api.sanctions.io).
Two steps are required to use the data for sanction list screening:
A – Get an API key from sanctions.io: register for a free trial account at api.sanctions.io, note down the API key provided after registering, and maintain the key in the parameters for this check. Notify the remQ or santions.io support team, we will activate the sanctions.io account and assign a plan with 50k sanction checks per year (free of cost).
B – Enable the SSL connection to sanctions.io: The SAP system has to connect as SSL client to api.sanctions.io and therefore requires an active SSL service and has to trust the SSL server.
To enable this:
1. Check the SSL server status of the SAP system in transaction SMICM -> Goto -> Services:
there must be an active HTTPS service.
2. In transaction SM59, create an HTTP Connection to External Server (type G):
Name of the connection=SANCTIONS.IO
Target Host:Port=api.sanctions.io:8443
Logon Procedure=No Logon (authentication uses the API key that is sent via HTTPS)
SSL Status: Active
SSL Client Certificate: SSL Client (Anonymous)
3. In transaction STRUST, establish a trust relationship to the SSL server at https://api.sanctions.io:8443
Download the self-signed X.509 certificate from https://api.sanctions.io:8443
Import this certificate to the certificate list of the SSL Client (Anonymous).
We use a self-signed certificate with extended lifetime so that maintenance of the trust relationship in STRUST becomes minimal and you do not have to renew the certificate every few months.
If you prefer a CA-issued SSL server certificate, you can use port 443.
Note: For testing, you can access our sandbox API: in this case, set up a HTTP destination for sandbox.sanctions.io, an API key for testing is provided on that website. Also adjust your SSL settings accordingly.
