As a part of the release candidate consultation process for v2.0.0, we asked for the industry’s opinion on whether there was any additional functionality that would enable use cases not currently supported by the APIs. The Account Information API not including Credit Card accounts and related credit card information was a recurring theme of feedback received, and was identified as a significant barrier to what Third Party propositions c an can cover, and ultimately impacting the potential products offered to their Customers.
...
The standard does not mandate the provision of any account type that a customer cannot currently access via their online banking environment. Each API Providers has variations in their product that will fall into scope of this Standard. To assist Third Parties, it has been agreed that all API Providers must define what account types are available via the API in their developer portals.
It is the intention of the API Centre working groups that as part of future development activities, the scope of account types that are made available through the Account Information API are reviewed and expanded where there is an opportunity to do so as the market matures. This may include adding other account types that are currently not in scope of v2.1 such as foreign currency accounts. This may also include adding products that have joint accounts or have more than one signatory (v2.1 does not currently support multi-authorisation processes).
...
These pages should be read in conjunction with the overview & background pages in order to fully understand the changes made.
Specifications page tree
...
Child pages (Children Display)
all
true
page
API specifications - v2.1.0-
...
rc1
Consultation & feedback
Please refer to the below page to provide your feedback on the release candidate for version 2.0.
