1. Version Control

Version	Date	Description of Changes
Bahrain OBF v1.0.0	25th Aug 2020	Initial Release

2. Introduction

International Future Dated Payment allows the user/customer to post his/her consent at PISP to make a one-time international payment for a specific amount to a specific payee on a specific future date, wherein the PISP provides this instruction to the customer’s ASPSPs. This use case details out the Customer Experience Guidelines and Technical API Specifications that are required to be developed and followed by both ASPSPs and PISPs. The use case is applicable to both retail and corporate customers.

Few sample International Future Dated Payments may include account to account transfers, loan re-payment, university/exam fee, restaurant/hotel payments, e-commerce payment, wallet payments, invoice and other corporate payments. This is similar to the single international payment, however the payment here is at a future date as against immediate payment in single international payment.

3. Customer Experience Guidelines

3.1 International Future Dated Payment – a/c selection @PISP

3.1.1 Customer Experience Journey:

User/Customer can setup, through PISPs, an instruction to their ASPSPs to make a one-time international payment for a specific amount to a specific payee on a specific future date. The example reference journey illustrates account selection occurring in the PISP domain. However, please note that account selection can take place at the ASPSP domain. For this scenario, please follow the approach as documented in Single Domestic Payment a/c selection @ ASPSP.

For cancellation of International Future Dated Payment, please refer to Single Future Dated Payment - Cancellation of Single Future Dated Domestic Payment @PISP.

3.1.2 Customer Experience Checklist and Customer Experience Considerations

S.No.

Customer Experience Checklist and Customer Experience 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
Destination Country
Instruction Priority (Normal or Urgent)
Payee Account Name
Payee Account Identification details (e.g. IBAN, BBAN (SWIFT))
Any supplementary information required, which the ASPSP has published as required and is specific to that ASPSP
Payment Reference - This is optional but it is good practice to be populated for a payment

CX consideration:

PISPs may display an indicative FX rate for the payment currency pair if:

User/customer selected a user/customer payment Account or provided user/customer payment Account details
User/customer provided the currency of the selected user/customer payment Account

In that case, PISPs must clearly indicate to the user/customer that the FX rate displayed is indicative and may be different to the FX rate to be provided by their ASPSPs.

If the PISP has the ability to provide any actual FX rate quote to the user/customer at this stage (e.g. having implemented a quoting mechanism with the ASPSP) then the PISP should be able to display the actual FX rate to be used for the transaction.

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

Required

3

Execution Date

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

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
Destination Country
Instruction Priority (Normal or Urgent)
Payee Account Name
Payment Reference, if it has been entered by user/customers or pre-populated by PISPs in S.No. 1
User/customer payment Account Identification and/or the selected ASPSP (based on S.No. 2 options)

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, if the user/customer payment Account identification has been input by user/customers in S.No. 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 S.No. 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, BBAN (SWIFT)):

If this has been provided by user/customers in S.No. 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 PISP to ASPSP redirection screen and message

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

6

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. Moreover, ASPSPs must allow the user/customer to provide additional details related to the payment order during the authentication journey (authentication and supplementary information screens) such as for example, the account for the payment. The information to be provided in the supplementary information / additional payment order details screen may include:

User/customer payment Account Identification
Payee Account Name
Payment Reference
Payment Execution Date
Payee Account Identification details (e.g. IBAN, BBAN (SWIFT))
Country
Payment Currency
Payment Amount
FX currency pair and rate
Bank Charges
Payment priority (Normal or Urgent)

ASPSPs must display to the user/customer the FX currency conversion rate to be used for the payment order. This FX rate can be:

Indicative - In this case ASPSPs must clearly inform user/customer that the FX rate is indicative and may be different than the actual rate that will be used for the payment order
Actual - ASPSPs must clearly inform the user/customer for the validity period of this actual FX rate. If the payment order is not submitted within the validity window of the FX, then a new actual FX quote must be displayed. If user/customer confirm the payment but the payment order submitted by PISPs is not submitted within the validity period, ASPSPs may choose to either reject the payment or process it at the agreed FX rate
ASPSPs may display the payment amount in the user/customer payment Account currency (from applying the FX rate).

CX consideration:

ASPSPs should ensure that charges related to international payments are provided to user/customer as agreed in the framework contract

o Note1: Any provision of charges can only be those of the ASPSP as the Beneficiary's bank charges are not known in many cases

o Note 2: Where the final charges are not known to the ASPSP, the responsibility should remain with the ASPSP for notifying the customer of the charges as per the Bahrain OBF regulatory requirements

Other Options:

o ASPSPs should display the Final Debit Amount (including charges) in user/customer payment Account currency

o ASPSPs may display the expected Value Date for the international payment

ASPSPs should inform the user/customer about their “point of no return” for making the payment initiation Example wording: “Press Proceed to initiate the payment"
ASPSPs should allow the user/customer 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 ASPSP to PISP redirection screen and message

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)
Actual FX rate used for the international payment transaction

PISPs must provide a message to user/customer to inform that cancelling of the international future payment order may be done at their ASPSP/PISP.

CX consideration:

If user/customer provide their payment account identification details (as per S.No. 2 options), PISPs may save the account details for future transactions, where this is part of the payment initiation service explicitly requested by the user/customer.

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

4. API specification: Brief description

4.1 International Future Dated Payment Consents

This API Specification page details out the International Future Dated Payment Consents resource used by a PISP to register an intent to initiate a International Future Dated Payment.

4.2 International Future Dated Payments

This API Specification page details out the International Future Dated Payment resource used by a PISP to initiate a International Future Dated Payment.