Denied Party Screening
Last updated
Last updated
Glopal automatically validates all provided buyer delivery addresses against international carrier rules, and checks if the buyer is listed on any relevant official sanction list. Glopal checks below official sources daily for updates: are:
EU (FSF)
UK issued by the Office of Financial Sanctions Implementation (OFSI)
US Trade (CSL) issued by the International Trade Administration (ITA), consolidating multiple export screening lists of the US Departments of Commerce, State, and Treasury
The screening is carried out during the order processing. Alternatively, Glopal provides a separate API service to allow the integration of denied party screening in a customised process:
Client username (set by Glopal)
username
Pattern: ^[a-z0-9\-]{3,255}$
Optional system username to enable separation of authentication credentials by integrated client system. (set by Glopal)
alias-username
Pattern: ^[a-z0-9\-]{3,50}$
The authentication signature is created by using the concatenation of the login, the ‘@’ sign and the timestamp, transformed into a HMAC_256 signature using your secret access key.
40b976b35a08bb951439ea7bbfa0a7bd73dab7c813399a31d9d1a157bc08929b
Pattern: ^[0-9a-f]{64}$
The authentication timestamp must be a decimal numeric representing the current POSIX time, extended to microsecond accuracy. If the requesting system does not provide high-resolution time, it is advised to use a 6-digit random number. It is important to have the requesting system synchronised with a reliable time source (f.i. a stratum 2 NTP server) to avoid request rejection.
1680010295.775523
Pattern: ^[12]\d{9}\.\d{6}$
0.68
Pattern: (^0\.\d{2}$|^[1-9]\d*\.\d{2}$)