1. Description
One-time payment scheduled for execution in the future. A Future Dated Payment (FDP) is initiated by a TPP from a payment account held at the LFI with the explicit consent of the User. The payment is initiated by the LFI on the date scheduled by the TPP. The TPP acquires explicit consent from the User for a single-use access to the User’s payment account. The User MUST authenticate with the LFI and authorize the single-use consent. The payment related to the authorized consent, is warehoused by the LFI and is initiated by LFI on the day it is due, as per the authorized consent.
The FDP scope is targeted to domestic payee accounts (i.e. payee accounts offered by LFIs located in UAE) and payments in local currency as used by the local payment systems infrastructure for domestic payments.
This funtionality requires a Single-Use Consent. The consent parameter type for this capability is Single Future Dated Payment Consent, which MUST be used for a single payment which will be initiated by the LFI in the future after User authorization at the LFI.
1.1 Payer and Payee Segments
The scope of the FDP bank service initiation related to the segments of payers and payees is shown below:
Payer | Payee | ||||
|---|---|---|---|---|---|
Consumers | SME | Corporates | Consumers | SME | Corporates |
|
|
|
|
|
|
1.2 Future Dated Payment (FDP) - Example User Story
User Story
As a User (Consumer or Business),
I want to provide my consent to a TPP to use my payment account for scheduling with my LFI a Single Future Dated payment of a fixed amount to a domestic beneficiary account owned by a business or an individual,
so that I can pay the relevant beneficiary.
2. User Journey
Users can schedule, by providing their consent to TPPs, a payment order to their LFIs to make a one-off single payment of a specific amount to a specific payee on a specific date.
3. Wireframes
%20NEW2.png?version=1&modificationDate=1718366050878&cacheVersion=1&api=v2&width=1280&height=578)
3.1. Rules & Guidelines
# | Step | Rules & Guidelines |
|---|---|---|
FDP-1 | Single Future Dated Payment Consent | Basic Consent Parameters TPPs MUST: 1.1 Enable Users to provide and review the parameters related to the FDP they need to consent to. These parameters include:
Note: Depending on the use case, the Payee details may not be displayed to Users in full. However, these still need to be part of the payment Consent request sent by the TPP.
|
Additional Consent Parameters TPPs MUST: 1.2 Set the Accepted Authorization Type (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft3/pages/70092902/Common+Rules+and+Guidelines#7.-Accepted-Authorization-Type). 1.3 Set the Authorization Time Window (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft3/pages/70092902/Common+Rules+and+Guidelines#8.-Authorization-Time-Window) if there are specific timing requirements that must be met for the consent authorization. This is also relevant to cases where multiple authorizers are required to authorize the payment consent. The Authorization Time Window MUST be less than the Requested Execution Date. 1.4 Set the Consent Expiry Date accordingly if the Authorization Time Window is set to more than 1 day. This is to avoid the consent expiring before all necessary authorizations are completed. Otherwise, the default value of the Consent Expiry Date MUST be set to the same day (i..e current day). The Consent Expiry Time MUST always be set to 23:59:59 of the Consent Expiry Date. 1.5 Set the Risk Information Block (as perhttps://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft3/pages/70092902/Common+Rules+and+Guidelines#9.-Risk-Information-Block) 1.6 Enable Users to provide explicit consent for the initiation (i.e. scheduling) of a Single Future Dated payment from their online payment account held at their LFI as per the payment parameters specified in the consent. | ||
FDP-2 | Consent Staging | |
FDP-3 | Hand-off to LFI | Example wording to use: ‘We will securely transfer to YOUR LFI to authenticate and authorize your payment setup“. |
FDP-4 | Authentication | LFI Authentication Only LFIs MUST: 4.1 Enable Users to perform authentication with their LFIs, as per the following sections: 4.2 Re-direct Users back to the TPPs, with information that the Consent has not been authorized, if User Authentication has failed or Users opted to cancel the authentication/authorization process. |
Centralized Authentication and Authorization (Federated) Only 4.3 As per https://openfinanceuae.atlassian.net/wiki/x/HoBBAw | ||
FDP-5 | Confirmation/ Authorization | LFIs MUST: 5.1 Enable Users to authenticate using Multi-Factor Authentication (MFA) in order to review and authorize the Single Future Dated Payment (FDP) Consent. 5.2 Retrieve from the OFP the Future Dated Payment (FDP) Consent details staged by the TPP using the unique Consent Identifier and present to Users all the details included in this. 5.3 Allow Users to select a payment account for the initiation of the Future Dated Payment (FDP), if this was not provided in the retrieved staged Payment Consent details as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft3/pages/70092902/Common+Rules+and+Guidelines#12.-Payment-Account-Selection-at-LFI
5.4 NOT earmark (i.e. block) the funds related to the Future Dated Payment in the Users' payment account. 5.5 Check the authorization status of the selected payment account is in accordance with the TPPs' Accepted Authorization Type as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft3/pages/70092902/Common+Rules+and+Guidelines#13.-Check-Accepted-Authorization-Type. |
Using Proxy for Beneficiaries Only 5.6 Add to the Future Dated Payment Consent the IBAN of the Payee returned by the Proxy resolution process, if the Future Dated Payment Consent was submitted for User Authorization using a Proxy as the Payee Identification. The Consent is thereafter tied to the IBAN of the Payee rather than the proxy itself. This will allow the payment to be initiated to this IBAN even if the Payee changes the proxy between the time of the Future Dated Payment Consent and the initiation of the Future Dated Payment.
| ||
5.7 Present to Users the following minimum required information for authorizing the Single Future Dated Payment (FDP) Consent:
5.8 Request Users to authorize the Future Dated Payment (FDP) Consent, so that the future dated payment can be scheduled and warehoused by the LFI. 5.9 Provide Users the ability to abort the payment journey, if Users decided to terminate the request. The LFI MUST hand-off the Users back to the TPP, providing the necessary error message to the OFP and reject the Future Dated Payment (FDP) Consent. 5.10 Check the Authorization Time window is valid as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft3/pages/70092902/Common+Rules+and+Guidelines#20.-Check-Authorization-Time-Window 5.11 Change the state of the payment Consent from Awaiting Authorization to Authorized when all Authorizers (one or more) have authorized the payment Consent. 5.12 Update the Future Dated Payment (FDP) Consent details stored in the OFP with all the information included in the Future Dated Payment (FDP) Consent authorized by the User. | ||
OFP MUST: 5.13 Confirm back to the LFIs that the Future Dated Payment (FDP) Consent details have been updated successfully. | ||
Multi-Authorization Journey Only | ||
FDP-6 | FDP Warehousing & Scheduling | LFIs MUST: 6.1 Warehouse the FDP Payment in their systems for it to be scheduled for inititiation, processing and execution on the Requested Execution Date. |
FDP-7 | Hand-off back to the TPP | |
FDP-8 | Confirmation to User | |
FDP-9 | FDP Initiation, Processing & Execution | LFIs MUST: 9.1 Allow the FDP Payment to be initiated on the Requested Execution Date without any additional MFA or authorization from the User. 9.2 Schedule the initiation, processing and execution time at the future Requested Execution Date to occur as per their existing BAU process for Future Dated Payments initiated via other LFI channels. 9.3 Apply all existing BAU payment account controls and limits such as single transaction value limit, total transaction value limit, AML checking (if applicable) and others, as if the payment request has been initiated by the existing channels of the LFI. 9.4 Follow existing BAU processing rules in cases the payment account selected for the payment has insufficient funds. LFIs may reject the FDP payment completely or may have processes in place that would allow the retry of the FDP payment at a later time on the same day, to allow Users to place funds to the account so that sufficient balance is available for the execution of the Future Dated Payment (FDP). 9.5 Subject to successful BAU checking, validation and payment processing, proceed with the execution of the Futue Dated Payment (FDP) by either submitting the payment to the underlying payment rails or executing internally as Intra-bank payment. |
FDP-10 | Payment Notifications |