Release note

This release note explains what's new in the Open Data API Specifications v2.2.0

Enhancements

• IncrementalBorrowingAmount added to OverdraftFeeChargeDetail section in PCA specification to allow LBG to accurately represent their new overdraft pricing.

• Minimum Arranged Overdraft Amount added for PCA and BCA
• Fee and charges Cap can now be linked with the any Fee Type
• Academic Term has been added to the period code list
• Sort Code added to Branch Locator
• Renamed the FeeMinMaxType field to MinMaxType

Fixes

• Regular Expressions (Regex), that are required to constrain values entered in to fields to a certain pattern, are now in the data dictionary as well as the Swagger. 

• All Notes fields have a consistent cardinality 0..*

• OverdraftFeeApplicableRange section was a modelling error and has been removed from the PCA design

• The Max256Type datatype was not correctly generated in the Swagger files. This has now been fixed.

• Fixed the way that mandatory field restrictions are generated by the Swagger generation script.

• Added missing fee category codes.

• Base path corrected to /open-banking/vX.y

Documentation

• Examples of how to implement overdraft pricing for 4 known pricing models has been added to PCA Message Implementation Guide (MIG)

• MIGs have been converted from Powerpoint to a Confluence & Web-friendly format

• "Compliance Report" has been renamed "Field Mapping Report" to better represent the purpose of this artefact.

• Description of the "Buffer Amount" field has been clarified and an example as to how to implement this added to the PCA Message Implementation Guide (MIG)
• Description of the "TierBandMethod" field in the CreditInterest section was incorrect. This has been changed to "The methodology of how credit interest is paid/applied".
• Replaced Message Implementation Guides with Usage Examples in JSON Request and Response format.

Specifications