Glossary of terms

Find definitions of key terms used across the GBG GO platform, including journeys, modules, outcomes, decisions, and API concepts.

This glossary provides definitions of key terms used in GBG GO to help you understand the platform and its features.

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.

Card

A UI unit inside an interaction page that collects domain elements from the user. Card plugins are generated dynamically per domain element listed in a card’s collects definition. The domain element id is appended only when a card collects more than one element, such as IdentifierCardSSN. Otherwise, the card keeps the base id, such as NameCard.

Collects and consumes

Interaction fields that specify which domain elements are gathered for collection (collects) or needed for display (consumes).

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.

DomainElementSpec

The schema describing a domain element requirement, including its ref and spec. A spec can be required, optional, or conditional. Also known as the input or output spec.

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.

Export to PDF

A user action that triggers generation of the journey session PDF report.

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.

Granular domain elements

A way to request just part of a piece of customer information instead of the whole thing. For example, instead of asking for a customer’s full name (first name, middle names, last name, and title), a module can ask for only the first name. This keeps customer journeys shorter by only collecting the data that’s actually needed.

Granular elements are written using a slash, such as FullName/firstName or MobilePhone/number. The customer still sees the same form, but only the requested fields are required to continue.

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.

Journey session PDF report

A PDF report generated for a journey session and streamed to clients through the files service.

Journey session status

The status values used for a session in Investigation. A session can be In Progress, Completed, Pending Input, Expired, or Cancelled.

Journey status

The execution status values returned by Captain APIs. A journey can be InProgress, Completed, Failed, or Paused.

Locale awareness

The ability of cards to adapt their labels and format based on country or language.

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.

Date of birth matching has additional granularity:

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” vs. “not available”: 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.

Operators

Operators are comparison points that define the relationship between a field and its target value when creating conditional rules. Operators establish the logical comparison that determines whether a rule passes or fails.

PII

Personally identifiable information. Data that identifies a subject and must be stored and handled with retention and access controls.

Preview environment

A test environment where journeys can be validated before being published to production.

Production environment

The live environment where published customer journeys are actively used by real customers.

Routing

A mechanism that determines how users move through a journey based on predefined conditions, for example, verification results or fraud risk scores.

Schema

A structured format that defines the required data fields for a journey’s API integration. The schema updates dynamically based on the modules included in a journey.

Webhook

A GBG GO feature that allows you to send real-time notifications through a POST request to external systems when specific events occur in a customer journey.