User Journey

PSUs can setup, through PISPs, payments which require multiple parties with delegated user authority to authorise a payment order. This functionality can be used by ASPSPs for any payment initiation that requires multiple authorities (including consumers, SMEs and Corporates).

The authentication approach used in this journey replicates journey Single Domestic Payments – Supplementary info, where there is supplementary information to be displayed. If the payment order is incomplete then the principles of journey Single Domestic Payments – a/c selection @ ASPSP apply. The principles of Single Domestic Payments – a/c selection @ PISP may also be applied if all details of the payment order are provided by PISPs, and ASPSPs decide not to display any supplementary information.

 

Wireframes

CEG Checklist Requirements 1

Minimum Set of Parameters: As per Single Domestic Payments – a/c selection @ PISP, item #1.

CEG Checklist Requirements 2

PSU payment Account Selection: As per Single Domestic Payments – a/c selection @ PISP, item #2.

CEG Checklist Requirements 3

PSU Consent to PISP : As per Single Domestic Payments – a/c selection @ PISP, item #3.

CX Considerations 4

As per Single Domestic Payments – a/c selection @ PISP, item #4.

CX Considerations 5

As per Single Domestic Payments – a/c selection @ PISP, item #5.

CEG Checklist Requirements 6

As per Single Domestic Payments – a/c selection @ PISP, item #8.

CX Considerations 7

Although some of the payment instruction order details are known to ASPSPs before PSUs are authenticated, ASPSPs must introduce a step after authentication to display supplementary information associated with the payment such as for example to inform the PSU that the PSU payment Account requires multiple authorisations before the payment can be executed.

CX Considerations 8

ASPSP should display to the PSU all the payment instruction information received from the PISP together with the supplementary information required for the multi-authorisation payment.

CX Considerations 9

ASPSPs should display to PSUs the same information about the multi-auth payment as displayed for multi-auth payments initiated by the PSU directly via the ASPSP's online channels. This information could include the number and name of the authorisers that need to authorise the payment before it can be processed and executed by the ASPSP.

CX Considerations 10

ASPSPs should inform PSUs about their “point of no return” for making the payment and that their payment will be made after pressing the Proceed button. Example wording: “Press Proceed to make payment“.

CX Considerations 11

ASPSP must allow the PSU to proceed with these additional items for the payment initiation or cancel it, on the same screen with steps 7,8 & 9.

CX Considerations 12

As per Single Domestic Payments – a/c selection @ PISP, item #9.

CEG Checklist Requirements 13

PISP Confirmation
PISPs must display the information received from the ASPSP. This information may include:
Whether the payment requires multiple authorisations.
The status of the multiple authorisations.
The number of required authorisations (total required at the start of the multi authorisation journey).
Number of authorisations complete.
The date and time of last authorisation update.
The date and time the authorisation flow must be completed.

CX Considerations 14

If PSUs provided payment account identification details (as per item #2 options), PISP could save the account details for future transactions ,provided that this is explicitly agreed by the PSU.

CEG Checklist Requirements 15

Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12.

Requirements and Considerations

CEG Checklist Requirements & CX Considerations

Minimum Set of Parameters: As per  Single Domestic Payments – a/c selection @ PISP, item #1.

22

PSU payment Account Selection: As per  Single Domestic Payments – a/c selection @ PISP, item #2.

24

Although some of the payment instruction order details are known to ASPSPs before PSUs are authenticated, ASPSPs must introduce a step after authentication to display supplementary information associated with the payment such as for example to inform the PSU that the PSU payment Account requires multiple authorisations before the payment can be executed.

ASPSP should display to the PSU all the payment instruction information received from the PISP together with the supplementary information required for the multi-authorisation payment.

ASPSPs should display to PSUs the same information about the multi-auth payment as displayed for multi-auth payments initiated by the PSU directly via the ASPSP’s online channels. This information could include the number and name of the authorisers that need to authorise the payment before it can be processed and executed by the ASPSP.

ASPSPs should inform PSUs about their “point of no return” for making the payment and that their payment will be made after pressing the Proceed button. Example wording: “Press Proceed to make payment“.

ASPSP must allow the PSU to proceed with these additional items for the payment initiation or cancel it, on the same screen with steps 7,8 & 9.

PISP Confirmation 

PISPs must display the information received from the ASPSP. This information may include:

  • Whether the payment requires multiple authorisations.
  • The status of the multiple authorisations.
  • The number of required authorisations (total required at the start of the multi authorisation journey).
  • Number of authorisations complete.
  • The date and time of last authorisation update.
  • The date and time the authorisation flow must be completed.

25

26

If PSUs provided payment account identification details (as per item #2 options), PISP could save the account details for future transactions ,provided that this is explicitly agreed by the PSU.

Further Payment Status Update: As per  Single Domestic Payments – a/c selection @ PISP, item #12.

27