This documentation is for WSO2 Open Banking version 1.3.0. View documentation for the latest release.

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Released DateUpdate Description


Displays the error response for access token failures in the UK error format.

See Displaying the error response for access token failures in the UK error format to add the required configurations for this WUM update.


This WUM update introduces the certificate revocation validation feature.

In order to apply this update:

  • Update the axis2.xml file
  • Update the open-banking.xml file

See the instructions given under the Certificate revocation validation section for the BERLIN specification.

An update to UK specification is sent to make the transport header configurable. Click here to find instructions.

According to the OBIE, the Account Servicing Payment Service Providers (ASPSPs) need to make sure that the TPPs can be registered in a seamless, ideally a fully automated process. The Dynamic Client Registration(DCR) endpoint is capable of dynamically registering the clients with the ASPSP when the client sends a registration request with its metadata. Click here to see how to deploy the DCR v3.2 API.

An improvement for Berlin specification compliant solution in WSO2 Open Banking. Verifies if an account-id sent within the account-consents resource that is sent by TPP, is valid from the bank back-end. For the required configurations, see here.

Request Payload Validation adds flexibility to validate an incoming request against any customisations done to the swagger definition. To use the feature, see Request Payload Validation for UK.


Validates PSD2 roles in the eiDAS QWAC (Transport Layer Certificate) during Berlin API Calls and restrict TPP accessing APIs if the required roles are not available in the certificate.


Allows the use of the DCR software_id as the application name. Therefore, removes the native naming limitation set in place by WSO2 products. Add the following changes for this update;


Improved the solution by validating the TPP when retrieving a payment submission. This validation confirms whether it is the same TPP that submitted the consent, is viewing the payment submission.


Separates the redirect URI validation and the hostname validation for all the URIs in the request and changes the consumer_key and the consumer_secret in the response as client_id and client_secret with compliance to the Open Banking Implementation Entity (OBIE) specification. Click here for more information.


Restricts RS256 signed messages from TPP. OBIE (Open Banking Implementation Entity) allowed both RS256 in addition to PS256 as the signature for signing JSON Web Signature (JWS). When market adopts RS256 sufficiently, RS256 has to be deprecated from signing JWS. As WSO2 Open Banking is an OBIE compliant solutions, this WUM update was released to deprecate the use of RS256. It includes the following changes: