Skip to main content

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.

Customer journeys are structured processes that guide users through verification workflows such as identity verification, document processing, and approvals. The GBG GO platform allows you to create, manage, and deploy these journeys to securely onboard customers while preventing fraud. Each journey consists of modules that handle specific tasks, including identity verification and fraud detection.

​
Key components

  • Modules: Functional components that perform specific verification tasks
  • Evaluation: Decision points that determine whether to accept, reject, or flag users for review
  • Publishing: Deploying journeys to Preview (for testing) or Production (for live use)

​
User roles in journeys

  • Business users: Design and configure customer journeys in the GBG GO platform journey builder, defining workflows, adding verification modules, and publishing journeys
  • Developers integrate with the API to start journeys, fetch interactions, and submit verification data

​
Journey workflow

1

Step 1

Create a journey using templates or from scratch
2

Step 2

Configure modules and decision logic
3

Step 3

Add evaluation steps to determine outcomes
4

Step 4

Publish the journey for testing or production use
5

Step 6

Integrate with your system using API-first or Hosted journeys delivery methods

​
FAQ

These are the core building blocks of the GBG GO platform:
  • Journey: A journey is a structured workflow that guides an end user through verification steps such as identity checks, document processing, and fraud screening.
  • Module: A module is a functional component within a journey that performs a specific verification task. Examples include Document Classification, Document Authentication, Data Verification, Age Verification, and Facematch. Each module can have one or more variants, which are different configurations tailored to specific regions, compliance rules, or business requirements, for example, “US Data Verification.”
  • Capability: Capabilities are the underlying services that modules use to perform their tasks. For example, the Document Authentication module relies on the Document Authentication capability, which provides the core logic for verifying document authenticity.
  • Interaction: An interaction is a step in the journey where the platform collects information from the end user. When you fetch an interaction, the response describes which data elements are needed (the collects array), which are required or optional (the spec field), and which have already been provided (the outstanding array). In the v2 API, interactions replace the v1 task-based model.
  • Evaluation: An evaluation is a decision-making step in the journey where the platform determines an outcome, such as accept, reject, or refer for manual review, based on the results of the preceding verification modules.
A resource ID identifies a specific published version of a journey. When you publish a journey in GBG GO, the system assigns it a resource ID. You include this ID in the journey start request to tell the API which journey to run. To always use the most recently published version, append @latest to the resource ID (for example, your-resource-id@latest). To pin your integration to a specific version, use the fixed resource ID without @latest.An instance ID identifies a single execution of that journey. When you start a journey, the API creates a journey instance and returns a unique instanceId in the response. You use this instance ID in subsequent API calls.