...
# | 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:
|
Additional Consent Parameters TPPs MUST: 1.2 Set/clear the “Is Single Authorization” flag as appropriate (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1rc2standardsv1dot1final/pages/134843363210800446/Common+Rules+and+Guidelines#7.-Is-Single-Authorization-flag). 1.3 Set the Authorization Expiration DateTime (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1rc2standardsv1dot1final/pages/134843363210800446/Common+Rules+and+Guidelines#8.-Authorization-Expiration-DateTime) 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 Expiration DateTime MUST be less than the Requested Execution Date. 1.4 Set/clear the “Is Pay By Account” flag as appropriate in the case the initiated payment is a payment at POS or e-commerce payment. 1.5 Set the Risk Information Block (as perhttps://openfinanceuae.atlassian.net/wiki/spaces/standardsv1rc2standardsv1dot1final/pages/134843363210800446/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 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 Centralized Authentication and Authorization | ||
FDP-5 | 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 and present to Users the relevant 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/standardsv1rc2standardsv1dot1final/pages/134843363210800446/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' “Is Single Authorization” flag, as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1rc2standardsv1dot1final/pages/134843363210800446/Common+Rules+and+Guidelines#7.-Is-Single-Authorization-flag. |
5.6 Display to Users the TPP Trading Name of the TPP that initiated the Single Future Dated Payment (FDP) Consent.
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 cancel the payment journey, if Users decide 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 Change the state of the payment Consent from Awaiting Authorization to Authorized when all Authorizers (one or more) have authorized the payment Consent. 5.11 Update the Future Dated Payment (FDP) Consent details stored in the OFP. | ||
OFP MUST: 5.12 Check the Authorization Time window is valid as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1rc2standardsv1dot1final/pages/134843363210800446/Common+Rules+and+Guidelines#19.-Check-Authorization-Time-Window. 5.13 Confirm back to the LFIs that the Future Dated Payment (FDP) Consent details have been updated successfully. | ||
Multi-Authorization Journey Only | ||
TPPs MUST: 5.15 Submit to OFP the FDP payment initiation requests with the same parameters as per the FDP Payment Consent authorized by the User(s).
| ||
FDP-6 | FDP Warehousing & Scheduling | LFIs MUST: Warehouse the FDP Payment in their systems for it to be scheduled for inititiation, processing and execution on the Requested Execution Date as per BAU future dated payments processing. |
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 |
...