1. Version Control

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

2. Introduction

Domestic Standing order allows the user/customer to set up an instruction to their ASPSPs to make a series of payments of a specific amount to a specific payee on a number of specified future dates or on a regular basis. 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. This use case is applicable to both retail and corporate customers. Few sample standing orders may include retail payments such as rent payment, loan re-payment, university/exam fee payments, merchant payments (including bill payments for electricity, water, and telephone), subscription fees, membership fees, and other corporate payments.

This section describes how each of the Participants (PISPs and ASPSPs) involved in the delivery of these services can optimize the customer experience for these services. Furthermore, it provides clarifications to participants on the usage of the APIs, and best practice guidelines for implementation of the customer journeys.

3. Customer Experience Guidelines

3.1 Domestic Standing order – a/c selection @PISP

3.1.1 Customer Experience Journey:

User/Customer can initiate, by providing their consent to PISPs, an instruction to their ASPSPs a series of payments of a specific amount to a specific payee on a number of specified future dates or on a regular basis. Once user/customer has been authenticated in ASPSPs domain, user/customer must be directed back to the PISP domain. 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 standing order, 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/customer to specify the below minimum set of parameters or pre-populate them for the user/customer: Payment Amount and Currency (BHD for Bahrain implementations) Payee Account Name Payee Account Identification details (e.g. IBAN, PAN) Payment Reference (optional)	PISP	Required
2	User/Customer standing order schedule(s) PISPs must provide user/customer at least one of the following options or pre-populate them for the customer: First payment Date, payment Amount and Currency (BHD for Bahrain implementations) Recurring payment date, payment Amount and Currency (only if different from the first payment amount and date) If standing order is not open ended: Either the Final payment Date (only if different from the Recurring payment date), payment Amount and Currency (BHD for Bahrain implementations) Or the Number of payments to be made by the standing order	PISP	Required
3	User/Customer payment Account Selection PISPs must provide user/customer 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 and a user/customer is required to verify/authorize the account identification details in a PISP before storing it in PISP)	PISP	Required
4	User/Customer Consent to PISP PISPs must request for the user/customer' consent to the payment in a clear and specific manner. PISPs must display the following information in the consent screen: The Standing Order Schedule parameters including first payment, recurring payment, final payment and frequency Payment Amount and Currency (BHD for Bahrain implementations) Payee Account Name Payment Reference, if it has been entered by user/customer or prepopulated by PISPs in S.No. 1 User/Customer Payment Account Identification o Note 1: if user/customer payment Account identification is selected in S.No. 3, PISPs should* mask the user/customer payment Account details on the consent screen. Otherwise, or if the user/customer payment Account identification has been input by user/customer in* S.No. 3, PISPs should not* mask these details to allow user/customer to check and verify correctness* o Note2: if user/customer payment Account identification is provided by user/customer in S.No. 3, PISPs may* use this to identify and display the ASPSP without having to ask user/customer* For Payee Account Identification details (e.g. IBAN, PAN): If this has been provided by user/customer in S.No. 1, then PISPs must also display this in the consent screen to allow user/customer to check and verify correctness If this has been pre-populated by PISPs, PISPs may choose whether to display this information or not PISPs must provide messaging to inform user/customer 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
5	CX consideration: Generic PISP to ASPSP redirection screen and message 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. CX consideration: If SCA as described in this section cannot occur on the same screen as displaying the amount and the payee (e.g. for some biometric authentications methods), then ASPSPs should offer user/customer options to proceed or cancel the payment with "equal prominence”	ASPSP	Required
6	ASPSPs must display the payment details, schedule and any supplementary information about difference in actual execution day for each transaction. CX consideration: ASPSPs should inform users/customers about their “point of no return” for making the payment initiation. Example wording: “Press Proceed to initiate the payment “ 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 ASPSP, PISPs must display the following additional information: The expected payment execution date & time The expected settlement date & time (i.e. the value date of the payment) · The ASPSP charges (where applicable) PISPs must provide a message to user/customer to inform that cancelling of the standing order may be done at their ASPSP/PISP. CX consideration: If user/customer provide their payment account identification details (as per S.No. 3 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/customer 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 Domestic Standing Order Payment Consents

This API Specification page details out the Domestic Standing Order Payment Consents resource used by a PISP to register an intent to initiate a Domestic Standing Order Payment.

4.2 Domestic Standing Order Payments

This API Specification page details out the Domestic Standing Order Payment resource used by a PISP to initiate a Domestic Standing Order Payment.