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

# GBG Go Release Notes

> All notable changes related to GBG Go functionalities will be documented in this page. To receive notifications about new releases, please subscribe to the RSS feed.

**October 14th, 2026**

## October releases

The releases for October 14th, 2026 add the Biometric Onboarding module and failed-step details in the slim response, and fix several issues.

### New features

* **Biometric Onboarding module.** Released the [Biometric Onboarding](/docs/go-v2/platform/modules/biometrics/biometric-onboarding.md) module to production. Its **Biometrics Onboarding** variant combines face matching and liveness detection to confirm a person's identity at onboarding.

* **Injection attack detection for onboarding.** The module's **Biometrics Onboarding with Injection Attack Detection** variant adds protection against injection attacks, using an encrypted selfie.

* **Name your own consent agreement.** A journey can now link its consent screen to your own agreement document, instead of the GBG Biometric Notice. The agreement's address is also recorded as the `url` of the consent record.

### Improvements

* **Failed module steps in the slim response.** On `journey/state/fetch` and `interaction/fetch` with `?view=slim`, each failed module step now shows `status: 'error'` with an error that explains it. `result.errors` lists one entry per failed step, in step order, even when the journey completes.

* **Digital Identity Results settings.** You can now set the timeout and the maximum number of checks for the [Digital Identity Results](/docs/go-v2/platform/modules/others/digital-identity.md#digital-identity-digital-identity-results) step in the **Journey builder**. If you save the settings unchanged, the defaults are 15 minutes and 10 checks.

* **Test embedding from localhost.** A delivery's embedding origins can now include `https://localhost` or `http://localhost`, with or without a port, in every environment. Other `http` origins are still refused in production.

- **History API response.** A default **History API** read no longer returns `context.subjectSources` or `context.results`, matching the state response.

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-18855** | Fixed an issue where a name matching module received the name read from the document, not the name the applicant entered. The module now compares the two as intended. |
| **GGO-19468** | Fixed an issue where `journey/state/fetch` could return `context.process.steps` out of execution order. Steps now appear in the order they ran. |
| **GGO-18864** | Fixed an issue where a source requirement on part of a name or address was ignored when a module wrote the whole value. The requirement is now enforced, for example on `FullName/firstName`. |
| **GGO-19200** | Fixed an issue where the **US instance** variants of **PEPs and Sanctions** showed No Hit in the **Investigation Portal** for every match. Matched watch lists now appear when your account returns watch list details. |
| **GGO-16966** | Fixed an issue where adverse media matches from older records showed no hit in the **Investigation Portal**. Match details are now grouped by category and keep every record. |
| **GGO-17642** | Fixed an issue where the **Digital Identity Results** step gave up within seconds when its settings had never been saved. It now keeps checking for about 68 minutes. Republish journeys to apply the fix. |

**September 30th, 2026**

## September releases

The releases for September 30th, 2026 add new document and identity elements, new module variants and limits on interaction requests, and fix several issues.

### New features

* **New Australian document elements.** The **Australia DVS Security Identification Card** element covers ASIC and MSIC cards. The **Australia DVS Change of Name Certificate** element records a change of name, including the previous names.

  These elements can be supplied when you start a journey or produced by a module.

* **New identity elements.** **Passport**, **Driving Licence** and **Birth Certificate** record the issuing country as a field, so one element serves every country. **Aliases** records other names a person uses, and **Nationality** records the nationality they declare.

  These elements can be supplied when you start a journey or produced by a module.

* **Resume an unfinished journey.** An applicant who closes the page can reopen the same link in the same browser and carry on where they stopped. Resume is on by default for every delivery.

  The resume window starts at the applicant's first visit and does not extend when they return. The default is 7 days, and a delivery can ask for up to 30 days. The window never outlasts the journey's data retention period.

  To turn resume off, set `resumeMode` to `off` in `linkConfig` on the journey start request. For hosted journeys, the resume credential is bound to the browser that obtained it.

* **Your own SMS invite wording.** A delivery or organisation can now set its own text for single-user SMS invites in `linkConfig.smsInviteMessage`. Use `{{inviteUrl}}` and `{{firstName}}` in the text, and the link is added if you leave it out.

* **Document Attachments module.** Released the [Document Attachments](/docs/go-v2/platform/modules/documents/document-attachments.md) module to production. You can add it to journeys from the Low Code canvas.

* **Business Insights variants.** Released the **Global Business Entity Verification** and **Global Business Officer Verification** variants of the [Business Insights](/docs/go-v2/platform/modules/others/business-insights.md) module to production.

  Entity verification checks a business name and address against official sources. Officer verification checks that a person is a registered officer of the business.

* **Device Intelligence module.** Released the **Device Intelligence** module to production, with **Single Tenant** variants for the US, Australia and the EU, and a **Consortium** variant. It assesses device, network and behavioural signals to support fraud decisions.

  These variants are available through the API, not yet from the Low Code canvas.

* **New Data Verification variants.** Released 40 new variants of the [Data Verification](/docs/go-v2/platform/modules/data/data-verification.md) module to production:

  * **Australia:** Driver Licence, Passport, Visa, Citizenship Certificate, Electoral Roll, Credit Header 2, Event Member Data and Residential.

  * **Europe:** consumer, residential, utility and credit bureau sources for France, Spain, Italy, Germany, Belgium, the Netherlands, Poland, Austria, Ireland and Switzerland.

  * **United States:** Phone, Phone 2, Consumer, Financial Services and Residential.

  * **Brazil:** National ID, Residential and Tax Registration.

  * **Asia:** India Aadhaar card and China National ID.

  Apart from **Australia - Electoral Roll**, these variants are available through the API, not yet from the Low Code canvas. The five Australian government checks run in the Australian region only.

### Improvements

* **Interaction request limits.** Interaction submit and asset upload requests from an applicant's device are now rate limited per journey instance. A request over the limit returns `429` with a `Retry-After` header.

  A submit request body is limited to 32 MB, and a larger body returns `400`. A request can carry at most 50 documents, 50 biometric entries and 25 inline images.

* **Australian document fields.** The **Australia DVS Marriage Certificate** element gains `documentNumber` and `issueDate`, and `registrationNumber` is now optional on birth and marriage certificates. The **Australia DVS Centrelink Concession Card** element now stores the cardholder's `fullName`.

* **Business entity fields.** `dissolutionDate` is now optional, `headcount` must be a whole number, and an associated person's `nationality` is a country code.

* **Bank accounts identified by IBAN.** A bank account in `subject.accounts[]` can now carry `iban` without `accountNumber`. Each account needs at least one of the two, and a module that requires `accountNumber` still needs it.

* **Token request documentation.** The published OpenAPI specification now shows `scope=gbg.token` as required on client credentials token requests. Generated clients that left it out could not get a token.

* **More variants on the Low Code canvas.** **US Taxpayer Verification**, **Canada - Credit Bureau - FINTRAC 1** and **FINTRAC 2** can now be added from the Low Code canvas. So can **US: Credit Bureau 1**, **2** and **3**.

* **Manual review notes in results.** The two-button [Manual Review](/docs/go-v2/platform/modules/utilities/manual-review.md#manual-review-manual-review-2-button) variant now saves the reviewer's note with the decision. The **Investigation Portal** shows both with the session's results.

* **UK CRA Combined Decision on Low Code journeys.** The [UK CRA Combined Decision](/docs/go-v2/platform/modules/utilities/cra-combined-decision#uk-cra-combined-decision) variant now works on Low Code journeys. It combines the results of the **UK: Credit Bureau 1**, **2** and **3** checks.

  Place an evaluation step between the credit bureau checks and the combined decision, so that it runs after them.

* **Name Match on Low Code journeys.** [Name Match](/docs/go-v2/platform/modules/others/name-match.md) now works on Low Code journeys, with a **Document Extraction** step as its input. It compares the name on the document with a name the applicant enters, never with itself.

  **Action required.** Review journeys that use Name Match. On Low Code journeys, collect the name from the applicant, because a prefilled name does not run the check.

* **New Zealand data verification outcomes.** **New Zealand - Credit Header 2** and **New Zealand - Land Titles** now need a stronger match for Identity Match. **New Zealand - Credit Header 3** adds 10 outputs and raises an alert for a lost or stolen ID.

  **Action required.** Review journeys that route on these variants' default outcomes.

* **Spain - Utility outputs.** The **Spain - Utility** variant replaces its middle name and generic phone results with ID card, mobile phone and landline results. Last name is now optional.

  **Action required.** Update rules that use the removed results.

* **Webhook retries.** The **Webhook** variant now retries a request up to 3 times when the receiving server returns a temporary error. Each request times out after 30 seconds.

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-17881** | Fixed an issue where `?view=slim` returned no status for abandoned and in-progress journeys, which could read as success. These journeys now report `error` and `pending`. |
| **GGO-18326** | Fixed an issue where the title and **Continue** bands were transparent, so content scrolled visibly beneath them. The bands are now opaque. |
| **GGO-18082** | Fixed an issue where a business address submitted as several fields reached the verification module as a single field, so the address could not match. The full address now reaches the module. |
| **GGO-18658** | Fixed an issue where bold text set in screen copy showed literal `[b]` tags. Bold text now displays as expected. |
| **GGO-18426** | Fixed an issue where an address component supplied at journey start was removed when the applicant submitted the rest of the address. The component is now kept. |
| **GGO-17633** | Fixed an issue where a sub-organisation running a parent's journey lost the parent's screen customisations. These customisations now apply as expected. |
| **GGO-17982** | Fixed an issue where additional documents submitted together were duplicated in `subject.documents`. Each document now appears once. |
| **GGO-17407** | Fixed an issue where reviewer notes submitted with a manual review decision were dropped. Notes of up to 500 characters now reach the module. |
| **GGO-18153** | Fixed an issue where US data verification and US PEPs and Sanctions checks returned a generic error for missing data or credential problems. They now return a specific input or configuration error. |
| **GGO-18275** | Fixed an issue where US data verification variants ignored a supplied SSN, so SSN results and outcomes were wrong. The SSN is now matched. |
| **GGO-18532** | Fixed an issue where an identity document with no type or number made the whole data verification check fail. Such documents are now skipped. |
| **GGO-17565** | Fixed an issue where a customer reference supplied at journey start was not passed to data verification and UK PEPs and Sanctions checks. It is now passed through. |
| **GGO-18216** | Fixed an issue where **PEPs and Sanctions Standard** variants ignored the **Birth Year +/- Range** setting and matched the same birth year only. The setting now applies. |

**August 30th, 2026**

## August releases

The releases for August 30th, 2026 add new domain elements, new modules and variants, and changes to delivery links and the Schema API.

> [!NOTE]
>
> Some changes in this release need action from integrators. Each one is marked **Action required**.

### New features

* **New domain elements.** The following elements are now available to journeys and modules:

  * **Australia DVS Visa**, for an Australian visa number.

  * **Consent**, for an explicit consent record.

  * **Stored Face**, a reference to a face template held by a supplier, for reverification.

  * **Entity Person Address**, the home address of a person associated with a business.

* **OpenAPI specification in YAML.** `GET /v2/captain/openapi.yaml` now serves the specification as YAML, alongside the existing JSON version.

* **User Invite module.** Released the [User Invite](/docs/go-v2/platform/modules/utilities/user-invite.md) module to production. Its **Single User Invite** variant sends the applicant a link to complete a journey by SMS, by email, or both.

* **Business Insights module.** Released the [Business Insights](/docs/go-v2/platform/modules/others/business-insights.md) module to production, with the **US Taxpayer Verification** variant. It verifies the name, address and taxpayer identification number of a US business and an associated person.

* **Digital ID Provider Selector.** Released the [Digital ID Provider Selector](/docs/go-v2/platform/modules/others/digital-identity.md#digital-id-provider-selector) variant of the **Digital Identity** module to production. It returns the identity providers your account can use in `result.note.providers`.

  Supply a country, state or mobile number in E.164 format to rank the providers, with recommended providers first. Ranking needs the **Verification Profile Id** credential, so save your stored credentials again before you use it.

* **Japan - Single Source.** Released the **Japan - Single Source** variant of the [Data Verification](/docs/go-v2/platform/modules/data/data-verification.md) module to production. It checks a person's name, address, date of birth and document details.

### Improvements

* **Delivery links last 7 days by default.** An unconfigured link now lasts 7 days instead of 24 hours. Set `linkConfig.ttlMinutes` for a shorter lifetime.

  **Action required.** No link can last more than 7 days, and a longer requested lifetime is reduced to 7 days without an error. `deliveryUrlTtlMinutes` still works but is deprecated in favour of `linkConfig.ttlMinutes`.

* **Schema API uses short IDs.** `POST /v2/captain/journey/schema/fetch` now takes the same `resourceId` as the journey start request, for example `my-delivery@latest`, and takes the organisation from your token. The response returns `deliveryId` and `resolvedVersion`, which together pin a journey start to that exact version.

  **Action required.** The `grId` request member has been removed, and the response no longer contains full resource names. A request that sends `grId` receives `400`.

* **Business entity data.** The legal form of a business, such as `LLC` or `plc`, has moved from `subject.entities[].type` to `subject.entities[].businessType`. The `PrimaryEntity/type` reference is now `PrimaryEntity/businessType`.

  **Action required.** A request that sends the legal form in `subject.entities[].type` now receives `400`. Journeys and modules that reference `PrimaryEntity/type` must change to `PrimaryEntity/businessType`.

* **Millisecond ordering for journey events.** Journey action events now carry `createdAtMs`. Order a journey's events by instance ID and `createdAtMs`, and fall back to `createdAt` for older events.

* **Facematch Score.** The [Facematch Verification - NIST](/docs/go-v2/platform/modules/biometrics/facematch-verification.md#facematch-verification-nist) variant is now named **Facematch Verification - NIST Accredited**. It adds a **Facematch Score** capability from 0 to 100 for your own outcome rules, and the default outcomes are unchanged.

* **PEPs and Sanctions datasets and score.** The [PEPs and Sanctions Standard](/docs/go-v2/platform/modules/compliance-screening/peps-and-sanctions.md#peps-and-sanctions-standard) variants can now search the Disqualified Directors, Profile of Interest and Regulatory Enforcement datasets. A new **Decision score** capability reports the top match score from 0 to 100.

  Each dataset you select is billed separately.

* **Document type and country name values.** In the **Document Classification V2** and **Document Verification** variants, the document type value `Driving License` is now `Drivers License`. Country name values now follow ISO 3166-1, adding missing countries and correcting or removing others.

  **Action required.** Update any outcome rule that uses a renamed or removed value.

* **Canada FINTRAC outcomes.** The **Canada - Credit Bureau - FINTRAC 1** and **FINTRAC 2** variants replace Identity Match with four outcomes, one per FINTRAC verification method.

  **Action required.** Review and republish journeys that route on Identity Match from these variants.

* **PEPs and Sanctions match rule.** A **PEPs and Sanctions Standard** result is now a match whenever the search returns a match, even without PEP, sanctions or adverse media details. Some journeys might now see a match where they previously saw none.

  **Action required.** Review journeys that route on the PEPs and Sanctions result.

* **Digital Identity error format.** **Digital Identity** errors now use the standard `result.error.errors[]` format, with the HTTP code in `originalError`.

  **Action required.** Update integrations that read `result.errors` from this module.

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-17782** | Fixed an issue where submitting a screen twice completed the next screen without collecting any data. A duplicate submit is now ignored. |
| **GGO-17571** | Fixed an issue where a partial submit after the first stage of a journey stopped the journey from progressing. These journeys now continue as expected. |
| **GGO-17881** | Fixed an issue where an abandoned journey returned no errors from `journey/state/fetch`. The response now lists each blocked step and missing input. |
| **GGO-16017** | Fixed an issue where the completion notification webhook was not sent for most organisations. Completion notifications now send as expected. |
| **GGO-17785** | Fixed an issue where a delivered completion notification was not recorded on the journey. `journey/state/fetch` now shows the notification step. |
| **GGO-17240** | Fixed an issue where GBG SIP modules, including the UK National Fraud Database, failed to deploy or rejected every request. The **History API** also no longer returns internal process configuration values. |
| **GGO-16965** | Fixed an issue where a module placed twice in a journey could not be addressed separately in evaluation rules. Each placement now has its own identifier. |
| **GGO-17878** | Fixed an issue where a business journey start failed when an address had no `purpose`. Addresses without a purpose now start as expected, and all five purpose values can be submitted. |
| **GGO-16688** | Fixed an issue where the **Digital Identity** module appeared in the Journey builder palette as Name Match. It now shows its own name and description. |
| **GGO-17310** | Fixed an issue where the **Netherlands: Single match consumer \[Legacy]** variant listed two Phone Match capabilities in the rules editor. The second now reads Email Match. |

**July 30th, 2026**

## July releases

The releases for July 30th, 2026 change how the anchor image is produced across the v2 document module variants, and update where **Document Authentication V2** runs in a journey.

### New features

*No new standalone features were introduced in this release.*

### Improvements

* [Document Classification V2](/docs/go-v2/platform/modules/documents/document-classification.md) now outputs the anchor image. The variant produces the anchor image alongside its classification results, so the image is available earlier in the journey and can be consumed by parallel branches rather than waiting for extraction to complete.

* [Document Extraction V2](/docs/go-v2/platform/modules/documents/document-extraction.md) no longer outputs the anchor image. The image is already produced by **Document Classification V2** earlier in the journey, so the output has been removed from this variant to avoid duplication. **Document Extraction V2** continues to extract data fields such as name, date of birth, document number, and expiry date.

* [Document Authentication V2](/docs/go-v2/platform/modules/documents/document-authentication.md) now depends on both **Document Classification V2** and **Document Extraction V2**. Place the variant after both modules in your journey. The supported module order is **Document Classification V2**, then **Document Extraction V2**, then **Document Authentication V2**.

> [!NOTE]
>
> These changes apply to the v2 document module variants only. The v1 variants are unaffected.

### Bug fixes

*No bug fixes were introduced in this release.*

**July 24th, 2026**

## July releases

The releases for July 24th, 2026 improve how module variants are presented in the Journey Builder.

### New features

*No new standalone features were introduced in this release.*

### Improvements

Re-ordered the variants in each module's variant drop-down list into alphabetical order, making it quicker to find and select the variant you need.

### Bug fixes

*No bug fixes were introduced in this release.*

**July 21st, 2026**

## July releases

The releases for July 21st, 2026 introduce response profiles on the journey APIs, letting you choose how much detail a response carries.

### New features

Added response profiles to the [`/journey/state/fetch`](/docs/go-v2/api-reference/endpoint/fetch-journey-state) and [`/journey/interaction/fetch`](/docs/go-v2/api-reference/endpoint/fetch-interaction) endpoints. Use the `view` query parameter to control how much detail the response carries:

| Value | Description |
| - | - |
| `full` | Returns the complete response. This is the default. |
| `slim` | Returns a streamlined response containing only the verified results of the journey. |

The slim response returns a `result.data` object containing only verified module output. It excludes the data originally submitted, captured images, and diagnostic detail.

> [!NOTE]
>
> The default remains `full`, so this change is backward compatible. Existing integrations continue to work unchanged.

### Improvements

Added an additional way to authorise session export in the Investigation Portal, so that export can be enabled for your organisation through your access permissions.

### Bug fixes

*No bug fixes were introduced in this release.*

**July 16th, 2026**

## July releases

The releases for July 16th, 2026 let you delete selected personal data from a session in the Investigation Portal.

### New features

Added the option to delete selected personal data from a session in the Investigation Portal. On the session detail page, you can now remove one category at a time, rather than deleting the whole session. You can delete any of the following:

* Personal information
* Documents
* Biometrics

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-16495** | Fixed an issue where the **Publish to Production** button stayed disabled for some journeys, preventing them from being published. Affected journeys can now be published to production. |

**July 13th, 2026**

## July releases

The releases for July 13th, 2026 make journey results easier to consume from the API, add new domain elements for Australian certificates, and fix a number of issues across journey execution and the Investigation Portal.

### New features

Added new domain elements for Australian Birth Certificate and Marriage Certificate documents. The new fields cover registration number, certificate number, registration date and year, marriage party, and spouse names.

### Improvements

* Promoted the overall journey result to the response root. The [`/journey/state/fetch`](/docs/go-v2/api-reference/endpoint/fetch-journey-state) and [`/journey/interaction/fetch`](/docs/go-v2/api-reference/endpoint/fetch-interaction) endpoints now return the journey result as `response.result`, so you no longer need to read it from the nested `context.result`.

* Added the step name to each entry in `steps[]`. Entries now include a readable `name` alongside `nodeId`, so you can show which check ran without looking it up in the journey configuration.

* Added decision and evaluation nodes to `steps[]`. Responses now show which branch a journey took and why.

* Added support for the OAuth 2.0 `client_credentials` grant. Tokens issued through this grant are now accepted, where they were previously rejected with a `401` response.

* Documented how each `emails[].type` value maps to its domain element in the API reference. The values map as follows:

  | Value | Domain element |
  | - | - |
  | `personal` | `PersonalEmail` |
  | `work` | `WorkEmail` |
  | `other` | `OtherEmails` |

* Corrected the API reference to show `type` as required on document submissions. The field has always been required, so document submissions must include it.

* Updated the Investigation Portal to show a Pass/Fail result rather than a score for the **Biometrics Reverification** variant.

* Removed the **Relevance** column from the **Document Authentication V2** validation tab in the Investigation Portal, as it doesn't apply to this variant.

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-16689** | Fixed an issue where some journey events did not appear in the Investigation Portal. Affected events are now displayed correctly. |
| **GGO-16595** | Fixed an issue where an unsupported or unclassified document caused the journey to repeatedly ask the user for more captures. |
| **GGO-16554** | Fixed an issue where Hosted journeys couldn't be completed when verifying a US address. The address lookup now supplies the address detail the module requires, so these journeys complete as expected. |
| **GGO-16368** | Fixed an issue where a journey failed to publish when a Data Verification variant was placed before the step that provides its data. Affected journeys now publish correctly. |
| **GGO-16185** | Fixed an issue where some journeys did not apply the outcome of a branch, and used the default outcome instead. Branch outcomes are now applied correctly. |
| **GGO-15915** | Fixed an issue where the Investigation Portal did not apply the custom colours configured on evaluation outcomes. Decision chips and icons now display in their configured colours. |
| **GGO-13648** | Fixed an issue where the Investigation Portal hid the backside tab for a document whose back could not be classified. The tab is now always shown. |

**July 2nd, 2026**

## July releases

The releases for July 2nd, 2026 introduce a new module to production for biometric identity verification.

### New features

Released the [Biometrics Reverification](/docs/go-v2/platform/modules/biometrics/biometrics-reverification.md) module to production.

**June 30th, 2026**

## June releases

The releases for June 30th, 2026 introduce three new module variants to production for document and biometric identity verification.

### New features

Released the following module variants to production:

* [Liveness Verification with Injection Attack Detection](/docs/go-v2/platform/modules/biometrics/liveness-verification.md#liveness-verification-with-injection-attack-detection)
* [Facematch Verification - NIST](/docs/go-v2/platform/modules/biometrics/facematch-verification.md#facematch-verification-nist)
* [Document Verification](/docs/go-v2/platform/modules/documents/document-verification.md)

**June 18th, 2026**

## June releases

The releases for June 18th, 2026 focus on journey publishing reliability.

### New features

*No new standalone features were introduced in this release.*

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-16016** | Fixed an issue where a journey failed to publish when two variants in the same linear segment defined the address field differently. One using granular address inputs such as building, thoroughfare, and locality, and the other using a single combined address object. Journeys with mixed address configurations now publish successfully. |

**June 16th, 2026**

## June releases

The releases for June 16th, 2026 introduce Designer-level management of iframe embedding allowlists, along with audit logging for cross-organization access decisions.

### New features

Added a Designer interface for managing which domains are permitted to embed a journey in an iframe. Designers and org admins can now configure embedding allowlists directly at the delivery level or as organisation-wide defaults. This is without editing JSON or calling APIs. The interface includes built-in validation, clear limits, and messaging that embedding stays blocked by default until origins are added.

### Improvements

Added audit logging for cross-organisation access decisions in partner and sub-organisation journeys. Every allow or deny decision is now recorded with full context, including the requesting and target organisations, the outcome, the reason, and the user. Details are searchable by organisation, user, time range, and outcome in the Investigation Portal audit view.

### Bug fixes

*No bug fixes were introduced in this release.*

**June 11th, 2026**

## June releases

The releases for June 11th, 2026 focus on Investigation Portal accuracy for biometric and compliance screening results.

### New features

*No new standalone features were introduced in this release.*

### Improvements

Updated the Investigation Studio to display Biometrics Reverification module results as clear Pass/Fail outcomes rather than raw scores. Reviewers now see the overall result alongside individual outcomes for IAD Capture Liveness, Face Liveness, and Face Match, with both the selfie and trusted anchor image shown.

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-15445** | Fixed an issue where PEP-by-association hits from Direct PEPs and Sanctions v2 displayed insufficient detail in the Investigation Portal, preventing reviewers from assessing potential matches at onboarding. The portal now surfaces the full association breakdown, including who the individual is associated to and links to supporting evidence. |
| **GGO-15880** | Fixed an issue where Adverse Media hits from PEPs and Sanctions v2 journeys were not rendered in the Investigation Portal, leaving reviewers without the match detail. Adverse Media results now display at full parity with PEPs and Sanctions hits, including the match details and source context. |

**June 4th, 2026**

## June releases

The releases for June 4th, 2026 introduce a set of document and biometric module variants to production, available exclusively as Hosted journeys through Flow Captain v2.

### New features

Released the following document and biometric module variants to production:

* [Document Classification v2](/docs/go-v2/platform/modules/documents/document-classification.md)
* [Document Extraction v2](/docs/go-v2/platform/modules/documents/document-extraction.md)
* [Document Authentication v2](/docs/go-v2/platform/modules/documents/document-authentication.md)
* [Facematch Verification v2](/docs/go-v2/platform/modules/biometrics/facematch-verification.md)
* [Liveness Verification v2](/docs/go-v2/platform/modules/biometrics/liveness-verification.md)
* [Chip Authentication](/docs/go-v2/platform/modules/documents/nfc-chip-authentication.md)

These variants are available only as hosted journeys through Flow Captain v2.

> [!NOTE]
>
> The v1 **Facematch Verification** and **Liveness Verification** variants are not supported in v2.
>
> The following v1 document variants remain supported in v2:
>
> * Document Classification v1
> * Document Extraction
> * Document Authentication v1

### Improvements

Renamed the biometric image inputs for clarity. Across the biometric modules in v2, the inputs previously referred to as `face1Image` and `face2Image` are now `selfieImage` and `anchorImage`.

The selfie image is the photograph captured from the end user during the journey, and the anchor image is the reference image it is compared against.

### Bug fixes

*No bug fixes were introduced in this release.*

**June 2nd, 2026**

## June releases

The releases for June 2nd, 2026 focus on Investigation Portal accuracy and report export reliability.

### New features

*No new standalone features were introduced in this release.*

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-15324** | Fixed an issue in the Investigation Portal where Document, Biometrics Liveness, and FaceMatch modules failed to display their images and result data. The modules could also show failure indicators despite completing successfully. These modules now render their images, extracted data, and match scores correctly. |
| **GGO-15537** | Fixed an issue where the Export button in report views was greyed out and unselectable, preventing users from downloading reports as PDF. Report export now works as expected. |

**June 1st, 2026**

## June releases

The releases for June 1st, 2026 introduce evaluation outcome classification and consolidated audit logs in the Journey Builder, along with fixes to biometric processing and module configuration.

### New features

* Added the ability to classify evaluation outcomes as **Positive**, **Negative**, or **Neutral** directly in the Journey Builder, enabling richer analytics and clearer interpretation of journey decisions at a glance.

  > [!NOTE]
  >
  > Classification is optional and fully backward compatible. Existing journeys continue to work unchanged, with unclassified outcomes appearing as "unclassified" in reporting.

* Added Investigation audit logs to the Journey Builder **Audit log** page through a new tabbed view, letting admins review both journey and investigation activity from a single, consistent interface.

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-15402** | Fixed an issue where biometric images supplied at journey start were lost during document processing, causing Liveness and FaceMatch steps to hang until timeout. Biometrics are now preserved correctly so verification completes as expected. |
| **GGO-15495** | Fixed an issue in the Journey builder where switching between two placed modules could cause a module's sidebar to revert to its default variant. Instead of the one actually configured. Modules now correctly retain their placed variant when navigating between them. |

**May 29th, 2026**

## May releases

The releases for May 29th, 2026 introduce the Document module v2 variants to production for document-based identity verification.

### New features

Released the Document module v2 variants to production. The variants include:

* [Document Classification v2](/docs/go-v2/platform/modules/documents/document-classification.md)
* [Document Extraction v2](/docs/go-v2/platform/modules/documents/document-extraction.md)
* [Document Authentication v2](/docs/go-v2/platform/modules/documents/document-authentication.md)

This release provides improved performance and efficiency for document-based identity verification workflows through Captain v2 orchestration, while maintaining full backward compatibility with existing v1 journeys.

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

*No bug fixes were introduced in this release.*

**May 7, 2026**

## May releases

GBG Go V2 — the next-generation Journey Orchestrator — is now live in production.

GBG Go V2 is the runtime that executes your journeys end-to-end: it owns journey state, dispatches modules, validates interaction inputs and outputs, and emits the events that drive the Investigation Portal and your downstream pipelines. The cutover from the previous orchestrator is transparent to existing journeys — your published journeys continue to run unchanged — and brings the new capabilities and contracts described below. See the [V1 to V2 Migration Guide](/docs/go-v2/migration/v1-to-v2-migration-guide.md) for details on how to migrate.

### New features

* **Granular domain elements.** Interaction inputs and outputs now travel as discrete domain elements with full provenance. Pre-fill values are preserved across steps even when the same field is collected more than once, and downstream consumers can see which step in a journey produced each value.
* **Parallel module execution within a linear segment.** When a journey segment contains independent modules, Go v2 now runs them concurrently, reducing end-to-end journey latency on multi-module flows.
* **Module re-execution within a journey.** A module can be executed more than once within the same journey instance — useful for retry, multi-document capture, and re-attempt patterns.
* **Terminate-node interaction screens.** Journeys can now display a final interaction screen at terminate nodes, so end users see a definitive completion or rejection message rather than the journey ending silently.
* **Design-time Schema API.** `POST /journey/schema/fetch` returns the interaction schema for a journey, derived from the published configuration, so Designer and integrating clients can render and validate against the exact contract Go will enforce at runtime.
* **OnboardChildOrg.** A new use case onboards child organisations with reciprocal parent/child relationships, retention policy, and a test-account flag. Child orgs are immediately able to consume shared resources via `@ref`.
* **Configurable data retention per organisation.** Progress events written to your S3 bucket now carry a `RETAIN-<duration>` object tag derived from the org's retention duration, so lifecycle rules can enforce retention without per-bucket configuration.
* **Automatic 30-day journey-data cleanup.** Journey state older than 30 days is now purged automatically, in line with REQ-04-025.
* **OAuth2 credential resolution.** Delivery credentials can now be resolved through an OAuth2 token-exchange flow, with multi-client registry support, retry, exponential backoff, and concurrent-request deduplication.
* **Brand resolution.** A deterministic three-step brand-resolution chain selects the correct brand (logo, copy, theme) for an end user, including across child-org journeys.
* **Iframe embedding allowlist.** Journeys can only be embedded by origins on a configured allowlist, enforced at the platform via `frame-ancestors` and `X-Frame-Options`.
* **Loqate runtime injection.** The address-lookup card now receives its Loqate API key at journey execution time, so a single journey definition works across customers without rebuilding.
* **Interaction events to S3.** `INTERACTION_STARTED` and `INTERACTION_COMPLETED` are now forwarded to your progress-events bucket alongside module events.
* **GBG Errors Catalog.** Go v2 API error responses follow the platform-wide [GBG Errors Catalog](/docs/go-v2/developer-integration/error-handling.md) format — stable `code`, `type`, and `details` shape — replacing the ad-hoc error shapes of the previous orchestrator.
* **JOURNEY\_ABANDONED event.** Go v2 records an explicit `JOURNEY_ABANDONED` event when a journey times out or is terminated, so abandonment is visible to the Investigation Portal and progress consumers as a first-class outcome.
* **Journey deletion endpoint.** Journey instances can be deleted explicitly via API (REQ-02-002), supporting right-to-be-forgotten workflows.

### Improvements

* **Higher throughput, lower latency.** Go v2 is a ground-up rewrite on a modern runtime. Per-request CPU and memory footprint are materially lower than the previous orchestrator, and replica counts and HPA targets have been tuned for production load.
* **Production-grade resilience.** Per-dependency timeouts, retry policies, and circuit breakers are tuned for production traffic (GGO-13550). Failures in a downstream module no longer cascade into journey-wide outages.
* **Token hardening.** Device and end-user JWTs now carry explicit `aud` and `scope` claims and enforce TTLs. The `Authorization: Bearer` header is the sole supported credential transport — body credential fallbacks have been removed (REQ-01-003).
* **Structured logging with PII filtering.** Logs are emitted as structured JSON with a PII-filter stage on the stdout path, suitable for ingestion by Coralogix and downstream pipelines.
* **Configurable journey context size limit.** The maximum journey-context payload size is now controlled by an environment variable, so high-data journeys can be enabled without code changes.
* **`/version` endpoint enriched.** Go's version endpoint now reports the build timestamp and the versions of bundled GBG dependencies (schema, flow compiler, end-user app/lib), so deployed builds can be identified unambiguously from the outside.
* **Server-side schema-error volume capped.** Go bounds the number of schema-validation errors returned per request, preventing unbounded log volume from pathological payloads.
* **Service-principal allowlist for Flowable events.** Go v2 only accepts Flowable callbacks from a configured set of service principals (GGO-13550).
* **Compiler version in deployment cache key.** Module deployments are cached against the flow-compiler version, so a compiler bump correctly invalidates stale deployments instead of serving them.

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-1250** | Journey-start now uses the correct resource ID when the journey is referenced via an alias, eliminating a class of "resource not found" failures at start. |
| **GGO-13030** | `MODULE_EXECUTED` events now consistently carry the journey `subject`, restoring downstream correlation in the Investigation Portal and progress pipeline. |
| **GGO-14460** | Schema-fetch errors caused by an invalid filter name now return the `INVALID_FILTER` error code instead of a generic schema error, giving integrators a clear, actionable response. |
| **GGO-1763** | Variant-level `env` is now propagated to the execution-node configuration, including for superflow modules — fixing cases where a module ran with stale or missing environment values. |
| **GGO-1763 H4** | `process.step` is reliably rebuilt from the journey graph when missing on Flowable callbacks, eliminating intermittent "step not found" failures on resumed journeys. |
| **GGO-14535** | Interaction events are now forwarded to S3 alongside module events, closing the gap between interaction-level data in the Investigation Portal and the progress-events pipeline. |
| **#1136** | `RETAIN-<duration>` S3 object tag is now applied at progress-event write time using the org-specific retention duration, so per-org retention policies are enforced from the moment data lands. |
| **#1480 US2** | Iframe embedding allowlist closes prefix-overlap and write-path fail-open defaults, and tightens `Cache-Control` for embedding-relevant responses, so embedding restrictions cannot be bypassed by edge-case origin strings. |
| **#1606** | Flow-compiler version is now part of the module-deployment cache key, preventing stale module deployments from being served after a compiler upgrade. |
| **#1758 / #1759** | Dapr SDK identifiers are now confined to per-domain bridges, eliminating state-key collisions that could occur when modules and journeys shared a Dapr state store. |
| **#1763 I9** | Submit-context updates now honour the latest-wins ordering guarantee even when an intermediate view-extraction read returned stale data. |

**April 6th, 2026**

## April releases

The releases for April 6th, 2026 introduce new modules for document collection and continuous compliance screening, along with improved PEP and Sanctions configuration options.

### New features

* Added Document Attachments module for supporting document collection. This module enables you to request and securely collect supporting documents during onboarding workflows such as Proof of Address, Proof of Income, and Marriage Certificate.

* Added PEP and Sanctions Standard OGM Push variant, enabling automated push of individual records for continuous compliance screening with configurable worklist targeting and success/error outcome reporting.

### Improvements

Improved PEP and Sanctions module screening. The variants now offer extensive configuration options including:

* Dataset selection
* Customizable match thresholds (75-100)
* Sanction body filtering
* Automatic name transliteration to Latin alphabet
* DOB/country matching requirements
* PEP tier selection
* Configurable candidate limits

These options provide enterprise-grade compliance screening with detailed match profiles and sanction body mapping.

### Bug fixes

*No bug fixes were introduced in this release.*

**March 21st, 2026**

## March releases

The releases for March 21st, 2026 focus on journey editing reliability.

### New features

*No new standalone features were introduced in this release.*

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-13723** | Fixed issue where journeys without existing drafts could not be updated or modified, causing silent backend errors with no user-facing feedback. Automatic fallback was implemented to the last existing version to ensure you can always edit your journeys without encountering draft-related errors. |

**March 12th, 2026**

## March releases

The releases for March 12th, 2026 focus on Investigation Portal accuracy.

### New features

*No new standalone features were introduced in this release.*

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-12672** | Fixed critical issue where Evaluation modules incorrectly displayed "Error" status in the Investigation Portal summary view even when journey decisions were correct and successful. This fix ensures accurate evaluation outcome representation across all module types including Data Verification, Document Classification, and FaceMatch workflows. |

**March 10th, 2026**

## March releases

The releases for March 10th, 2026 focus on Subject Risk outcome accuracy.

### New features

*No new standalone features were introduced in this release.*

### Improvements

| Bug # | Description |
| - | - |
| **GGO-13396** | Fixed issue where Subject Risk code "single.address.in.file" was incorrectly triggering "No Match" outcomes even when the module returned successful results. |

### Bug fixes

*No bug fixes were introduced in this release.*

**March 2nd, 2026**

## March releases

The releases for March 2nd, 2026 focus on outcome classification accuracy for data verification workflows.

### New features

*No new standalone features were introduced in this release.*

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-12442** | Fixed issue where Data and Age Verification variants incorrectly generated Error outcomes in certain cases. There is now proper outcome classification for data verification workflows. |

**February 18th, 2026**

## February releases

The releases for February 18th, 2026 focus on Investigation Portal performance and stability.

### New features

*No new standalone features were introduced in this release.*

### Improvements

Improved PDF export performance in the Investigation Portal, reducing generation time and improving responsiveness when exporting journey session details and documentation.

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-12763** | Fixed issue where the Investigation Portal would become unresponsive when switching between Documents and Biometrics tabs, requiring manual page refresh to recover. The fix now ensures smooth tab transitions and maintains application responsiveness during navigation. |

**February 11th, 2026**

## February releases

The releases for February 11th, 2026 enable the Update Modules feature in the production environment.

### New features

* Enabled Update Modules feature in production environment. To learn more, refer to [How to update modules in GBG Go](/docs/go-v2/guides/product-guides/update-module.md).

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

*No bug fixes were introduced in this release.*

**February 6th, 2026**

## February releases

The releases for February 6th, 2026 add support for new UK identity verification datasets.

### New features

* Added support for UK Edited and Historical Electoral Roll dataset, providing comprehensive electoral register verification. This includes both current and historical voter registration data for improved UK identity verification workflows.

* Added support for UK National ID Register dataset, providing access to national identity registration data for improved UK identity verification workflows.

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

*No bug fixes were introduced in this release.*

**February 5th, 2026**

## February releases

The releases for February 5th, 2026 focus on Investigation Portal.

### New features

*No new standalone features were introduced in this release.*

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

| Bug # | Description |
| - | - |
| **GGO-12331** | Fixed an issue where the Investigation Portal only displayed the first five module results in journeys with more than five modules, causing incomplete journey information and incorrect decisions to be shown. All module results are now properly displayed regardless of journey complexity. |

**February 4th, 2026**

## February releases

The releases for February 4th, 2026 introduce bank account schema support for subject context.

### New features

Added bank account schema to the subject context, enabling bank account verification workflows with support for multiple account types. The schema supports the following account details:

* Account numbers
* Sort codes
* Routing numbers
* IBAN/BIC codes
* Account holder information for UK, US, and international banking systems

**Sample response (Single UK Bank Account):**

```json JSON theme={null}
{
  "context": {
    "subject": {
      "accounts": [
        {
          "type": "Bank Account",
          "accountNumber": "12345678",
          "sortCode": "12-34-56",
          "accountHolderName": "Jane Doe",
          "bankName": "Example Bank Ltd",
          "country": "GB",
          "accountType": "current"
        }
      ]
    }
  }
}
```

**Sample response (Multiple Accounts: UK + IBAN):**

```json JSON theme={null}
{
  "context": {
    "subject": {
      "accounts": [
        {
          "type": "Bank Account",
          "accountNumber": "12345678",
          "sortCode": "12-34-56",
          "accountHolderName": "Jane Doe",
          "bankName": "Example Bank Ltd",
          "country": "GB",
          "accountType": "current"
        },
        {
          "type": "Bank Account",
          "accountNumber": "89370400440532013000",
          "iban": "DE89370400440532013000",
          "bic": "COBADEFFXXX",
          "accountHolderName": "Jane Doe",
          "bankName": "Commerzbank",
          "country": "DE",
          "accountType": "savings"
        }
      ]
    }
  }
}
```

### Improvements

*No improvements were introduced in this release.*

### Bug fixes

*No bug fixes were introduced in this release.*

**February 3rd, 2026**

## February releases

The releases for February 3rd, 2026 add authentication capabilities to the Webhook module.

### New features

*No new standalone features were introduced in this release.*

### Improvements

Added authentication capabilities to the Webhook module settings window. This enables secure integration with protected external services through username/password or API key authentication. To learn more, refer to [How to use and configure a Webhook module in Go](/docs/go-v2/guides/product-guides/webhook-module-guide.md).

### Bug fixes

*No bug fixes were introduced in this release.*

**January 29th, 2026**

## January releases

The releases for January 29th, 2026 focus on improving outcome management in Journey Designer and journey execution stability.

### New features

*No new standalone features were introduced in this release.*

### Improvements

Improved the Outcome Map to display more meaningful default outcome names. The default outcome now automatically reflects the name defined in the module configuration instead of the generic "No warning signals" label. You can now edit default outcome names.

### Bug fixes

This section contains bug fixes for January 29th, 2026.

| Bug # | Description |
| - | - |
| **GGO-11210** | Fixed an issue where production journeys could only be executed using `@latest` version identifier instead of specific version numbers. Journey executions now work correctly with exact version references in production mode. |

**January 13th, 2026**

## January releases

The releases for January 13th, 2026 are focused on improving credit bureau integrations, data consistency, and Investigation Portal reliability.

### New features

*No new standalone features were introduced in this release.*

### Improvements

Updated the Single Source Credit Bureau variants with consistent output formats and expanded matching capabilities. Introduced new Credit Bureau 1, 2, and 3 variants with improved advice fields, improved match counting, and age threshold detection to support more accurate identity verification.

### Bug fixes

This section contains bug fixes for January 13th, 2026.

| Bug # | Description |
| - | - |
| **GGO-11813** | Fixed an issue where subject names could disappear from the Investigation Portal when evaluation events were processed. The system now preserves subject identity information throughout the journey lifecycle, ensuring names remain visible even when subsequent events do not include name data. |
| **GGO-11814** | Fixed an issue where evaluation decisions were not displayed in the Investigation Portal when multiple events for the same journey were processed simultaneously. Concurrent event handling has been improved to ensure evaluation results and decisions are consistently shown. |

**December 16th, 2025**

## December releases

Releases for December 16th, 2025 focused on improving version control, user support, dashboard navigation, and data accuracy.

### New features

This section contains new releases December 16th, 2025.

* You can now restore journeys to previous deployment versions directly from the Journey Dashboard. This feature provides improved version control and deployment safety, allowing you to quickly roll back to earlier journey configurations when needed. To learn more, refer to [Restore journeys to a previous version](/docs/go-v2/guides/product-guides/restore-journey-version.md).

* Integrated Intercom for in-app support chat, enabling you to access help resources and receive real-time assistance directly within the Go application.

* Added filtering and sorting capabilities to the Go dashboard for improved navigation and organization of journeys. To learn more, refer to [Create journeys](/docs/go-v2/platform/journey-builder/create-journey.md).

### Improvements

This section contains improvements for December 16th, 2025.

* Added configurable Originating Agency Code (OAC) settings for Australian FVS document verification (driver's license and passport) in Journey Designer.

### Bug fixes

This section contains bug fixes for December 16th, 2025.

| Bug # | Description |
| - | - |
| **GGO-10976** | Fixed an issue where dates were incorrectly displayed as the previous day for users in certain time zones. Go now properly distinguishes between date-only values and date-time timestamps, ensuring dates are displayed consistently regardless of your time zone. |
| **GGO-11266** | Fixed Investigation Portal displaying incorrect "Received" date, showing "21 Jan 1970", to now show actual data received timestamps. |

**December 2nd, 2025**

## December releases

Releases for December 2nd, 2025 focused on improving module reliability and data handling.

### Bug fixes

This section contains the recent bug fixes.

| Bug # | Description |
| - | - |
| **GGO-11332** | Fixed an issue where the Trust Module would not properly process phone numbers when the type was specified in lowercase, for example, "mobile" instead of "Mobile". The module now correctly handles phone number types regardless of case, ensuring reliable phone verification for all input formats. |

**November 4th, 13th, 24th, 2025**

## November releases

Releases for November 4th, 13th, and 24th, 2025, focused on improving journey execution capabilities, improving the Investigation portal, and refining module output displays.

### New features and improvements

This section contains the recent new releases and improvements.

* Improved journey execution to enable modules to access and use subject information updated by other modules within the same journey. This capability allows for more sophisticated identity verification workflows where modules can build upon data gathered and enriched by previous steps.

* Added new PEP and Sanctions functionalities to the Investigation Portal. Functionalities include:
  * **Results Summary tab** for quick identification of PEP matches and sanctions database matches with clear, organized result summaries.
  * **PEPs tab** for detailed PEP match information, including confidence scores, identity details, and relevant metadata to support compliance decisions.
  * **Sanctions tab** for evaluating matches against sanctions lists, with results organized by source authority or dataset for clear compliance context.
  * **PDF export capability** to generate comprehensive reports of all PEP and Sanctions screening results for audit and regulatory compliance documentation.

* Improved the "Raw" tab in the Investigation Portal to display a clean, API-response-structured JSON object. The tab now shows relevant module output data (status, advice, notes, subject, documents) in a consistent format, making it easier to understand module results and troubleshoot issues.

For more information about updates to module tabs in the Investigation portal, refer to the [View details of a journey session](/docs/go-v2/platform/investigate/view-journey-details.md) documentation.

### Bug fixes

This section contains the recent bug fixes.

| Bug # | Description |
| - | - |
| **GGO-11210** | Fixed issue where production journeys could only be executed using `@latest` version identifier instead of specific version numbers. Journey executions now work correctly with specific versions in production. |
| **GGO-10526** | Fixed overlapping text issue in journey session PDF exports where audit log and module detail titles would overlap with other content elements when the PDF contained multiple modules with images. |
| **GGO-10248** | Fixed an issue where dates in the User Data section of journey session PDF exports were not rendered correctly. Date fields are now displayed properly in exported PDFs. |

### API changes

This section contains the recent API changes.

| Change # | Description |
| - | - |
| **GGO-10542** | Added `note` property to API response schema for PEP and Sanctions screening results, so that you can view or store notes alongside results. |

**September 30th, 2025**

## September releases

Releases for September 2025 are all about improving user experience for complex journeys and giving you more control over your platforms’ configuration. We rolled out several key improvements and one important bug fix designed to make the system more powerful and flexible for your needs.

### New features and improvements

This section contains new releases and improvements for September
2025\.

* Session detail PDF exports now include a complete audit log showing the history of actions taken on the record. This enables offline compliance reviews and audits with full traceability.

* Increased the journey completion timeout from 30 minutes to 7 days, allowing customers more time to gather and submit required information during multi-step verification processes. This is particularly helpful for journeys requiring document collection or manual review steps.

* Enabled settings configuration for document and biometric verification modules in production environments. You can now customise module behavior according to specific business rules and requirements. To learn more, refer to the [How to configure module settings in Go](/docs/go-v2/guides/product-guides/configure-module-settings.md) documentation.

* Enabled settings configuration for the **Webhook** module in preview and production environments. You can now customise the webhook module to accept your preview and production webhook URLs. For more details, refer to the [How to use and configure a Webhook module in Go](/docs/go-v2/guides/product-guides/webhook-module-guide.md) documentation.

## Bug fixes

This section contains bug fixes for September 2025.

| Bug # | Description |
| - | - |
| **GGO-9857** | Fixed an issue where the Liveness module would only show the "ERROR" option instead of the complete liveness scale when no custom outcomes were configured. The full scale is now displayed correctly in all scenarios. |

**August 28th, 2025**

## August releases

Releases for August 2025 introduced new features into the Go Investigation portal.

### New features

* Added the ability to export customer sessions to PDF. This is great for record-keeping, compliance reporting, or sharing with stakeholders outside the GBG Go platform. For more details, see the [Export journey session](/docs/go-v2/platform/investigate/export-journey-session.md) documentation.

* Added webhook support for customer journeys. You can now configure webhooks using the **Webhook** module to send real-time notifications about task status changes in your customer journeys to external apps. This enables better integration with your existing systems and workflows.

**July 31st, 2025**

## July releases

Releases for July 2025 focus on improving platform stability and reliability in GBG Go, particularly around API functionality and journey execution workflows.

### New features and improvements

The investigation portal now includes zoom controls for detailed image inspection. Use these controls to examine evidence images more closely during investigation.

You can view and zoom images in two locations within the Investigation tab:

* **Processing tab**: Navigate to this tab and expand the documents and biometrics module. **Click More Details** > **Extracted Images** to view and zoom the image.

* **Documents & Biometrics tab**: You can immediately view and zoom images when you navigate to this tab.

When viewing an image in the investigation portal, you'll see four zoom control buttons:

* **Zoom In (+)**: Click to magnify the image for closer inspection.

* **Zoom Out (-)**: Click to reduce the magnified image.

* **Center**: Click to center the image in the viewing area.

* **Reset (X)**: Click to return the image to its original size and position.

### Improvements

* No improvements added this month.

### Bug fixes

| **Bug #** | **Description** |
| - | - |
| **GGO-9124** | Fixed issue where the task schema API endpoints were failing to retrieve schema information for valid task IDs. The `/journey/task/schema` and `/journey/task/list/schema`. APIs now properly return task schema data as expected. |
| **GGO-9211** | Fixed issue where certain journeys would remain stuck *In Progress* indefinitely and fail to appear in the Investigation portal. Journey executions now properly complete and become visible for investigation as expected. |

**May 26th, 2025**

## May releases

Releases for May 2025 focus on improving the user experience in GBG Go, particularly in the Journey builder.

### Improvements

* Shortened the connection lines between modules in the journey designer canvas for a cleaner, more compact visual experience. The updated spacing makes it easier to view and work with complex journeys without excessive scrolling.
* Added support for optional asynchronous journey execution in pre-fill mode to prevent timeout issues with long-running processes. Developers can now receive immediate response with instance IDs and monitor progress separately.

**April 8th, 2025**

## April releases

Releases for April 2025 focus on improving the user experience for licensed and unlicensed modules in GBG Go. The changes include clearer visual indicators, improved variant lists, and helpful guidance messages when selecting unlicensed variants.

### Improvements

* Updated visual indicators for unlicensed modules with clearer icons and colors.
* Improved variant lists by removing unnecessary licensing indicators.
* Added a helpful guidance message when selecting unlicensed variants.

### Bug fixes

| **Bug #** | **Description** |
| :- | :- |
| **GGO-7903** | Fixed loading error on Settings page. |
| **GGO-7576** | Fixed the logout session error |
| **GGO-7930** | Fixed Settings page issue where changing data retention policies caused blank screen. |
| **GGO-7937** | Removed Audit log nonfunctional link in Settings page. |
| **GGO-7453** | Fixed journey template filtering issue. You can now properly combine filters to find the templates you need. |
| **GGO-7906** | GBG Assistance turned on for all organizations. All new organizations now have GBG Assistance enabled by default. This ensures that you receive immediate support from the GBG team when you first get started, without needing to manually enable this feature. You can turn this feature off in your GBG Go Settings page, located on your dashboard. |