FAQ

1. Go to the GBG GO sign-in page.
2. Click Forgot your password? on the login screen.
3. Check your email for a recovery code and enter it in the recovery code field.
4. Enter a new password and confirm it.
5. Click Change Password to save your new password.

• Preview environment: A test environment where you can validate journeys before deploying them to production. Use this to test API calls, verify journey behaviour, and confirm that modules are configured correctly.
• Production environment: The live environment where published journeys are used by real customers.

1. Open your journey in the Journey builder.
2. Click Publish to Preview.
3. A confirmation message appears: “Delivery deployed successfully”.
4. Click Dashboard, where you can see the environment label (Preview), version number, resource ID, last published date, and the auto-generated schema.

1. Navigate to Investigation.
2. Click the Preview Environment tab.

• 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.

• page: Use this for GBG hosted journeys (low-code). When delivery is set to "page", the start response includes an instanceUrl, which is a GBG-hosted page URL that you redirect the end user to. The platform handles the entire user interface.
• api: Use this for API-first integration. When delivery is set to "api", the start response does not include an instanceUrl. You are responsible for building the user interface and collecting data from the end user.

{
  "resourceId": "your-resource-id@latest",
  "context": {
    "config": {
      "delivery": "page"
    },
    "subject": {}
  }
}

{
  "resourceId": "your-resource-id@latest",
  "context": {
    "config": {
      "delivery": "api"
    },
    "subject": {}
  }
}

{
  "resourceId": "your-resource-id@latest",
  "context": {
    "config": {
      "delivery": "api"
    },
    "subject": {
      "uid": "user-12345"
    }
  }
}

• Traceability: Matching journey results back to the correct customer record in your system.
• Debugging: Identifying which user a journey instance belongs to when investigating issues.
• Reporting: Correlating GBG GO verification outcomes with your internal user data.

{
  "instanceId": "your-instance-id",
  "interactionId": "your-interaction-id",
  "participants": [
    { "domainElementId": "PrimaryDocument" }
  ],
  "context": {
    "subject": {
      "documents": [
        {
          "side1Image": "<base64-encoded-image>",
          "side2Image": "",
          "type": "Primary"
        }
      ]
    }
  }
}

​

Submitting a selfie

{
  "instanceId": "your-instance-id",
  "interactionId": "your-interaction-id",
  "participants": [
    { "domainElementId": "Selfie" }
  ],
  "context": {
    "subject": {
      "biometrics": [
        {
          "selfieImage": "<base64-encoded-image>"
        }
      ]
    }
  }
}

​

Submitting a Social Security Number (SSN)

{
  "instanceId": "your-instance-id",
  "interactionId": "your-interaction-id",
  "participants": [
    { "domainElementId": "SSN" }
  ],
  "context": {
    "subject": {
      "identity": {
        "idNumbers": [
          {
            "idNumber": "123-45-6789",
            "type": "ssn"
          }
        ]
      }
    }
  }
}

​

Submitting date of birth only

{
  "instanceId": "your-instance-id",
  "interactionId": "your-interaction-id",
  "participants": [
    { "domainElementId": "DateOfBirth" }
  ],
  "context": {
    "subject": {
      "identity": {
        "dateOfBirth": "1990-01-01"
      }
    }
  }
}

​

Submitting partial identity data

• Through the v2 API error response
• Through the Investigation portal.

​

v2 API error responses

{
  "errors": [
    {
      "code": "4002",
      "name": "MISSING_FIELD",
      "location": "Body",
      "problem": "problem description goes here",
      "action": "action to resolve the issue goes here"
    }
  ]
}

​

Investigation portal

1. Log in to the GBG GO platform and navigate to the Investigation section.
2. Click the Session ID of the session you want to review. This opens the session detail view, which shows an overview of the session.
3. Navigate to the Processing tab to see each module’s outcome, for example, Match, No Match, or Error.
4. Expand any module section to see a breakdown of individual data point matches.
5. Click More details to open the module detail view. The available tabs vary by module type.
6. Check the Raw Response tab for the complete response from the verification provider, which contains the module errors and reasons.