Page Comparison

...

1. A User will initiate a consent from a TPP's mobile or web app.
   

2. The User will be redirected to the LFI's mobile or web app to authorise the consent.

   1. The LFI need to adapt their mobile and/or web app to receive the redirect and parameters passed over from the TPP

   2. The LFI will use the API Hub Authorisation Server to verify the request and the parameters
      

3. The User will go through SCA (Strong Customer Authentication), review the consent, and authorise/reject it.

   1. The LFI needs to adapt their mobile and/or web app to display the consent authorisation screens.

   2. Each consent type will have different information to display to the user

   3. All screens and the required UX guideline will be provided as part of the Open Finance Standards

   4. The LFI will use the Consent Manager and the Authorisation Server to communicate the outcome of the consent authorisation.

   5. The User will be redirected back to the TPP's mobile or web app.

   6. The API Hub will generate the redirect url & access token
      

4. The TPP will receive an access token to allow appropriate actions under the conditions of the consent on the User's account(s).

   1. The Ozone Connect API will be responsible for serving data for action service initiation

...