Skip to main content

Release History

Series 2 Release Notesโ€‹

Open Gateway v2.1.0โ€‹

Updatesโ€‹

  • [feature] Open Gateway supports the instalment plan endpoints required for the 9 November 2026 FDO (Banking sector):

    • Get Instalment Plans for Account V1.
    • Get Instalment Plans Bulk V1.

    Both endpoints accept the optional plan-status query parameter (ACTIVE, INACTIVE or ALL). If omitted, ACTIVE is assumed. Plans are returned in descending creationDate order. Both endpoints use the existing biza-au:og:cds-au:bank:regular_payments:read scope, so no new scope needs to be provisioned for your software product.

  • [feature] Open Gateway supports the transaction endpoint changes required for the 9 November 2026 FDO (Banking sector):

    • Get Transactions for Account V2.
    • Get Transaction Detail V3.

    These versions introduce instalmentPlanId, which links a transaction to the instalment plan it belongs to. To receive instalmentPlanId, request x-v: 2 on Get Transactions for Account or x-v: 3 on Get Transaction Detail. Earlier versions are unaffected and continue to be served as before.

  • [general] New OG API release v2.1.0. See the Open Gateway API reference for the full specification.

note

Data Holders taking up this release must ensure their data adapter implements the corresponding adapter operations. See the Open Gateway Future Dated Obligations page for the obligations this release satisfies.

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


Open Gateway v2.0.1โ€‹

Updatesโ€‹

  • [feature] Introduce EnumParticipantCapabilityV2 with CDS_AU_DATA_SHARING_NON_BANK_LENDING and CDS_AU_PRD_NON_BANK_LENDING, enabling full support for Non-Bank Lending data holders joining the CDR Register. Non-Bank Lending exposes the same two-capability model as Banking (CDS_AU_DATA_SHARING_* + CDS_AU_PRD_*). EnumParticipantCapabilityV1 is frozen at its original 5 values for backward compatibility.
  • [feature] All agreement, participant, and template endpoints now support x-v: 2 responses returning full v2 capability sets including NBL. x-v: 1 responses continue to filter NBL capabilities to remain schema-valid for existing integrations.
  • [feature] Register polling now handles CDR Register API v3 responses, enabling discovery and capability mapping of Non-Bank Lending data holders.
  • [vtt] Arrangement detail page now requests API x-v: 2 so NBL capabilities are visible. Previously x-v: 1 was used, which filtered NBL tokens for schema compatibility with the v1 enum.
  • [vtt] Test suite routes both NBL capabilities to the banking test cases, since Non-Bank Lending data holders implement the same CDR banking endpoints at the wire level.
  • [feature] Product Reference Data requests (/banking/products, /banking/products/{productId}) now route using the productBaseUri field from Get Data Holder brands when present, falling back to publicBaseUri otherwise. Existing banking and energy holders are unaffected.
  • [feature] The consent flow now groups participating brands by brandGroup in line with DSB CX guidance, so brands sharing a group are displayed together. Brands without a brandGroup continue to render individually as before.

Open Gateway v2.0.0โ€‹

Updatesโ€‹

  • [feature] OG API upgraded to v2.0.0. All bulk banking endpoints (balance list, direct debits, scheduled payments) now return CDR Banking V2/V3 responses, with the response version determined by the x-v request header.
  • [feature] Data Holder Brands endpoint now consumes CDR Register V3, which resolves brands using brandGroup and productBaseUri fields.
  • [feature] productCategory enum upgraded to V2, adding BUY_NOW_PAY_LATER across all banking product and account APIs.
  • [feature] templateId field added to the Agreement schema.
  • [fix BZ-11271] Agreement revocation in OG Admin was blocked when a prior amendment attempt left a stale PRIMED agreement log entry. The revoke button is now correctly enabled when an active agreement exists for the same CDR arrangement ID.
  • [fix] Register data holder brand polling is now processed in isolated transactions per brand. Previously, a failure on one brand (e.g. database error) could roll back all successfully-processed brands in the same polling job.
  • [fix] Malformed CDR sharing prime requests now correctly return 400 Bad Request instead of 500 Internal Server Error.
  • [fix] Agreement end jobs are now marked as FAILED when no webhook URL is configured, rather than completing without an error.
  • [fix] Fixed a null pointer exception when a data holder brand carries an unsupported industry value during register V2 parsing.
  • [fix] Resolved a crash loop in ThemeInitialiser triggered by a duplicate softwareProductId.
  • [general] Terminology standardised from "arrangement" to "agreement" throughout OG Admin.

