Skip to main content

Series 4 Release Notes

Open Gateway v4.0.0​

Series 4 makes consent faster and clearer for consumers, lets you change your branding without a release, and tightens security.

We handle the upgrade of your environment, and your branding carries over automatically. Series 4 incorporates the recent Series 3 fixes (see the Series 3 release notes).

The four-step consent wizard has been replaced with a single screen. Consumers can now manage their provider selection, data-sharing visibility, and duration preferences on one page for a faster confirmation experience.

  • [feature] A searchable dropdown replaces the list of cards making provider selection easier. Providers are grouped by brand so a bank's sub-brands sit together, and the list is fully keyboard-navigable.
  • [feature] The data being shared is organised into collapsible groups, so consumers can scan it at a glance.
  • [feature] Consumers clearly see how long their data will be accessed and the exact date access ends.
  • [feature] When a consumer edits an existing arrangement, the page highlights the new end date, making amendments clear.
  • [fix] The confirm button stays disabled until the page has fully loaded, so an early click can no longer land a consumer on an error page. All dates now display in the consumer's own timezone.
info

If your support materials or screenshots show the old four-step wizard, they'll require updating.

Branding without a release​

Your colours, shades, font, logo, favicon, contact address, and CDR logo are now configurable settings on your environment. Updating your look no longer requires a software release, and your existing branding carries across when we upgrade you.

Fixes​

  • [fix] Cancelled consents now return your state: Cancelled consents redirected to your errorRedirectUri now include the original state value if you have supplied one. This allows you to match the cancellation directly to the initiating session. The redirect payload includes error=cancelled, errorDescription and state (plus errorUri if returned by the holder). If your redirect handler validates incoming parameters, please ensure it accepts state.
  • [fix] Data holder omitting scope no longer causes failures: The standard allows a data holder to omit scope from a token response when it matches the request. This previously caused connection failures; we now treat the requested scopes as granted.

Security​

  • [fix] Sensitive tokens masked in logs: Data holder access, refresh and ID tokens, and authorisation codes, are no longer written in to logs in readable form.
  • [fix] Streamlined consent error messages: To prevent information leakage, consumer-facing errors for failed consent savings have been replaced with a generic "Please try again" prompt. Complete diagnostic data is still captured safely in our server logs.

tip

Please see here for the OG release history.