...
The development of the v2.2 & v2.3 release candidates need to be considered in the context of a wider standards development roadmap. The main objective of the v2.2 & v2.3 API standards is to shift existing ‘optional’ functionality contained in earlier versions to being mandatory ‘mandatory’ for API Providers to implement.
This is shift to Mandatory ‘mandatory’ will clearly define and set an implementation pathway for API Providers to provide support for key functions already defined and published in the Standards.
...
multi-authorisation capability, which will enable the open banking standardised APIs to be used by some business accounts or joint accounts, which commonly require more than one account holder to authorise an action;
two-way notifications (commonly referred to as ‘event notifications’), which will enable API Providers to push notifications to Third Parties. The standard will create an event-subscription resource with an API Provider so that the API Provider knows the Third Party would like to subscribe to updates. The API Provider can then send a signed event notification to the Third Party. This functionality makes the open banking standardised APIs more usable by Third Parties, and also puts in place capability building blocks that we can use when we want to introduce new functionality in the future; and
we are also carrying out initial assessments on expanding the scope of v3.0 to include the potential for introducing standardised APIs that enable a payment refund capability.
...