Page Comparison

S. No.

Requirements and Considerations

 Participant

Implementation Requirements

1

Minimum Set of Parameters

PISPs must either allow User/Customers to specify the below minimum set of parameters 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)

• Payment Reference

PISP

Required

2

User/Customer payment Account Selection

PISPs must provide User/Customers at least one of the following options:

• Enter their Payer's payment Account Identification details

• Select their Account Identification details (this assumes they have been saved previously)

PISP

Required

3

PSU Consent to PISP

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

• Payment Amount and Currency (BHD for Bahrain  implementations)

• Payee Account Name

• Payment Reference, if it has been entered by User/Customers or prepopulated by PISPs in item #1

• User/Customer payment Account Identification

  • 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

  • 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 (Bank) without having to ask User/Customer

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

• 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 an e-commerce payment scenario) PISPs may choose whether to display this information or not 

CX consideration:

• PISPs should provide messaging to inform User/Customers that they will be taken to their ASPSPs (Banks) to complete the payment. Example wording: "You will be securely transferred to your ASPSP (Bank) to authenticate and make the payment"

• Generic PISP to ASPSP (Bank) redirection screen and message

PISP

Required

4

SCA-Strong Customer Authentication

ASPSPs (Banks) must apply SCA including dynamic linking, unless an exemption applies. The ASPSP (Bank) authentication must have no more than the number of steps that the User/Customer would experience when directly accessing the ASPSP (Bank) channel.

ASPSP

Required

5

Additional Supplementary Information

ASPSPs (Banks) must be able to introduce a step as part of the authentication journey to display supplementary information associated with that payment if required. If the supplementary information screen is displayed ASPSPs (Banks) must display as minimum the Payment Amount, Currency and the Payee Account Name to make the User/Customer aware of these details.

CX consideration:

• ·        ASPSPs (Banks) should display to User/Customers all the payment instruction information received from PISPs together with the supplementary information. This information may include the following:o  

  • Payment Amount and Currency (BHD for Bahrain implementations)

  o  

  • Payee Account Name

  o  

  • Payment Reference, if it has been entered by User/Customers or prepopulated by PISPs in item #1

  o  

  • User/Customer payment Account Identification

  o  

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

• ·        ASPSPs (Banks) 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 (Banks) must allow User/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“

• Generic ASPSP (Bank) to PISP redirection screen and message

ASPSP

Required

 6

PISP Confirmation

If received from ASPSPs, 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

• initiation

• The expected payment execution date & time

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

• The ASPSP (Bank) charges (where applicable)

 CX consideration:

If PSUs User/Customers provide their payment account identification details (as per item #2 options), the PISP couldmay, with the consent of the PSUUser/Customer, save the account details for future transactions (such as making further payments or initiating refunds back to PSUsUser/Customers) where this is part of the payment initiation service explicitly requested by the PSUUser/Customer. For example, a merchant, upon request from the PSUUser/Customer, may initiate a refund back to the PSUUser/Customer, by instructing the same PISP that initiated the initial PSU User/Customer transaction to use the saved PSU User/Customer payment account identification details as the beneficiary details for the refund. This will be dependent on the same PISP being used by both the PSU User/Customer and the merchant, their specific contractual terms and the existing regulations.

PISP

Required

7

Further Payment Status Update

PISPs must follow up with ASPSPs (Banks) in order to check and update the PSUs User/Customers with the most updated information that can be received by ASPSPs (Banks) in relation to the execution of the payment. For more details on Payment Status, please also refer to section Payment Status.

PISP

Required