This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.
About this Release
WSO2 Open Banking provides the technology requirements that banks need in order to become regulatory-compliant (Payment Service Directive 2 (PSD2), Consumer Data Standards (CDS)) and digitally transformed. It combines the technical capabilities of WSO2 API Manager, WSO2 Identity Server, WSO2 Stream Processor, and WSO2 Enterprise Integrator with PSD2 and CDS specific feature customisations to quickly satisfy open banking requirements.
For more information on WSO2 Open Banking, see the overview and architecture pages in our documentation and the product page.
What is new in this release
The WSO2 Open Banking version 1.5.0 is the successor of version 1.4.0. It contains the following new features and enhancements:
Updates to the AU solution
The solution is now compliant with CDS API v1.2.0. It supports the following features:
- Dynamic Client Registration v0.1
- Consent flow for CDS API v1.2.0
- API flow for CDS v1.2.0
- Refresh token time validity time with sharing duration
- Metadata cache management
- Metrics API v1.2.0
- Consent management apps for banks (Customer Care Portal) and customers (Self Care Portal)
- Endpoint versioning
Updates to the UK solution
The solution is compliant with the following conformance test suites:
Test Suite | Version |
---|---|
OpenID conformance suite | v4.1.10 |
Functional conformance suite | v1.6.7 |
Dynamic Client Registration conformance suite | v1.0.3 |
Support for following UK-specific APIs:
Updates to the Berlin solution
The solution is now compliant with NEXTGEN PSD2 API v1.3.4. It supports the following features:
Support for the following Berlin-specific APIs:
- Frequency per day throttling.
- Extended the FrequencyPerDay parameter to clarify the frequency that addresses only the read account data requests (
GET /accounts/{account-id}
) without Payment Service User's involvement.
- Extended the FrequencyPerDay parameter to clarify the frequency that addresses only the read account data requests (
What has changed in this release
- Added the
paymentInformationId
field to the JSON structure of bulk-payments in the Berlin-compliant solution. - As per the Berlin Group NextGenPSD2, when the response body is deleted from the payment cancellation request (
DELETE /{payment-service}/{payment-product}/{paymentId}
), it generates a204
instead of201
error message in the Berlin-compliant solution.
Deprecated features and functionalities
The following features and functionalities are deprecated in WSO2 Open Banking 1.5.0 and will be unavailable from the next release (Open Banking 2.0.0):
- /wiki/spaces/OB150/pages/27919555
- Manual Client Registration
- Dynamic Client Registration v1.0.0
- Support for UK APIs v1.0.0, v1.1.0, and v2.0.0
- Support for Berling APIs v1.0.0 and v1.1.0
- Support for STET APIs v1.4.0
- Support for CDS APIs v0.95 and 1.0.0
- The following versions of Consent Management APIs:
- /consent/uk110 and /consent/uk200
- /consent/berlin110/
- /consent/stet140