Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Inbound redirection screen (from User-facing TPP to LFI) – owned by the User-facing TPP – from the User-facing TPP domain to the LFI domain, after the User has provided consent to the User-facing TPP for the OB service. For the avoidance of doubt, LFIs MUST not present any additional inbound redirection screens.

  • Outbound redirection screen (from LFI to User-facing TPP) – owned by the LFI – from the LFI domain to the User-facing TPP domain, after the LFI has authenticated the User and completed the OB service request (e.g. DSR,SIR).

The redirection screens are a useful part of the process, providing User trust. The following reasons are noted:

  • They help Users navigate their online journey and inform them of what is going to happen next.

  • They help create a clear sense of separation between the User-facing TPP's domain and the LFIs domain.

The messaging on the redirection screens serves to reassure the User that they are in control and helps engender trust. For example, Users will be more willing to trust the process if they feel there is a partner (User-facing TPP or LFI) on their side that is known and reputable (use language such as ‘we’, ‘our’). In this sense, the use of words that indicate that the User is in control and taking the lead is key, as these are indications that the User-facing TPP or the LFI is working with or for the User.

(info) Note: The duration Redirection Screens are shown to Users MUST be plausible for the Users to clock the journey.

image-20240726-142412.png

 

4.1 Redirection Screen Variation

...