_{S. No.}

_{Requirements and Considerations}

 _Participant

_{Implementation Requirements}

 ₁

_{Minimum Set of Parameters}

_{PISPs must either allow PSUs to specify the below minimum set of parameters or pre-populate them for the PSUs:}

• _{Payment Amount and Currency (BHD for Bahrain implementations)}

• _{Payee Account Name}

• _{Payee Account Identification details (e.g. account number and IBAN)}

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

 _PISP

 _Required

₂

_{PSU payment Account Selection}

_{PISPs must provide PSUs 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)}

• _{Select their ASPSP in order to select their PSU payment Account from there later on in the journey}

 _PISP

 _Required

₃

_{Execution Date}

_{PISPs must allow PSUs to select the expected execution date for the payment by the ASPSPs}

 _PISP

 _Required

₄

_{PSU Consent to PISP}

_{PISPs must request for the PSUs' 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 PSUs or pre-populated by PISPs in item #1}

• _{PSU payment Account Identification and/or the selected ASPSP (based on item #2 options)}

  • _{Note 1: if PSU payment Account identification is selected in item #2, PISPs should mask the PSU payment Account details on the consent screen. Otherwise, if the PSU payment Account identification has been input by PSUs in item #2, PISPs should not mask these details to allow PSUs to check and verify correctness}

  • _{Note 2: if PSU payment Account identification is provided by PSUs in item #2, PISPs could use this to identify and display the ASPSP without having to ask PSUs}

_{For Payee Account Identification details (e.g. account number and IBAN):}

• _{If this has been provided by PSUs in item #1, then PISPs must also display this in the consent screen to allow PSUs to check and verify correctness}

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

_{CX consideration:}

_{PISPs should provide messaging to inform PSUs 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"}

 _PISP

 _Required

₅

_{CX consideration:}

_{Generic PISP to ASPSP redirection screen and message. Please refer to Section 2.2.5}

_{SCA Authentication (including dynamic linking) must be the only action required at the ASPSPs (unless supplementary information required, refer to section 1.1.3).}

_{The ASPSP authentication must have no more than the number of steps that the PSU would experience when directly accessing the ASPSP channel}

 _ASPSP

 _Required

₆

_{ASPSPs must display the payment details and any supplementary information about difference in actual execution date}

_{CX consideration:}

• _{ASPSPs must 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”}

• _{ASPSPs must allow PSUs to review the information described above. The PSU 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. Please refer to Section 2.2.5}

 _ASPSP

 _Required

₇

_{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 by ASPSPs, PISPs must display any of the following information regarding initiation and execution of the payment:}

• _{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

₈

_{Further Payment Status Update}

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

 _PISP

 _Required

_{S. No.}

_{Requirements and Considerations}

 _Participant

_{Implementation Requirements}

₁

_{PISPs must provide PSUs to view and select from the list of future dated payment initiated at the PISP}

_{PISPs must allow PSUs to select only those payments that have at least 48 hours buffer from the execution date and time}

_{`CX Consideration:}

_{PISP could send notifications to PSUs with the following detail:}

• _{Last applicable date for cancellation of the initiated future dated payment from PISP portal}

_PISP

_Required

₂

_{PSU Consent to PISP}

_{PISPs must request for the PSUs' consent to the cancellation of the future dated payment in a clear and specific manner. PISPs must display the following information in the consent screen:}

• _{Payment identifier assigned by the ASPSP}

• _{Payment Amount and Currency (BHD for Bahrain implementations)}

• _{Payee Account Name}

• _{Payment Reference, if it has been entered by PSUs or pre-populated by PISPs}

• _{Expected Payment Execution date}

• _{PSU payment Account Identification and/or the selected ASPSP}

_{CX consideration:}

_{PISPs should provide messaging to inform PSUs that they will be taken to their ASPSPs to complete the cancellation}

_{Example wording: "You will be securely transferred to YOUR ASPSP to authenticate and cancel the initiated payment"}

_PISP

_Required

₃

_{CX consideration:}

_{Generic PISP to ASPSP redirection screen and message. Please refer to Section 2.2.5}

_{SCA Authentication}

_{SCA Authentication (including dynamic linking) must be the only action required at the ASPSPs (unless supplementary information required, refer to section 1.1.3).}

_{The ASPSP authentication must have no more than the number of steps that the PSU would experience when directly accessing the ASPSP channel}

_ASPSP

_Required

₄

_{Additional Information}

_{ASPSPs must display the cancellation details and any supplementary information such as charges incurred, etc.}

_{CX consideration:}

• _{ASPSPs must inform PSUs about their “point of no return” for cancellation and that their cancellation will be made after pressing the proceed button. Example wording: "Press proceed to cancel the initiated payment”}

• _{ASPSPs must allow PSUs to review the information described above. The PSU can either proceed with the cancellation  or terminate the process, on the same screen using options with “equal prominence”}

• _{Generic PISP to ASPSP redirection screen and message. Please refer to Section 2.2.5}

_ASPSP

_Required

₅

_{PISP Confirmation}

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

• _{The unique identifier assigned to the cancelation instruction by ASPSPs}

• _{The cancellation status (and status update date & time) - Confirmation of successful cancellation of the initiated payment}

_{If received by ASPSPs, PISPs must display any of the following information regarding the ASPSP charges (where applicable)}

_PISP

_Required

₆

_{Further Status Update}

_{PISPs must follow up with ASPSPs in order to check and update the PSUs with the most updated information that can be received by ASPSPs in relation to the execution of the cancellation}

_PISP

_Required