Hi all,
The This release note explains what's new in the Open Data API Specifications v2.1 Specifications are now available on Confluence. We also intend to publish these on the openbanking.org.uk website in early September.
The following defect fixes and enhancements have been made to the APIs from v2.0 are as follows:-
ATM
- Inconsistencies between Swagger file and Data Dictionary - Swagger v JSON inconsistencies, ATM & Branch JSON Inconsistency
- Support for multiple currencies - ATM needs to support multiple currencies
Branch
...
.0.
Fixes
- ATM, Branch, PCA - Inconsistencies between Swagger file and Data Dictionary
- Branch - Timezone issue in Branch opening hours, which forced the implementer to provide local time
...
PCA
...
- PCA - Inconsistencies between the original codelist and the codes in the Data Dictionary
...
...
- PCA, BCA, SME Loans - Addition of missing 'Other' codes from the standard list where there is the ability to provide an OtherCodeType
...
...
Fixed code names in OB_FeeFrequency1Code codelist - Accepted Code Name changes
BCA
- Addition of missing 'Other' codes from the standard list where there is the ability to provide an OtherCodeType -
- Fixed code names in OB_FeeFrequency1Code codelist - Accepted Code Name changes
Commercial Credit Cards
No change
SME Loans
...
- PCA, BCA, SME Loans - Fixed code names in OB_FeeFrequency1Code codelist
...
...
Clarifications
Documentation changes have also been made to the Compliance Report and MIG to:-
- Remove references to fields that appeared in the v1.x data dictionary but where not actually used
...
- Fixed 1 example in the PCA MIG
...
- .
Enhancements
- ATM - Support for multiple currencies
- Branch - Re-design of phone section
- PCA - Multiple segments can be provided for a PCA product