Pre-authorisation 2.0 is an improved pre-authorisation flow to allow for a more flexible authorisation.
We are rolling out the ability for customers to reuse the pre-authorisation for multiple authorisation consents. This change also enables a strategic move towards common pre-authorisation between AIS and PIS where possible with the bank.
Institutions following pre-authorisation 2.0 flow will contain the following features:
INITIATE_ONETIME_PRE_AUTHORISATION_PAYMENTS- when pre-authorisation for payments has to be obtained separately
INITIATE_ONETIME_PRE_AUTHORISATION_ACCOUNTS- when pre-authorisation for account has to be obtained separately
INITIATE_ONETIME_PRE_AUTHORISATION- when pre-authorisation for accounts and payments can be obtained together and separately
to check the features to identify which flow each
Our old pre-authorisation AIS flow requires a new pre-authorised consent for each authorisation to access financial data.
That flow requires users to be redirected to the bank twice.
With the new AIS flow, you can obtain pre-authorised consent that can be used multiple times, therefore, you will no longer need to send your customers to the bank twice as long as full authorisation was completed before.
Initiate the flow illustrated below to obtain pre-authorised consent that will remain valid for the expiry period of the pre-auth consent.
If you already have a pre-authorised consent from the user, you can skip the pre-auth step and create account authorisation by following the diagram below.
Initiate the flow ilustrated below to obtain pre-authorised consent that will remain valid for the expiry period of the pre-auth consent.
If you already have a pre-authorised consent from the user, you can skip the pre-auth step and create payment authorisation by following the diagram below.