The GBG Trust module performs fraud checks by evaluating submitted identity data against the GBG Trust Network. It surfaces fraud signals such as application fraud, identity takeover, and mule activity during onboarding. This page contains documentation for the GBG Trust module, including its variants, capabilities, and the specific result values each variant returns. The module has two documented variants. Both draw from the GBG Trust Network, but they differ in result type and how outcomes are configured.Documentation Index
Fetch the complete documentation index at: https://docs.go.gbgplc.com/llms.txt
Use this file to discover all available pages before exploring further.
| Variant | Result type |
|---|---|
| GBG Trust EMEA | Numeric score (0–1000) |
| GBG Trust - Alerts | Binary outcome with rule names |
GBG Trust EMEA
The GBG Trust EMEA variant returns a numeric trust score that indicates the fraud risk level of the submitted identity data. Higher scores indicate lower risk. This variant requires the subject’s full name and date of birth. The current address is optional but improves match accuracy.Capabilities
The module returns three capabilities, a trust score and two service-status flags.GBG Trust score
This capability returns an integer trust score indicating the fraud risk level of the submitted identity data.| Detail | Description |
|---|---|
| Type | Integer |
| Range | 0–1000 |
| Default | 0 |
0 indicates that the comparison could not produce a result and should be treated as inconclusive rather than a confirmed high-risk outcome.
GBG Trust not available
This capability indicates whether the GBG Trust service was unavailable at the time of evaluation.| Detail | Description |
|---|---|
| Type | Boolean |
| Values | isTrue, isFalse |
| Default | isTrue |
GBG Trust time out
This capability indicates whether the GBG Trust service timed out during the evaluation.| Detail | Description |
|---|---|
| Type | Boolean |
| Values | isTrue, isFalse |
| Default | isFalse |
Default outcomes
The module uses score thresholds to classify the trust result into one of five outcomes.| Outcome | Condition | Description |
|---|---|---|
Low Risk | Score ≥ 600 | The identity data shows low fraud risk and can typically be accepted without further review. |
Medium Risk | Score ≥ 250 and ≤ 600 | The identity data shows moderate fraud risk. Depending on your risk tolerance, this might route to additional verification or manual review. |
High Risk | Score > 0 and < 250 | The identity data shows elevated fraud risk. This outcome typically routes to manual review or rejection. |
Unknown | Score is 0 or GBG Trust not available is isTrue | The service could not produce a result. Treat as inconclusive rather than as a confirmed high-risk outcome. |
ERROR | Default (no conditions matched) | The trust check could not be completed due to a system-level issue. |
Input payload
The following is a sample payload used to submit identity data to the GBG Trust EMEA variant for processing.JSON
Field descriptions
Field descriptions
The table below describes each field in the payload.
| Field | Required | Description |
|---|---|---|
identity.firstName | Yes | First name of the subject. |
identity.middleNames | No | Array containing middle name(s) of the subject. |
identity.lastNames | Yes | Array containing the last name(s) of the subject. |
identity.dateOfBirth | Yes | Date of birth in YYYY-MM-DD format. |
identity.currentAddress | No | Current address of the subject, broken down into building, thoroughfare, locality, postalCode, and country in ISO 3166-1 alpha-3 format. Improves match accuracy when supplied. |
identity.phones | No | Array of phone numbers. Each entry includes a type, for example, Landline or Mobile, and a number in international format. |
identity.emails | No | Array of email addresses. Each entry includes a type, for example, home, and an email value. |
documents[].type | No | Document type, for example, Driving Licence or International Passport. |
documents[].number | No | Document number as printed on the document. |
documents[].country | No | Country of issue in ISO 3166-1 alpha-3 format. |
Sample response
The following is a sample response for a medium-risk trust outcome.JSON
GBG Trust - Alerts
The Alerts variant evaluates a set of configurable alert rules against the GBG Trust Network and returns whether any rules triggered. Rather than a numeric score, it returns a pass or alert outcome with detail on which specific rules fired. You configure which alert rules are active, and you can use the names of triggered rules to drive journey routing decisions.Capabilities
The module returns two capabilities, an overall alert outcome and the list of rules that triggered.GBG Trust alert overall outcome
This capability indicates whether any configured alert rules triggered for the subject.| Detail | Description |
|---|---|
| Type | Boolean |
| Values | isTrue, isFalse |
| Default | isFalse |
GBG Trust alert rules triggered
This capability returns the names of the specific alert rules that triggered, if any.| Detail | Description |
|---|---|
| Type | Enumset |
| Values | GBG Alert Rule A1, GBG Alert Rule B1, GBG Alert Rule A6 |
| Default | None |
Default outcomes
The module classifies the alert evaluation into one of three outcomes based on whether any rules triggered.| Outcome | Condition | Description |
|---|---|---|
PASS | Alert overall outcome is isFalse | No alert rules triggered. The subject can typically proceed without further review. |
ALERT | Alert overall outcome is isTrue | One or more alert rules triggered. Check the triggered rules capability to determine the specific signals and route accordingly. |
ERROR | Default (no conditions matched) | The alert evaluation could not be completed due to a system-level issue. |
Input payload
The following is a sample payload used to submit identity data to the GBG Trust - Alerts variant for processing.JSON
Field descriptions
Field descriptions
The table below describes each field in the payload.
| Field | Required | Description |
|---|---|---|
identity.title | No | Subject’s title, for example, Mr., Ms., Dr.. |
identity.firstName | Yes | First name of the subject. |
identity.middleNames | No | Array containing middle name(s) of the subject. |
identity.lastNames | Yes | Array containing the last name(s) of the subject. |
identity.dateOfBirth | Yes | Date of birth in YYYY-MM-DD format. |
identity.gender | No | Subject’s gender, for example, Male or Female. |
identity.currentAddress | No | Current address of the subject, broken down into building, thoroughfareType, thoroughfare, dependentLocality, administrativeArea, postalCode, and country in ISO 3166-1 alpha-2 or alpha-3 format. |
previousAddress | No | Array of the subject’s previous addresses. Same structure as currentAddress. |
phones | No | Array of phone numbers. Each entry includes a type, for example, mobile or landline, and a number. |
emails | No | Array of email addresses. Each entry includes a type, for example, personal or home, and an email value. |
socials | No | Array of the subject’s social media identities. Each entry includes a type, for example, facebook, and an identity — the username or handle. |
Sample response
The following is a sample response for an alert outcome.JSON