Open Gateway v1.0.69โ€‹

Updatesโ€‹

  • [fix] Resolved an issue where unconstrained x-v header values were being forwarded to data holders during CDR version negotiation, causing request failures for certain data holders. Requests with unsupported x-v values are now rejected with an error indicating the version is not supported.

Open Gateway v1.0.68โ€‹

Updatesโ€‹

  • [feature] Open Gateway support product endpoints changes for the March 2026 FDO (DP338):
    • Get Products V4.
    • Get Product Detail V6.
    • Get Account Details V4
  • [feature] Open Gateway support product endpoints changes for the July 2026 FDO (DP367):
    • Get Products V5.
    • Get Product Detail V7.
  • [feature] Open Gateway support product endpoints changes for the November 2026 FDO (DP367):
    • Get Accounts V3.
    • Get Account Detail V5.

Open Gateway v1.0.67โ€‹

Updatesโ€‹

  • [BZ-10665] Patches to mitigate CVE-2025-55182.

Open Gateway v1.0.66โ€‹

Updatesโ€‹

  • [PRODUCT-1680] Bug fixed in calculation of active consumer count.

  • [PRODUCT-1524] Removal of errant closing parenthesis in consent flow.


Open Gateway v1.0.65โ€‹

Updatesโ€‹

  • [fix PRODUCT-1319] Unable to view agreement detail in the Open Gateway Administration portal.

  • [feature] An administrator is now able to trigger a revoke of an agreement on the agreement detail page in the Administration Portal.

  • [fix PRODUCT-1511] Open Gateway would not include the cdr arrangement id when performing amends. This caused new agreements to be created with holders as opposed to amending the existing arrangement.


Open Gateway v1.0.64โ€‹

Updatesโ€‹

  • [feature PRODUCT-176] FDO Y25#5 Added support for LCCD in Get Service Points v2 and Get Service Point Detail v2.

Open Gateway v1.0.63โ€‹

Updatesโ€‹

  • [feature PRODUCT-1039] Adding a new api endpoint โ€˜getAgreementHistoryโ€™ This enables a caller to retrieve versioned instances of the agreement if amendments have taken place. Also includes improvements to the api response where the agreementId would be inconsistent between calls after an amendment has occurred.

  • [fix] Brand logos were not correctly constrained in the consent flow header. This could result in a distorted logo being shown. No consent flow functionality was impacted, purely cosmetic.

  • [general] New OG api patch release v1.33.3.

Platform Updatesโ€‹

  • [Certificates] Update the Open Gateway trust store to include the new ACCC Certificate Authority (CA) that is scheduled to be in use from 1st of October 2025. standards issue 695

Open Gateway v1.0.62โ€‹

Updatesโ€‹

  • [feature PRODUCT-934] When agreements were amended, the duration was not correctly calculated from the time of the amendment but from the original agreement creation date.

  • [general] This release contains updates to libraries as part of our regular software maintenance schedule.

  • [general] New OG api patch release v1.33.2


Open Gateway v1.0.61โ€‹

Updatesโ€‹

  • [feature PRODUCT-974] When a consumer's name is not available from the identity provider, dashboard will attempt to find a substitute by parsing the email address. This fixes consumers not being able to amend their agreements due to a missing name value in the api call.

Open Gateway v1.0.60โ€‹

Updatesโ€‹

  • [feature PRODUCT-360] Database password rotations are now automated when the appliance is deployed on AWS, reducing Open Gateway downtime.

  • [feature PRODUCT-818] List Participant endpoint returns CDR legal entity ID additionally in response payload.

  • [feature - PRODUCT-822] CDR Sharing Agreement - Prime Endpoint - takes optional Participant ID list to filter out Data Holders during consent flow.

Open Gateway v1.0.59โ€‹

Updatesโ€‹

  • [feature PRODUCT-118] Changes to indicate which datasets, uses, and durations are being amended.

Open Gateway v1.0.58โ€‹

Updatesโ€‹

  • [fix PRODUCT-635] Fixes a regression introduced by PRODUCT-583 - Get Transaction Detail api call fail with an incorrect url.

Open Gateway v1.0.57โ€‹

Updatesโ€‹

  • [fix PRODUCT-583] Certain path parameters were not correctly url encoded when the request is relayed to the data holder.

Open Gateway v1.0.56โ€‹

