Requirements and Considerations

 Participant

Implementation Requirements

1

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

2

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

3

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

4

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

5

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

6

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