This glossary provides definitions of key terms used in GBG GO to help you understand the platform and its features.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.
Account management
The section in GBG GO where users with the correct permissions can manage team members, assign roles, reset passwords, and configure API access.Adaptive journey
A customer journey that collects data incrementally based on the journey stage, allowing for a more tailored verification process.Admin users
Users with administrative access in the GBG GO platform. They can add other users, manage roles, departments, and more.Analytics
A feature in GBG GO that provides insights into customer journeys, verification results, and user behavior through reports and dashboards.API access
A feature that allows authorized users to generate API credentials for integrating GBG GO with external systems.Capability
A specific data point or verification check available within a module or variant that can be evaluated when configuring outcome rules. Each module or variant provides different capabilities based on its functionality, which can be used to create conditional logic for determining customer journey outcomes.Combinators
Combinators are a type of logical operator that determines how multiple rules within an outcome are evaluated together. In GBG GO, there are two types of combinators:- All Match: All conditions must be true for the outcome to be applied.
- Any Match: At least one condition must be true for the outcome to be applied.
Customer journey
A defined workflow in GBG GO that guides users through verification processes, including identity checks and fraud detection.Documents and biometrics
A combination of document verification and biometric checks such as liveness and facematch, used to confirm a userâs identity.Evaluation
A key decision-making step in a journey where a customer is accepted, rejected, or flagged for manual review based on verification results. These decisions can be configured to meet specific business rules and compliance requirements.Fields
Fields are predefined capabilities or verification checks that you can use to build conditional rules within your journey outcomes. In GBG GO, Fields are selectable criteria that represent different types of verification checks the system can perform and evaluate. Theyâre essentially the âbuilding blocksâ for creating business logic. For example, Name + Address Matches checks whether name and address data align with any trusted sources.GBG GO
A platform for designing and managing customer verification workflows.GBG trust score
A comprehensive risk assessment score that combines various data points to evaluate the trustworthiness of a customer. GBG trust scores range from 0 to 100, with 100 being the highest level of trust. The higher the score, the lower the risk associated with the customer.Investigation
A GBG GO feature for investigating submitted customer data.Journey builder
The interface in GBG GO where business users design and configure customer journeys by adding modules, setting routing conditions, and defining evaluation rules to create customized journeys.Journey templates
Pre-configured workflows designed for specific industries or use cases to help users quickly set up customer journeys.Module
A functional component within a customer journey that performs specific tasks, such as identity verification or fraud detection. Module results are known as outcomes. These outcomes can be configured to meet specific business needs and compliance requirements. Examples of a modules in GO include:- Age Verification
- Document Authentication
Modules and variants
- Modules perform specific tasks within a journey, for example, ID verification.
- Variants are different versions of a module configured for specific regions, compliance rules, or business needs, for example, âUK: Single match super bureauâ.
Match flags
Match flags are the values returned by module variants to indicate the result of comparing a submitted data point against a supplierâs records. Each data point in a verification response carries one of the following match flag values:| Value | Meaning |
|---|---|
match | The submitted data fully matched the supplierâs record. |
partial match | The submitted data partially matched (e.g. a shortened or abbreviated name matched a longer record). |
initial match | Only the initial letter of a name field matched. |
alias match | The submitted name matched a known alias on the supplierâs record. |
mismatch | The customer provided data, but it did not match the supplierâs record. |
no result | The customer did not provide data for this field, so no comparison was attempted. |
not available | The customer provided data, but the supplier indicated the data point is unavailable in their records. |
unrecognised value | The supplier returned a value that does not conform to their expected schema. This typically triggers an investigation with the supplier integration team. |
| Value | Meaning |
|---|---|
match | Full date of birth matched (day, month, and year). |
month level match | Only the month and year matched. |
year level match | Only the year matched. |
partial match | A partial match that does not fall into the month or year categories above. |
no result means the customer never submitted the data point â there was nothing to compare. not available means the customer did submit data, but the supplier does not hold that data point in their records, so a comparison could not be made.
not available is an optional return value for identity match flags, but is mandatory for fraud flags.