Updatesโ€‹

  • [fix ADR-1626] Open Gateway Admin - Searching for Agreements by cdr arrangement id silently failed do to a bug in the Open Gateway Api Client. This is now resolved.

  • [feature PRODUCT-42] Implement support for new Y25 #3 FDO API changes

    • Banking - Get Product Detail v5

    • Banking - Get Transaction Detail V2

  • [fix PRODUCT-259] Open Gateway will now allow the following uri encoded strings to be parameter values

    • %2f the โ€œ/โ€ character

    • %25 the โ€œ%โ€ character

  • [general] Security Updates for Spring Cloud, Spring Boot.


Open Gateway v1.0.55โ€‹

Updatesโ€‹

  • [fix] Improved SIEM log formatting. There were json formatting differences between some outputs making SIEM log consumption difficult. All SIEM log json from all Open Gateway components is now aligned.
  • [feature admin] New reporting page that allows an administrator to query the number of active consumers during a date range inclusive.
  • [fix ADR-1583] Consent flow will only use the โ€œConsumer Data Rightโ€ logo in the ACCC ecosystem. This was incorrectly shown in Biza Test Ecosystem.

Open Gateway v1.0.54โ€‹

Updatesโ€‹

  • [fix ADR-1560] Open Gateway second patch related to support of extraConfig field in Holder discovery document.
  • [patching] General library updates and patching for Open Gateway.
  • [general] Renamed references to online help to โ€œBiza Guidesโ€ in the Open Gateway Admin application.

Open Gateway v1.0.53โ€‹

Updatesโ€‹

  • [fix ADR-777] SIEM logging format is improved to allow easier readability when parsed in log analysis tools such as Datadog.
  • [fix ADR-1078] fixed an error where when processing the holder discovery document, the extraConfig field could be incorrectly parsed.

Open Gateway v1.0.52โ€‹

Updatesโ€‹

  • [patching ADR-1417] Patches including fixes for https://nvd.nist.gov/vuln/detail/CVE-2025-29927.
  • [fix ADR-1519] Open Gateway incorrectly sent a reminder notification to a consumer when they created a new agreement and havenโ€™t accessed the consumer dashboard for greater than 90 days.

Open Gateway v1.0.51โ€‹

Updatesโ€‹

  • [fix ADR-1498] Open Gateway was unable to process holder updates when the change included a move to a new legal entity. These holder updates are now reflected in Open Gateway.
  • [stability] Open Gateway is now more resilient to parsing errors when consuming Holderโ€™s well-known configuration documents. Errors will no longer be generated when advertised values are not recognised.

Open Gateway v1.0.50โ€‹

Updatesโ€‹

  • [fix ADR-1486] Open Gateway selected the wrong token_endpoint when parsing the Holders well-known configuration endpoint. Open Gateway will now correctly substitute from the mtls_endpoint_aliases when an override is present.
  • [feature] Open Gateway now captures more historical information about access tokens that are claimed from a holder when a sharing arrangement is established and data requested.

Open Gateway v1.0.49โ€‹

Updatesโ€‹

  • [fix] General BTS bug fixes

Open Gateway v1.0.48โ€‹

Updatesโ€‹

  • [feature] OG - added support for banking - getProducts and getProductDetail endpoints
  • [feature] When a consumer attempts to start a consent flow via an expired link, an error page will be shown outlining this case
  • [feature] When a consumer is unable to submit consent, the error reason is now clearly shown at the bottom of the page. Previously a generic โ€œan error has occurredโ€ was shown.

Open Gateway v1.0.47โ€‹

Updatesโ€‹

  • [consent] UI Fixes when viewing consent flow on mobile. Corrects layout issues when viewed on iPhone SE viewports.
  • [general] Security Updates for Spring Cloud, Spring Boot, NextJS libraries.

Open Gateway v1.0.46โ€‹

Updatesโ€‹

  • [VTT ADR-1172] Banking > GetTransactions now shows both the posting date and value date of the returned transactions. Interactivity of the page has been improved by loading data asynchronously.
  • [VTT ADR-1218] On the List Arrangements - the active transactions filter did not correctly show inactive states. Internal Open Gateway states of INIT and PRIMED are removed from results with only EXPIRED and REVOKED shown along with ACTIVE.

Open Gateway v1.0.45โ€‹

