Contributing to standards development
Registered Community Contributors can read and comment on ‘release candidate’ standards.
Current development pipeline plan
This development pipeline plan outlines current work in progress and is subject to API Council consideration, prioritisation and market feedback. This development plan is subject to change.
The current pipeline plan includes:
- Resolve outstanding issues - finalise any incomplete work-in-progress standards development activity not resolved for inclusion in version 1.0.0.
- Payments Initiation standard v2.0.0 - based on v3 and draft v4 OBIE standards, the UK’s Open Banking Implementation Entity. This standard will be a generational leap and will contain further improvements and benefits, including adding options for the customer not to be redirected from the merchant to their bank, and back again (‘decoupled flow’).
- Enduring consent for Payment Initiation API – will convert the agreed conceptual design of enduring consent for payments into API standards. This will enable customers to set up a long-lived consent for payment arrangements.
- Account Information standard v2.0.0 - also based on v3 and draft v4 OBIE standards, this standard will contain further improvements and benefits.
Contributing to the pipeline plan
Registered Standards Users can contribute to the pipeline plan and the development process. They can also log into Confluence to view and comment on the plan, raise development issues, opportunities, and propose fixes. The API Business and Technical Groups then work together to deliver on the agreed plan of new standards and enhancements. To find out more about the role and responsibilities of the groups, see the About section.
API Community Contributors will also be consulted on the proposed annual pipeline plan.
To find out more about the benefits of being part of our API Centre, see the Join section.