Other pages in this section Account selection at PISP Account Selection at PISP – Supplementary Info Account Selection at ASPSP Scheduled Payments – Future Dated Standing Orders International Payments Bulk / Batch Payments Multi-authorisation Payments Confirmation of Funds for PISP – Y/N Response Payment Refunds VRP Payments with an SCA exemption VRP Payments under Sweeping Access VRP Payments with delegated SCA VRP Consent Dashboard & Revocation VRP – Access Dashboard & Revocation
This content is best viewed on a desktop browser. 1 CEG Checklist Requirements 1Minimum Set of Parameters: As per Single Domestic Payments – a/c selection @ PISP, item #1. 2 CEG Checklist Requirements 2PSU payment Account Selection: As per Single Domestic Payments – a/c selection @ PISP, item #2. 3 CEG Checklist Requirements 3PSU Consent to PISP : As per Single Domestic Payments – a/c selection @ PISP, item #3. 4 CX Considerations 4As per Single Domestic Payments – a/c selection @ PISP, item #4. 5 CX Considerations 5As per Single Domestic Payments – a/c selection @ PISP, item #5. 6 CEG Checklist Requirements 6As per Single Domestic Payments – a/c selection @ PISP, item #8. 7 CX Considerations 7Although 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. 8 CX Considerations 8ASPSP 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. 9 CX Considerations 9ASPSPs 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. 10 CX Considerations 10ASPSPs 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“. 11 CX Considerations 11ASPSP 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. 12 CX Considerations 12As per Single Domestic Payments – a/c selection @ PISP, item #9. 13 CEG Checklist Requirements 13PISP 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. 14 CX Considerations 14If 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. 15 CEG Checklist Requirements 15Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12. Select to scroll left Select to scroll right
CEG Checklist Requirements & Customer Experience Considerations 1 Minimum Set of Parameters: As per Single Domestic Payments – a/c selection @ PISP, item #1. 22 2 PSU payment Account Selection: As per Single Domestic Payments – a/c selection @ PISP, item #2. 24 3 PSU Consent to PISP : As per Single Domestic Payments – a/c selection @ PISP, item #3. 8 4 As per Single Domestic Payments – a/c selection @ PISP, item #4. 5 As per Single Domestic Payments – a/c selection @ PISP, item #5. 6 As per Single Domestic Payments – a/c selection @ PISP, item #8. 19 1 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. 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. 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. 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“. 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. 12 As per Single Domestic Payments – a/c selection @ PISP, item #9. 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. 25 26 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. 15 Further Payment Status Update: As per Single Domestic Payments – a/c selection @ PISP, item #12. 27
Bulk / Batch Payments Previous Related articles Please select API specifications Multiple Authorisation Multi-Auth Payment Order Consent Confirmation of Funds for PISP – Y/N Response Next