Updatesโ€‹

  • [OG ADR-1209] Open Gateway used an incorrect signing algorithm when signing a request to refresh an access token from a Data Holder. This occurred only when certain permutations of different algorithms were chosen during registration with that same Data Holder.
  • [vTT ADR-1249] VTT did not properly encode holder ids when consumed from a Holder Api. This would result in Open Gateway rejecting these requests with a http 400 response status. These are now properly encoded and queries are now made to Holder endpoints.
  • [OG ADR-1213] Race condition causing agreement revoke to fail. Depending on timing of the jobs managing agreement status and its associated consents, there could be scenarios where the agreement status is not transitioned to its final state.
  • [OG ADR-1217] Open Gateway would send an invalid RFC3339 formatted DateTime when the passed DateTime contained zero seconds and part seconds. This only effects Data Holder API calls the used filtering parameters of type DateTime.

Open Gateway v1.0.44โ€‹

Updatesโ€‹

  • [VTT ADR-1187] fix - can now view service point usage for service points that contain โ€œ=โ€ in the id string.
  • [OG] Security patching - Updates to core libraries.

Open Gateway v1.0.43โ€‹

Updatesโ€‹

  • [VTT ADR-1208] Application would fail to call โ€œGet Account Scheduled Paymentsโ€ due to an incorrect mapping of page parameters to the underlying OG Api call.

Open Gateway v1.0.42โ€‹

Updatesโ€‹

  • [VTT ADR-1187] The selection of service point ids for the โ€œGet Service Point Detailโ€ screen were sometimes duplicated. This is now resolved.
  • [OG Admin] Improved ability to manage registration with holders. We can now support deactivating a registration when the holder deletes the registration unilaterally on in their system.

Open Gateway v1.0.41โ€‹

Updatesโ€‹

  • [VTT] Security patching.

Open Gateway v1.0.40โ€‹

Updatesโ€‹

  • [VTT ADR-118] VTT will now display service point ids from closed as well as open accounts.

Open Gateway v1.0.39โ€‹

Updatesโ€‹

  • [VTT ADR-1152] Clearly indicate that โ€˜Get Bulk Transactionsโ€™ is part of DataRight+ not CDS when allowing API selection in Banking > Get Accounts screen.
  • [VTT] Adding support for some DataRight+ plus apis. Where these are available in the user interface they will be clearly marked as separate from CDS apis calls.

Open Gateway v1.0.38โ€‹

Updatesโ€‹

  • [OG ADR-1045] fix - Open Gateway now correctly signs client_assertion tokens with the registered token signing algorithm during PAR requests. Previously this was incorrectly signed with the registered request signing algorithm.
  • [OG general] improved SIEM logs from Open Gateway appliance - now includes failed requests.

Open Gateway v1.0.37โ€‹

Updatesโ€‹

  • [OG ADR-1045] fix - incorrect client credentials grant when connecting to providers that advertise both TLS and mTLS token endpoints.
  • [OG ADR-1146] Incorrect signing algorithm chosen during holder registration requests. We now prioritise the existing registration signature during update calls. Occurs when the signing algorithms are changed between calls.

Open Gateway v1.0.36โ€‹

Updatesโ€‹

  • [VTT ADR-1119] VTT will no longer have default values for filters parameters that involve dates. These fields will also be able to be cleared to enable โ€œno dateโ€ to be sent.
  • [OG ADR-1045] Open Gateway now has increased support for RFC8705, specifically support for โ€œmtls_endpoint_aliasesโ€. When a holder advertises this feature Open Gateway will use those aliases as described in the RFC.
  • [OG ADR-1134] Open Gateway now supports enum value โ€œINACTIVEโ€ for the entity โ€œRegisterDataHolderBrandโ€ structure returned from the register api โ€œGet Data Holder Brandsโ€

Open Gateway v1.0.35โ€‹

Updatesโ€‹

  • [dashboard ADR-1121] When revoking an agreement on the consumer dashboard the response processing failed. This results in the agreement only being revoked on the holder side.

Open Gateway v1.0.34โ€‹

Updatesโ€‹

  • [vtt ADR-1103] feature - Upon agreement completion the success screen in VTT now contains a button to navigate to the specific agreement just created
  • [vtt ADR-1116] Get Billing For Account request โ€œoldestTimeโ€ parameter was ignored when changed in the user interface.

Open Gateway v1.0.33โ€‹

Updatesโ€‹

  • [vtt] fix validation messages
  • [vtt] fix Energy Get Billing api calls
  • [vtt] fix Banking Get Balance, Get Direct Debits call and filters
  • [vtt] fix to bread crumbs on various pages, incorrectly linked to an empty result

Open Gateway v1.0.32โ€‹

