Page Comparison

S. No.

Requirements and Considerations

 Participant

Implementation Requirements

 11

Minimum Set of Parameters

PISPs must either allow user/customers to specify the below minimum set of parameters or or pre-populate them for the user/customers:

• Payment Amount and Currency (BHD for Bahrain implementations)

• Payee Account Name

• Payee Account Identification details (e.g. IBAN, PAN)

• Payment Reference - This is optional but it is good practice to be populated for a payment

 PISP

PISP

Required

2

User/Customer payment Account Selection

PISPs must provide user/customers at least one of the following options:

• Enter their payment Account Identification details

• Select their Account Identification details (this assumes they have been saved previously and a user/customer is required to verify/authorize the account identification details in a PISP before storing it in PISP)

• Select their ASPSP in order to select their user/customer payment Account from there later on in the journey

 PISP

PISP

Required

3

Execution Date

PISPs must allow user/customers to select the expected execution date for the payment by the ASPSPs

 PISP

 Required 

PISP

Required

4

User/Customer Consent to PISP

PISPs must request for the user/customers' consent to the payment in a clear and specific manner. PISPs must display the following information in the consent screen:

• Payment Execution Date

• Payment Amount and Currency (BHD for Bahrain implementations)

• Payee Account Name

• Payment Reference, if it has been entered by user/customers or pre-populated by PISPs in item #1

• User/Customer payment Account Identification and/or the selected ASPSP (based on item #2 options)

o    Note 1: if user/customer payment Account identification is selected in item #2, PISPs should mask the user/customer payment Account details on the consent screen. Otherwise, if the user/customer payment Account identification has been input by user/customers in item #2, PISPs should not mask these details to allow user/customers to check and verify correctness

o    Note 2: if user/customer payment Account identification is provided by user/customers in item #2, PISPs may use this to identify and display the ASPSP without having to ask user/customers

For Payee Account Identification details (e.g. IBAN, PAN):

• If this has been provided by user/customers in item #1, then PISPs must also display this in the consent screen to allow user/customers to check and verify correctness

• If this has been pre-populated by PISPs (e.g. in a ecommerce payment scenario) PISPs may choose whether to display this information or not

• PISPs must provide messaging to inform user/customers that they will be taken to their ASPSPs to complete the payment. Example wording: "You will be securely transferred to your ASPSP to authenticate and make the payment"

 CX consideration:

• Generic Generic PISP to ASPSP redirection screen and message

 PISP

 Required

5 

PISP

Required

 5

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

 ASPSP

 Required   

ASPSP

Required

6

Additional Supplementary Information

ASPSPs must display as minimum the Payment Amount, Currency and the Payee Account Name, payment execution date, payment reference (if it has been entered by userUser/customers Customers or prepopulated by PISPs in item #1) to make the userUser/customer Customer aware of these details. ASPSPs must may display the payment details and any additional supplementary information about difference in actual execution date.

CX consideration:

• ASPSPs should allow user/customers to review the information described above. The user/customer can either proceed with the payment or cancel it, on the same screen using options with “equal prominence”

• ASPSPs should inform user/customers 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”ASPSPs should allow user/customers to review the information described above. The user/customer can either proceed with the payment or cancel it, on the same screen using options with “equal prominence”

• Generic PISP to ASPSP redirection screen and message

 ASPSP

ASPSP

Required

7

PISP Confirmation

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

• The unique identifier assigned to the payment instruction by ASPSPs

• The payment status (and status update date & time) - Confirmation of successful payment initiation

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

• The expected payment execution date & time

• The expected settlement date & time (i.e. the value date of the payment)

• The ASPSP charges (where applicable)

 PISP

 Required

8

Further Payment Status Update

PISPs must follow up with ASPSPs in order to check and update the user/customers with the most updated information that can be received by ASPSPs in relation to the execution of the payment

 PISP

 Required