Skip to main content

Series 3 Release Notes

Open Gateway v3.0.3​

Updates​

  • [fix] Fixed two issues that prevented configured branding from being applied: the consent flow could display the default theme instead of the configured theme (custom theme colours are now applied correctly), and the Consumer Dashboard fell back to default branding for most theme profiles even when a logo was configured (configured logos are now correctly displayed).
  • [fix] Resolved a bug that caused Data Holder calls to time out at 10 seconds instead of the default 30 seconds, reducing intermittent OG failures.

Open Gateway v3.0.2​

Updates​

  • [fix] Resolved an issue where Open Gateway could not poll the CDR Register for data holder and brand information. Note that this release supersedes v3.0.1, which was an internal build that was not deployed to production.

Open Gateway v3.0.0​

Cloud-Native Deployment​

Series 3 moves Open Gateway to a fully cloud-native architecture deployed on Kubernetes. This is a foundational change that delivers higher availability, faster recovery, and a more consistent deployment model across environments. Key operational improvements include:

  • All services now communicate over mutual TLS with automatic certificate issuance and rotation. No manual certificate management is required.
  • Configuration and secret changes are applied at runtime without service restarts.
  • Service-to-service authentication uses a dedicated in-cluster identity provider, eliminating externally managed M2M credentials.

These changes are infrastructure-level and are transparent to existing API integrations.

Updates​

  • [feature] The Open Gateway Administration portal now includes a Jobs section, allowing administrators to manually trigger background jobs and review execution history.
  • [feature] A forced-login / SSO toggle (enabledForcedLogin) has been added to the consent dashboard configuration.
  • [fix] Resolved a bug where the consent flow was defaulting to Biza.io branding instead of your organisation's configured logo.
  • [fix] Open Gateway now handles data-holder token responses that omit the token_type field, preventing consent failures with non-compliant holders.
  • [fix] Requests to holder Product Reference Data endpoints now use a public CA trust chain, resolving PKIX validation failures against certain holder PRD base URIs.
  • [general] OG API updated to v2.1.0. See the Open Gateway API reference for the full specification.
  • [general] Security patches applied to resolve critical and high severity CVEs across backend (Java) and frontend (npm) dependencies.

Instalment Plans​

The following instalment plan capabilities, introduced in Series 2.1, are included in Series 3:

  • Get Instalment Plans for Account V1.
  • Get Bulk Instalment Plans V1.
  • Transaction endpoints updated to carry instalmentPlanId (Get Transactions for Account V2, Get Transaction Detail V3).

See the Series 2 release notes for full details on these endpoints.

VTT

Verification Testing Tool changes for this release are published separately in the VTS release notes.


tip

Please see here for the OG release history.