...
S.No. | Customer Experience Checklist and Customer Experience Considerations | Participant | Implementation Requirements |
1 | Minimum Set of Parameters PISPs must either allow users/customers to specify the below minimum set of parameters or pre-populate them for the users/customers:
|
PISP |
Required |
2 | User/Customer payment Account Selection PISPs must provide users/customers at least one of the following options:
|
PISP |
Required |
3 | User/Customer Consent to PISP PISPs must request for the users'/customers' consent to the payment in a clear and specific manner. PISPs must display the following information in the consent screen:
o Note 1: if user/customer payment Account identification is selected in S.No. 2, PISPs should mask the user/customer payment Account details on the consent screen. Otherwise, or if the user/customer payment Account identification has been input by users/customers in S.No. 2, PISPs should not mask these details to allow users/customers to check and verify correctness For Payee Account Identification details (e.g. IBAN, PAN):
|
PISP |
Required
|
4 | CX consideration:
SCA-Strong Customer Authentication SCA must be the only action required at the ASPSPs (unless supplementary information required). The ASPSP authentication must have no more than the number of steps that the user/customer would experience when directly accessing the ASPSP channel. CX consideration:
|
ASPSP |
Required |
5 | ASPSPs must display as minimum as the Payment Amount, Currency and the Payee Account Name to make the user/customer aware of these details (unless an SCA exemption is being applied). These details must be displayed as part of the authentication journey on at least one of the following screens without introducing additional confirmation screens (unless supplementary information is required):
Note: Displaying the balance in this instance need not require any additional strong customer authentication CX consideration:
|
ASPSP |
Required |
6 | PISP Confirmation PISPs must display the information received from the ASPSP. This information may include:
If received from ASPSP, PISPs must display the following additional information:
In case of payment cancellation, CX consideration:
|
PISP
|
Required
|
7 | Further Payment Status Update PISPs mustfollow up with ASPSPs in order to check and update the users/customers with the most updated information that can be received by ASPSPs in relation to the execution of the payment. |
PISP |
Required |
...
S. No. | Customer Experience Checklist and Customer Experience Considerations | Participant | Implementation Requirements |
1 | Minimum Set of Parameters PISPs must either allow users/customers to specify the below minimum set of parameters or pre-populate them for the users/customers:
|
PISP |
Required |
2 | User/Customer payment Account Selection PISPs must provide users/customers at least one of the following options:
|
PISP |
Required |
3 | User/Customer Consent to PISP PISPs must request for the users'/customers' consent to the payment initiation in a clear and specific manner. PISPs must display the following information in the consent screen:
o Note 1: if user/customer payment Account identification is selected in S.No. 2, PISPs should mask the user/customer payment Account details on the consent screen. Otherwise, or if the user/customer payment Account identification has been input by users/customers in S.No. 2, PISPs should not mask these details to allow users/customers to check and verify correctness For Payee Account Identification details (e.g. IBAN, PAN):
|
PISP |
Required
|
4 | CX consideration:
SCA-Strong Customer Authentication ASPSPs must apply SCA unless an exemption applies. The ASPSP authentication must have no more than the number of steps that the user/customer would experience when directly accessing the ASPSP channel. |
ASPSP |
Required |
5 | Additional Supplementary Information ASPSPs must be able to introduce a step as part of the authentication journey to display supplementary information associated with that payment if required. ASPSPs must display to users/customers all the payment instruction information received from PISPs together with the supplementary information. This information may include the following:
ASPSPs must allow users/customers to review as a part of the authentication process any supplementary Information. The user/customer can either proceed with the payment or cancel it on the same screen with supplementary information details, using options with "equal prominence“ CX consideration:
|
ASPSP |
Required |
6 | PISP Confirmation PISPs must display the information received from the ASPSP. This information may include:
If received from ASPSP, PISPs must display the following additional information:
In case of payment cancellation, CX consideration:
|
PISP
|
Required
|
7 | Further Payment Status Update PISPs must follow up with ASPSPs in order to check and update the users/customers with the most updated information that can be received by ASPSPs in relation to the execution of the payment. |
PISP |
Required |
...