GBG Trust

Evaluate identity data against the GBG Trust Network in GBG GO to detect application fraud, identity takeover, and mule activity using consortium intelligence.

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.

The module has two documented variants. Both draw from the GBG Trust Network, but they differ in result type and how outcomes are configured.

Variant	Result type
GBG Trust EMEA	Numeric score (0–1000)
GBG Trust - Alerts	Binary outcome with rule names

GBG Trust EMEA

Returns a numeric trust score indicating the fraud risk level of the submitted identity data, where higher scores mean lower risk.

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

A higher score indicates lower fraud risk. A score of 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

Date of birth anomaly matches - own data

Count of Rules for Date of Birth Anomaly Matches - Own Data

Detail	Description
Type	Integer
Range	0–2
Default	0

Contact detail change matches - network

Count of Rules for Contact Detail Change Matches - Network

Detail	Description
Type	Integer
Range	0–5
Default	0

High volume velocity matches - own data

Count of Rules for High Volume Velocity Matches - Own Data

Detail	Description
Type	Integer
Range	0–10
Default	0

Email address validation matches

Count of Rules for Email Address Validation Matches

Detail	Description
Type	Integer
Range	0–5
Default	0

Telephone validation matches

Count of Rules for Telephone Validation Matches

Detail	Description
Type	Integer
Range	0–5
Default	0

Contact detail change matches - external

Count of Rules for Contact Detail Change Matches - External

Detail	Description
Type	Integer
Range	0–5
Default	0

Non-Residential address matches

Count of Rules for Non-Residential Address Matches

Detail	Description
Type	Integer
Range	0–10
Default	0

Telephone anomaly matches - own data

Count of Rules for Telephone Anomaly Matches - Own Data

Detail	Description
Type	Integer
Range	0–2
Default	0

Test data matches

Count of Rules for Test Data Matches

Detail	Description
Type	Integer
Range	0–1
Default	0

Date of birth anomaly matches - network

Count of Rules for Date of Birth Anomaly Matches - Network

Detail	Description
Type	Integer
Range	0–5
Default	0

Mobile validation matches

Count of Rules for Mobile Validation Matches

Detail	Description
Type	Integer
Range	0–3
Default	0

Mobile risk signals

Count of Rules for Mobile Risk Signals

Detail	Description
Type	Integer
Range	0–5
Default	0

Name validation matches

Count of Rules for Name Validation Matches

Detail	Description
Type	Integer
Range	0–10
Default	0

High volume velocity matches - network

Count of Rules for High Volume Velocity Matches - Network

Detail	Description
Type	Integer
Range	0–15
Default	0

Address risk signals

Count of Rules for Address Risk Signals

Detail	Description
Type	Integer
Range	0–10
Default	0

Telephone risk signals

Count of Rules for Telephone Risk Signals

Detail	Description
Type	Integer
Range	0–15
Default	0

Disqualified director matches

Count of Rules for Disqualified Director Matches

Detail	Description
Type	Integer
Range	0–10
Default	0

Contact detail change matches - own data

Count of Rules for Contact Detail Change Matches - Own Data

Detail	Description
Type	Integer
Range	0–3
Default	0

Extreme volume velocity matches - own data

Count of Rules for Extreme Volume Velocity Matches - Own Data

Detail	Description
Type	Integer
Range	0–3
Default	0

Telephone anomaly matches - network

Count of Rules for Telephone Anomaly Matches - Network

Detail	Description
Type	Integer
Range	0–4
Default	0

Debt management matches

Count of Rules for Debt Management Matches

Detail	Description
Type	Integer
Range	0–10
Default	0

Duplicate match - same day

Count of Rules for Duplicate Match - Same Day

Detail	Description
Type	Integer
Range	0–1
Default	0

Email address anomaly matches - own data

Count of Rules for Email Address Anomaly Matches - Own Data

Detail	Description
Type	Integer
Range	0–5
Default	0

Input address quality level

A broad indicator of the input address quality

Value	Description
1	Excellent Quality
2	Good Quality
3	Poor
4	not possible to validate

Bank details anomaly matches

Count of Rules for Bank Details Anomaly Matches

Detail	Description
Type	Integer
Range	0–4
Default	0

At least one high priority rule fired

Detail	Description
Type	Boolean
Default	false

Address/Contact detail change matches - network

Count of Rules for Address/Contact Detail Change Matches - Network

Detail	Description
Type	Integer
Range	0–10
Default	0

Mobile anomaly matches - network

Count of Rules for Mobile Anomaly Matches - Network

