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.
• Task: A task is an action a user must complete within a journey, such as providing identity details, uploading a document, or performing biometric verification. When you retrieve tasks, the response describes which tasks are assigned to the journey instance. Each task has a unique taskId and moves through the Assigned, In Progress, and Completed stages as the journey progresses.
• 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.

• Synchronous (default): When you call /journey/start in prefill mode, the response returns only after all modules have finished processing. This is convenient for short-running journeys but can cause timeout issues for long-running verification flows.
• Asynchronous: Set "async": true inside the config object on the /journey/start request. The call returns an instanceId immediately and processing happens in the background. Use this mode to avoid timeouts.

{
  "resourceId": "your-resource-id@latest",
  "context": {
    "config": { "async": true },
    "subject": {
      "identity": { "firstName": "Jane", "lastNames": ["Doe"] }
    }
  }
}

• "async": true: The /journey/start call returns the instanceId immediately and module processing happens in the background. Use this for long-running prefill journeys to avoid timeouts.
• "async": false (or omitted): The journey runs synchronously. The response returns only after all modules have finished processing.

{
  "resourceId": "your-resource-id@latest",
  "context": {
    "config": { "async": true },
    "subject": {
      "identity": {
        "firstName": "Jane",
        "lastNames": ["Doe"],
        "dateOfBirth": "1992-10-01"
      }
    }
  }
}

{
  "resourceId": "your-resource-id@latest",
  "context": {
    "subject": {
      "documents": [],
      "biometrics": []
    }
  }
}

{
  "resourceId": "your-resource-id@latest",
  "context": {
    "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.

{
  "intent": "Complete",
  "instanceId": "your-instance-id",
  "taskId": "your-task-id",
  "context": {
    "subject": {
      "documents": [
        {
          "side1Image": "<base64-encoded-image>",
          "side2Image": "",
          "type": "Primary"
        }
      ]
    }
  }
}

​

Submitting a selfie

{
  "intent": "Complete",
  "instanceId": "your-instance-id",
  "taskId": "your-task-id",
  "context": {
    "subject": {
      "biometrics": [
        {
          "selfieImage": "<base64-encoded-image>"
        }
      ]
    }
  }
}

​

Submitting a Social Security Number (SSN)

{
  "intent": "Complete",
  "instanceId": "your-instance-id",
  "taskId": "your-task-id",
  "context": {
    "subject": {
      "identity": {
        "idNumbers": [
          {
            "idNumber": "123-45-6789",
            "type": "ssn"
          }
        ]
      }
    }
  }
}

​

Submitting date of birth only

{
  "intent": "Complete",
  "instanceId": "your-instance-id",
  "taskId": "your-task-id",
  "context": {
    "subject": {
      "identity": {
        "dateOfBirth": "1990-01-01"
      }
    }
  }
}

​

Submitting partial identity data in prefill mode

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

​

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

1. Sign in to GBG GO and click Investigation in the left navigation menu.
2. Click the Session ID of the session you want to review. The session details page opens.
3. Use the following tabs to view different parts of the submitted data:

1. Click Add Filter.
2. Select a filter (for example, Name, Email, Trust Score, Decision) and click Add Filter.
3. Apply additional filters as needed — the number of applied filters appears next to the filter button.
4. Click Apply Filter. Use Clear All to reset.

1. Hover over a column title and click the three dots that appear.
2. Choose Sort by ASC or Sort by DESC. You can sort by Session ID, Name, Decision, Started date, and other columns.

1. Click the Session ID of the session.
2. Review the session details, including processing modules, user data, and documents.
3. Select a new decision from the list. The default options are:
   • Decision: Accept
   • Decision: Manual review
   • Decision: Reject
4. (Optional) Add a note in the Note field explaining the reason for the change.
5. Click Change decision to confirm.

1. Select the checkbox next to the session.
2. Click Change Decision.
3. Select a new decision, optionally add a note, and click Change decision.

1. Sign in to GBG GO and click Investigation.
2. Click the Session ID of the session you want to export.
3. Click Export in the top-right corner of the session details page. The Export session dialog appears.
4. Click Export to PDF. The file downloads to your device automatically.