You can view PEP and Sanctions screening results in the Investigation Portal. For more information, refer to the View details of a customer session documentation.
Module variants
The PEPs and Sanctions module has three core variants that determine the scope of compliance checks performed on your customers.- UK Instance: Carries out two checks in the system:
- Checks if an end-user is a PEP.
- Checks if an end-user has sanctions against them.
- UK Instance (with OGM): This variant includes Ongoing Monitoring (OGM), allowing you to track verified customers on an ongoing basis. The system automatically alerts you if an end-user compliance status changes, such as being added to a sanctions list or identified as a PEP after their initial verification.
Ongoing Monitoring requires direct configuration with a PEP and sanctions data supplier. If you have not configured this integration, contact your GBG account manager for assistance.
- UK Instance (with Adverse Media and OGM): This variant screens end-users against negative news coverage, such as reports of fraud, financial crimes, or other risk-related activities. It returns details of any adverse media findings, including article titles, sources, and links. This variant also includes Ongoing Monitoring (OGM) to track end-users for new adverse media after their initial verification.
Capabilities and allowed values
Each PEPs and Sanctions variant supports different capabilities that determine what screening checks are performed. The table below defines the available capabilities and their allowed values.| Capabilities | Allowed values, labels, and descriptions |
|---|---|
PEPs and Sanctions Results: Results from PEPs and Sanctions check.
| View allowed values
|
| Sanctions Hit Type: Shows which customer data fields matched against a sanctions list entry. Values in this capability could indicate whether the match occurred through the customer’s full legal name, a known alias, or other matching criteria. This information helps you assess the accuracy and relevance of the match. | View allowed values (long list)
|
| Peps Hit Type: Shows which customer data fields matched against a PEPs database entry. This includes whether the customer is directly identified as a Politically Exposed Person or flagged as a family member or close associate of a PEP. It may also show if the match occurred through an alias or other matching criteria. | View allowed valuesSame values as Sanctions Hit Type. |
| Sent to OGM: Shows whether the customer has been added to Ongoing Monitoring for continuous tracking. When set to is true, this rule triggers a match if the customer has been enrolled in Ongoing Monitoring. | View allowed values
|
| Adverse Media Hit Type: Shows the nature and type of news coverage found for a customer during screening. This capability shows whether the customer has been linked to fraud, financial crimes, corruption, sanctions violations, or other compliance risks in news articles and media sources. | View allowed values
|
Variants and capabilities
This table shows the different variants and their capabilities of the module variants.| Variant | Capabilities |
|---|---|
| UK Instance | - PEPs and Sanctions Results - Sanctions Hit Type - Peps Hit Type |
| UK Instance (with OGM) | - PEPs and Sanctions Results - Sanctions Hit Type - Peps Hit Type - Sent to OGM |
| UK Instance (with Adverse Media and OGM) | - PEPs and Sanctions Results - Sanctions Hit Type - Peps Hit Type - Adverse Media Hit Type - Sent to OGM |
Example: Testing the PEPs and Sanctions module using GO API
This section walks you through testing the PEPs and Sanctions module.Step 1: Add the module to your journey
To test the PEPs and Sanctions module, you first need to add it to a customer journey.- Create a new journey or open an existing one in the journey builder.
- Click Browse and add modules.
- Search for PEPs and Sanctions or navigate to the Compliance Screening category.
- Select the PEPs and Sanctions module.
- Choose a variant.
The UK Instance (with Adverse Media and OGM) variant is used for testing during these steps.
- Click Add to journey.
- Click Configure outcomes.
- Rules:
- Match: PEPs and Sanctions Results + is any of + PEPs and Sanctions Hit. This rule means that if the PEPs and Sanctions check results in a hit, then there is a match.
- No Match: PEPs and Sanctions Results + is any of + PEPs and Sanctions No Hit. This rule means that if the PEPs and Sanctions check results in a no hit, then there is no match.
- Click Close.
Step 2: Publish the journey
After adding and configuring the module:- Click Publish to Preview.
- Go to the GBG GO Dashboard and copy your Resource ID and Version for testing.
Step 3: Start journey with test data
Use the Start journey endpoint to trigger the PEPs and Sanctions screening with test customer data. Send a POST request to/journey/start:
Request body:
cURL
your_access_token with a valid access token. Replace the resourceId value with your journey’s Resource ID and Version.
In the request, firstName and lastNames values are required. It’s recommended to use additional data, for example, the dateOfBirth value. This returns more accurate screening results.
What happens:
- The API creates a journey instance ID and processes the customer data through the PEPs and Sanctions module.
- You receive an
instanceIdin the response, which you will use to retrieve the results.
JSON
Step 4: Retrieve the screening results
Use the Fetch journey state endpoint to check if the PEPs and Sanctions screening has been completed. Send a POST request to/journey/state/fetch:
Request body:
cURL
- A list of tasks that were executed in the journey, including the PEPs and Sanctions screening task.
- Each task includes details about the screening outcome.
JSON
If the status is Completed, the PEPs and Sanctions screening has finished processing.