Detail	Description
Type	Integer
Range	0–3
Default	0

Email address anomaly matches - network

Count of Rules for Email Address Anomaly Matches - Network

Detail	Description
Type	Integer
Range	0–10
Default	0

Name manipulation matches - own data

Count of Rules for Name Manipulation Matches - Own Data

Detail	Description
Type	Integer
Range	0–5
Default	0

Address/Contact detail change matches - own data

Count of Rules for Address/Contact Detail Change Matches - Own Data

Detail	Description
Type	Integer
Range	0–5
Default	0

Mobile anomaly matches - own data

Count of Rules for Mobile Anomaly Matches - Own Data

Detail	Description
Type	Integer
Range	0–2
Default	0

Address anomaly matches - network

Count of Rules for Address Anomaly Matches - Network

Detail	Description
Type	Integer
Range	0–5
Default	0

IP address anomaly matches

Count of Rules for IP Address Anomaly Matches

Detail	Description
Type	Integer
Range	0–2
Default	0

Outcome matches

Count of Rules for Outcome Matches

Detail	Description
Type	Integer
Range	0–15
Default	0

Name manipulation matches - network

Count of Rules for Name Manipulation Matches - Network

Detail	Description
Type	Integer
Range	0–10
Default	0

Address validation matches

Count of Rules for Address Validation Matches

Detail	Description
Type	Integer
Range	0–4
Default	0

Duplicate match - different day

Count of Rules for Duplicate Match - Different Day

Detail	Description
Type	Integer
Range	0–1
Default	0

Email address risk signals

Count of Rules for Email Address Risk Signals

Detail	Description
Type	Integer
Range	0–15
Default	0

Document validation matches

Count of Rules for Document Validation Matches

Detail	Description
Type	Integer
Range	0–1
Default	0

Address anomaly matches - own data

Count of Rules for Address Anomaly Matches - Own Data

Detail	Description
Type	Integer
Range	0–1
Default	0

Date of birth validation matches

Count of Rules for Date of Birth Validation Matches

Detail	Description
Type	Integer
Range	0–3
Default	0

HMRC tax defaulter matches

Count of Rules for HMRC Tax Defaulter Matches

Detail	Description
Type	Integer
Range	0–5
Default	0

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 may 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.
Could Not Locate	default, when no conditions matched	—

Input payload

The following is a sample payload used to submit identity data to the GBG Trust EMEA variant for processing.

JSON

