The API standards were developed primarily by two working groups: the API Technical Working Group and the API Business Working Group. All Standards Users can contribute and participate on these working groups. Each group generally meets fortnightly, on alternating weeks. You can see who the API provider and third party Standards Users are on the API Centre public website.

The API Technical Working Group’s main focus from May 2019 to March 2020 was the development of the v2.0 standard. The API standard documentation on Confluence, and Swagger documentation on GitHub, were developed iteratively against an agreed scope of the API standard. Once final drafts of the standard were developed, the working group held longer working sessions to walk through the draft API standard. This helped ensure the final API standard aligned with the scope, accurately reflected the group’s previous discussions and agreements, and that the API standard held together as a whole.

The Business Working Group was instrumental in making scoping decisions on non-technical issues that arose from time to time. They also assessed the risks and scope of the standards, and generally supported the API Centre run the API standards development process.

The v2.0 security profile sets out how third parties connect securely to an API provider.

The v2.0 “NZ Banking Data Security Profile ” v2.0.0 is based on the OpenID Foundation's FAPI Read+Write specification document, and applies this standard to the New Zealand market context. This specification is used to help define requirements for how API providers can safely make APIs available and connect with third parties. This specification applies to both the Payment Initiation and Account Information API specifications. The security profile:

• Aligns with the UK’s upstream OBIE standards.

• Aligns with Australian direction being taken under their open data programme.

• Aligns with general best practice API security practices and global standards.

Key changes made to the v2.0 security profile (compared to v1.0) include:

• Adding the decoupled authentication flow (FAPI-CIBA profile) to accompany the redirect authentication flow.

• Reducing existing optional elements where applicable to simplify implementations and enhance security.

• Additional guidance for clarity.

• Simplifying and restructuring the content of the security profile document.

Functionality delivered by the API standard is supported through the use of static endpoint URLs that allow a developer to enable specific functionality as defined in the specification.

• The Account Information API v2.0 has 24 defined endpoints, enabling access to 11 functions, further detail can be found in the specification Account Information API Specification v2.0.0 .

• The Payments Initiation API v2.0 has 8 defined endpoints, enabling both domestic single payment and enduring payment consents, further detail can be found in the specification Payments Initiation API Specification - v2.0.0 .

The way in which the API specifications have been structured allow the API Centre to mandate a core set of functions that API providers must support when they implement the API standards, as a minimum to meet their obligations in their terms and conditions as a Standards User in the API Centre. There are however a range of additional optional endpoints that API providers can choose to support and provide if they decide to do so.

These endpoints have been defined as ‘mandatory’ and 'optional' in the specification for both the Account Information API Specification v2.0.0 and Payments Initiation API Specification - v2.0.0 APIs.

The endpoints that are being made available will be published on the respective organisations' developer portals and made available upon request.

Customer authentication is a crucial part of the consent journey, where an API provider validates that a customer has authorised a third party’s consent request, before providing access to a protected resource.

This can be carried out using one of two flows defined in the specification. The redirect flow has been defined as a mandatory function and API providers must provide this method of authentication to customers. The decoupled flow has been defined as an optional function and may be implemented by API providers. This information will be made available via their developer portals. More information about decoupled flow and redirect flow can be seen here.

The specifications leverage existing international error responses and structures, and have been expanded and tailored for implementation in the New Zealand environment. Further detail can be found in the API specification, error code enumerations table https://paymentsnz.atlassian.net/wiki/spaces/PaymentsNZAPIStandards/pages/294486025/NZ+Banking+Data+API+Specification+v2.0.0#Enumerations error code enumeration section.