Updatesโ€‹

  • [vtt] list arrangements - create and expiry dates now use browser timezone
  • [vtt] 401 error handling improvements, access tokens revoked when scenario detected
  • [vtt] Can view revoked arrangements in vtt using filter option
  • [consent] All existing VTT arrangements will now display the correct VTT logo
  • [OG] Http Client improvements - Swapped Ktor with RestTemplate

Open Gateway v1.0.31โ€‹

Updatesโ€‹

  • [consent] New agreements will use the Software Product logo vs the Brand logo
  • [vtt] Changes to severity of payload validation rules
  • [og] Improved access token handling during parallel calls, there will be a reduction in 401 errors from the api
  • [vtt] Improved error display - contains for detail from the underlying calls. Includes a โ€˜copy informationโ€™ feature.
  • [vtt] Fixes on search pages where incorrect filters were applied yielding empty results.

Open Gateway v1.0.30โ€‹

Updatesโ€‹

  • [VTT] Bug fixes

Open Gateway v1.0.29โ€‹

Updatesโ€‹

  • [OG] Support for Bulk transactions
  • [OG] Support for energy endpoints upgrade
  • [VTT] Bug fixes and improvements

Open Gateway v1.0.28โ€‹

Updatesโ€‹

  • [OG] Patch end-of-life callback urls of software products

Open Gateway v1.0.27โ€‹

Updatesโ€‹

  • [OG] Fix incorrect grant_type requested during client registration
  • [VTT] Include 12 month duration for agreements in Lab and CDR prod

Open Gateway v1.0.26โ€‹

Updatesโ€‹

  • [OG] Updates to PAR request compatibility

Open Gateway v1.0.25โ€‹

Updatesโ€‹

  • [OG] Send correct email notifications when amending arrangements

Open Gateway v1.0.24โ€‹

Updatesโ€‹

  • [Feature] customizing favicon of consent flow and dashboard apps
  • [OG] Fix consent expiry job related issues

Open Gateway v1.0.23โ€‹

Updatesโ€‹

  • [OG] AgreementTemplate Api - fix not saving callback urls

Open Gateway v1.0.22โ€‹

Updatesโ€‹

  • [Appliance Admin] Support โ€œfrom nameโ€ sendgrid configuration
  • [Appliance Admin] Security fixes - nextauth secret
  • [consent] Consent layout and theming changes
  • [og] Template support filtering of providers during consent flow
  • [og] support โ€œfrom nameโ€ when sending email via sendgrid
  • [consent] Using software product name vs brand name

Open Gateway v1.0.21โ€‹

Updatesโ€‹

  • [Appliance Admin] og directory id to be selected from a dropdown
  • [VTT] Correctly render validation errors when rendering table results
  • [OG] Improved support for AWS Cognito for Consumer Authentication
  • [OG] improvements to the sendgrid notification payloads
  • [OG] DCR improvements
  • [OG] Dashboard and Consent flow - Data Language Standards fixes
  • [VTT] Will correctly render the error message from OG/Data Holder when an invalid request is made

Open Gateway v1.0.20โ€‹

Updatesโ€‹

  • [appliance admin] Fix - switching open gateway to connect to another directory (CTS/ACCC) failed

Open Gateway v1.0.19โ€‹

Updatesโ€‹

  • [improvement] Remove deprecated sendgrid template configuration options for โ€œUseโ€ consents
  • [feature] Consent 'end of life' callback to software products

Open Gateway v1.0.18โ€‹

Updatesโ€‹

  • [improvement] VTT consent flow allows "at least one" data scopes to be shared
  • [improvement] Updates to DCR process

Open Gateway v1.0.17โ€‹

Updatesโ€‹

  • [Improvement] Minor improvements in VTT

Open Gateway v1.0.16โ€‹

Updatesโ€‹

  • [feature] OG admin supports enable/disable of automatic DCRs
  • [feature] OG admin supports registration maintenance features
  • [improvement] Improved response payload rendering in VTT
  • [improvement] Updates to OG theming

Open Gateway v1.0.15โ€‹

Updatesโ€‹

  • [feature] Support for OG standalone installation without software products
  • [feature] Support for theming in - [feature] DCR coverage improvements

Open Gateway v1.0.14โ€‹

Updatesโ€‹

  • [feature] Support success and error redirect urls while priming arrangements

Open Gateway v1.0.13โ€‹

Updatesโ€‹

  • [fix] Remove header policy that broke the cancellation of consent
  • [fix] Data holder registration error handling improvements