An event, like the change of the “Manual Review Result” for a compliance check record, is not the result of a direct API request. Our Notification Service solves this problem by letting you register a URL that we will send a Compliance Check-callback anytime such an event happens.
Compliance Checks
Last changes: 02-29-2024
With our Compliance Services we are offering the functionalities required to comply with regulatory requirements in regards to online sales.
The Compliance check process includes following components:
- Check of Individual Blacklist of a given acceptance point / market place operator or by Brand
- Check of different sanction lists, can be selected individually
- Check of PEP lists (only if required by Acceptance point / Market place or otherwise PEP is excluded from checks)
- Check of different law enforcement lists, can be selected individually.
In case of exact match, the compliance check is interrupted, and the system delivers a RED traffic light back to the request issuing system.
The following section will describe the procedure and results of a person compliance check and can be analogously applied to a company compliance check (see API method 1.111 Perform Company Compliance Check).
Call the API method 1.101 Perform Person Compliance Check and specify as much individual-related information as possible, e.g. customer name, address, birthdate, etc.
Compliance Check Request
-
Path:
-
POST {baseURL}/compliance/personCheck
-
Header:
-
Content-Type: application/json
Accept-Language: en-US
X-Auth-Token: eyJhbGciOiJSUzI1NiI{abbreviated}RW5kVG9rZW4=
{
"partnerReference": "COMPLIANCE-CHECK-D4CE1ABB1676E3DF5BB44",
"merchantReference": "ecbbda329fb2154157fcc2e3982cdad9",
"programCode": "COMPANY123",
"customerId": "100001073541",
"firstName": "Jacob",
"lastName": "Smith",
"street": "Anystreet",
"house": "321",
"postalCode": "12345",
"city": "Anycity",
"countryCode": "DE",
"dateOfBirth": "1965-01-01",
"gender": "MALE",
"localDate": "2018-11-12",
"localTime": "163835"
}Compliance Check Response
-
Status Code:
-
200 (OK)
-
Header:
-
Content-Type: application/json
Accept-Language: en-US
{
"partnerReference": "COMPLIANCE-CHECK-D4CE1ABB1676E3DF5BB44",
"programCode": "COMPANY123",
"complianceData":
{
"archiveId": "4108000025015465",
"trafficLight": "YELLOW",
"hitType": "SL",
"manualReview": true,
"details":
[
{
"name": "Jacob Smith",
"birthdate": "19660201",
...
},
{
"name": "Jacob Smith",
"birthdate": "19660201",
...
},
...
] ,
"listHit": true
},
"localDate": "2018-11-12",
"localTime": "163835",
"sysDate": "2018-11-12",
"sysTime": "153837",
"responseCode": "0000",
"responseDescription": "Successful execution.",
"additionalInformation": {
"requestId": "aff2728481a181dc36daedc14055b516"
}
}The result of the compliance check is summarized in the parameter “trafficLight” and can take on the following values:
Value | Explanation |
“RED” | Hit. |
“YELLOW” | Unsure hit. |
“GREEN” | No hit. |
We receive an unsure hit in our example response, because no perfect match, but similar entries (differing birthdates) could be found for the provided personal data.
Each found entry is stored as an array item in the parameter “details” and consists of a list of “name” -> “value” pairs.
Due to regulatory requirements, a person or company must not be part of one of the following lists (see parameter “hitType”):
Value | Explanation |
“SL” | |
“BL” | |
“PEP” |
If the check result has been manually added to the compliance white/black list, the parameter “listHit” is set to “True.