{
  "resourceId": "your-journey-resourceID@latest",
  "context": {
    "config": {
      "delivery": "api"
    },
    "subject": {
      "identity": {
        "firstName": "John",
        "lastNames": ["Doe"],
        "dateOfBirth": "1990-01-01",
        "currentAddress": {
          "building": "1",
          "thoroughfare": "Long Street",
          "locality": "Bristol",
          "postalCode": "PC5 1LT",
          "country": "GBR"
        },
        "phones": [
          {
            "type": "Landline",
            "number": "[phone]"
          },
          {
            "type": "Mobile",
            "number": "[phone]"
          }
        ],
        "emails": [
          {
            "type": "home",
            "email": "[e-mail]"
          }
        ]
      },
      "documents": [
        {
          "type": "Driving Licence",
          "number": "DOE99012345AB6CD",
          "country": "GBR"
        },
        {
          "type": "International Passport",
          "number": "123456789",
          "country": "GBR"
        }
      ]
    }
  }
}

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 (ISO 3166-1 alpha-3). Improves match accuracy when supplied.
identity.phones	No	Array of phone numbers. Each entry includes a type (for example, Landline, 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 returned by the module.

JSON

{
  "response": {
    "advice": {
      "gbgTrustNotAvailable": false
    },
    "outcome": "High Risk"
  }
}

Sample response

The following is a sample response for a medium-risk trust outcome.

JSON

{
  "response": {
    "advice": {
      "contains": {
        "gbgTrustNotAvailable": false
      }
    },
    "outcome": "Medium Risk"
  }
}

GBG Trust - Alerts

Evaluates configurable alert rules against the GBG Trust Network and returns a pass or alert outcome naming which rules fired.

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

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

{
  "resourceId": "your-journey-resourceID@latest",
  "context": {
    "config": {
      "delivery": "api"
    },
    "subject": {
      "identity": {
        "title": "Mr.",
        "firstName": "John",
        "middleNames": ["TWOFFFFFFFFFFFFFFFFFFFFFFFFFFF"],
        "lastNames": ["Doe"],
        "dateOfBirth": "1980-01-01",
        "gender": "Male",
        "currentAddress": {
          "country": "AU",
          "postalCode": "2617",
          "administrativeArea": "ACT",
          "dependentLocality": "Belconnen",
          "thoroughfareType": "Street",
          "thoroughfare": "Baloney",
          "building": "42"
        }
      },
      "previousAddress": [],
      "phones": [
        {
          "type": "mobile",
          "number": "0420000009"
        }
      ],
      "emails": [
        {
          "type": "personal",
          "email": "[e-mail]"
        }
      ],
      "socials": [
        {
          "type": "facebook",
          "identity": "john.doe"
        }
      ]
    }
  }
}

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, Female).
identity.currentAddress	No	Current address of the subject, broken down into building, thoroughfareType, thoroughfare, dependentLocality, administrativeArea, postalCode, and country (ISO 3166-1 alpha-2 or alpha-3).
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, landline) and a number.
emails	No	Array of email addresses. Each entry includes a type (for example, personal, 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 returned by the module.

JSON

{
  "response": {
    "advice": {
      "alertRaised": true
    },
    "export": {
      "sku": [
        "greenID_AU_trustalert"
      ]
    },
    "outcome": "ALERT"
  }
}

Sample response

The following is a sample response for an alert outcome.

JSON

{
  "response": {
    "advice": {
      "contains": {
        "alertRaised": true
      }
    },
    "export": {
      "sku": ["greenID_AU_trustalert"]
    },
    "outcome": "ALERT"
  }
}

GBG TRUST V2

Capabilities

Date of birth anomaly matches - own data

Count of Rules for Date of Birth Anomaly Matches - Own Data

Detail	Description
Type	Integer
Range	0–2
Default	0

Contact detail change matches - network

Count of Rules for Contact Detail Change Matches - Network

Detail	Description
Type	Integer
Range	0–5
Default	0

High volume velocity matches - own data

Count of Rules for High Volume Velocity Matches - Own Data

Detail	Description
Type	Integer
Range	0–10
Default	0

Email address validation matches

Count of Rules for Email Address Validation Matches

Detail	Description
Type	Integer
Range	0–5
Default	0

Telephone validation matches

Count of Rules for Telephone Validation Matches

Detail	Description
Type	Integer
Range	0–5
Default	0

Contact detail change matches - external

Count of Rules for Contact Detail Change Matches - External

Detail	Description
Type	Integer
Range	0–5
Default	0

Non-Residential address matches

Count of Rules for Non-Residential Address Matches

Detail	Description
Type	Integer
Range	0–10
Default	0

Telephone anomaly matches - own data

Count of Rules for Telephone Anomaly Matches - Own Data

Detail	Description
Type	Integer
Range	0–2
Default	0

Test data matches

Count of Rules for Test Data Matches

Detail	Description
Type	Integer
Range	0–1
Default	0

Date of birth anomaly matches - network

Count of Rules for Date of Birth Anomaly Matches - Network

Detail	Description
Type	Integer
Range	0–5
Default	0

Mobile validation matches

Count of Rules for Mobile Validation Matches

Detail	Description
Type	Integer
Range	0–3
Default	0

Mobile risk signals

Count of Rules for Mobile Risk Signals

Detail	Description
Type	Integer
Range	0–5
Default	0

Name validation matches

Count of Rules for Name Validation Matches

Detail	Description
Type	Integer
Range	0–10
Default	0

High volume velocity matches - network

Count of Rules for High Volume Velocity Matches - Network

Detail	Description
Type	Integer
Range	0–15
Default	0

Address risk signals

Count of Rules for Address Risk Signals

Detail	Description
Type	Integer
Range	0–10
Default	0

Telephone risk signals

Count of Rules for Telephone Risk Signals

Detail	Description
Type	Integer
Range	0–15
Default	0

Disqualified director matches

Count of Rules for Disqualified Director Matches

Detail	Description
Type	Integer
Range	0–10
Default	0

Contact detail change matches - own data

Count of Rules for Contact Detail Change Matches - Own Data

Detail	Description
Type	Integer
Range	0–3
Default	0

Extreme volume velocity matches - own data

Count of Rules for Extreme Volume Velocity Matches - Own Data

Detail	Description
Type	Integer
Range	0–3
Default	0

Telephone anomaly matches - network

Count of Rules for Telephone Anomaly Matches - Network

Detail	Description
Type	Integer
Range	0–4
Default	0

GBG TRUST score

The score returned by GBG’s TRUST processing

Detail	Description
Type	Integer
Range	0–1000
Default	0

Debt management matches

Count of Rules for Debt Management Matches

Detail	Description
Type	Integer
Range	0–10
Default	0

Duplicate match - same day

Count of Rules for Duplicate Match - Same Day

Detail	Description
Type	Integer
Range	0–1
Default	0

Email address anomaly matches - own data

Count of Rules for Email Address Anomaly Matches - Own Data

Detail	Description
Type	Integer
Range	0–5
Default	0

Input address quality level

A broad indicator of the input address quality

Value	Description
1	Excellent Quality
2	Good Quality
3	Poor
4	not possible to validate

Bank details anomaly matches

Count of Rules for Bank Details Anomaly Matches

Detail	Description
Type	Integer
Range	0–4
Default	0

At least one high priority rule fired

Detail	Description
Type	Boolean
Default	false

Address/Contact detail change matches - network

Count of Rules for Address/Contact Detail Change Matches - Network

Detail	Description
Type	Integer
Range	0–10
Default	0

Mobile anomaly matches - network

Count of Rules for Mobile Anomaly Matches - Network

Detail	Description
Type	Integer
Range	0–3
Default	0

Email address anomaly matches - network

Count of Rules for Email Address Anomaly Matches - Network

Detail	Description
Type	Integer
Range	0–10
Default	0

Name manipulation matches - own data

Count of Rules for Name Manipulation Matches - Own Data

Detail	Description
Type	Integer
Range	0–5
Default	0

Address/Contact detail change matches - own data

Count of Rules for Address/Contact Detail Change Matches - Own Data

Detail	Description
Type	Integer
Range	0–5
Default	0

Mobile anomaly matches - own data

Count of Rules for Mobile Anomaly Matches - Own Data

Detail	Description
Type	Integer
Range	0–2
Default	0

Address anomaly matches - network

Count of Rules for Address Anomaly Matches - Network

Detail	Description
Type	Integer
Range	0–5
Default	0

IP address anomaly matches

Count of Rules for IP Address Anomaly Matches

Detail	Description
Type	Integer
Range	0–2
Default	0

Outcome matches

Count of Rules for Outcome Matches

Detail	Description
Type	Integer
Range	0–15
Default	0

Name manipulation matches - network

Count of Rules for Name Manipulation Matches - Network

Detail	Description
Type	Integer
Range	0–10
Default	0

Address validation matches

Count of Rules for Address Validation Matches

Detail	Description
Type	Integer
Range	0–4
Default	0

Duplicate match - different day

Count of Rules for Duplicate Match - Different Day

Detail	Description
Type	Integer
Range	0–1
Default	0

Email address risk signals

Count of Rules for Email Address Risk Signals

Detail	Description
Type	Integer
Range	0–15
Default	0

Document validation matches

Count of Rules for Document Validation Matches

Detail	Description
Type	Integer
Range	0–1
Default	0

Address anomaly matches - own data

Count of Rules for Address Anomaly Matches - Own Data

Detail	Description
Type	Integer
Range	0–1
Default	0

Date of birth validation matches

Count of Rules for Date of Birth Validation Matches

Detail	Description
Type	Integer
Range	0–3
Default	0

HMRC tax defaulter matches

Count of Rules for HMRC Tax Defaulter Matches

Detail	Description
Type	Integer
Range	0–5
Default	0

Input payload

The following is a sample payload used to submit data to the GBG TRUST V2 module for processing.

JSON

{
  "context": {
    "subject": {
      "accounts": [
        {
          "accountNumber": "00000000",
          "sortCode": "00-00-00",
          "type": "Bank Account"
        }
      ],
      "documents": [
        {
          "cardNumber": "000",
          "number": "NZ000000",
          "type": "Driving License"
        }
      ],
      "identity": {
        "currentAddress": {
          "country": "GBR",
          "locality": "Anyton",
          "postalCode": "AA1 1AA",
          "premise": "0",
          "thoroughfare": "The Street"
        },
        "dateOfBirth": "2007-03-26",
        "firstName": "Missing",
        "lastNames": [
          "Person"
        ],
        "phones": [
          {
            "number": "[phone]",
            "type": "mobile"
          }
        ]
      },
      "uid": "variant-test-user"
    }
  }
}

Field	Required	Description
FullName	Yes	[Describe.]
CurrentAddress	No	[Describe.]
DateOfBirth	No	[Describe.]
MobilePhone	No	[Describe.]
LandlinePhone	No	[Describe.]

Sample response

The following is a sample response returned by the module.

JSON

{
  "response": {
    "advice": {},
    "outcome": "Could Not Locate"
  }
}