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:

• User Payment Account or User LFI (as per Common Rules and Guidelines | 2. User Payment Account Selection).

• Payment Amount & Currency (as per Common Rules and Guidelines | 3. Payment Amount & Currency).

• Payee Identification details (as per Common Rules and Guidelines | 4. Payee Identification).

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.

• Payer Note (as per Common Rules and Guidelines | 5. Payer Note) (Optional).

• Payment Reference (as per Common Rules and Guidelines | 6.Payment Reference).

• Purpose of Payment (as per Common Rules and Guidelines | 21. Purpose of Payment).

• Requested Execution Date, as per the following:

  • 1.1.1 Either allow Users to manually enter the date when the payment needs to be executed or pre-populate it for Users based on the specific business case and the receiving beneficiary party.

  • 1.1.2 Specify the Requested Execution Date to a date in the future and cannot use the same day or a day in the past.

  • 1.1.3 NOT allow Users to select the time of the future date for the payment to be initiated. This is to prevent Users entering time values that could lead to either sub-optimal payment load balancing or limited time available for retries of payments which have failed due to funds checking, unavailability.

Additional Consent Parameters

TPPs MUST:

1.2 Set the Accepted Authorization Type (as per Common Rules and Guidelines | 7. Accepted Authorization Type).

1.3 Set the Authorization Time Window (as per 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 perCommon 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.

Consent Staging

As per Common Rules and Guidelines | 10. Consent Staging

Hand-off to LFI

As per Common Rules and Guidelines | 11. Hand off to LFI

Example wording to use: ‘We will securely transfer to YOUR LFI to authenticate and authorize your payment setup“.

Authentication

LFI Authentication Only

LFIs MUST:

4.1 Enable Users to perform authentication with their LFIs, as per the following sections:

• Authentication by LFI | 2. Redirection

• Authentication by LFI | 3. Decoupled Redirection

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

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 Common Rules and Guidelines | 12. Payment Account Selection at LFI

• 5.3.1 Allow Users to select the payment account for the initiation of the Future Dated Payment even if it has insufficient funds at the time of consent authorization. This allows Users to fund the payment accounts appropriately before the future dated payment is initiated.

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/standardsv1draft4/pages/98339394/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.6.1 Return back to the OFP (and the TPP) in the payment Consent response the IBAN of the Payee identification returned by the Proxy resolution.

5.7 Present to Users the following minimum required information for authorizing the Single Future Dated Payment (FDP) Consent:

• User Payment Account

• Payment Amount & Currency

• Payee Identification details including:

  • Payee Name

  • Payee proxy

  • Payee Account Holding LFI

• Payer Note (Optional)

• Payment Reference

• Purpose of Payment

• Requested Execution Date

• Fees & VAT (if applicable): These are the charges that may be applied to the User account for making the payment in relation to the Future Dated Payment (FDP) Consent. Both bank charges and VAT MUST be presented and stated separately, prior to the User Consent authorization. If applicable, LFIs MUST apply the charges on the date of the payment initiation and not at the point of Consent Authorization.

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/standardsv1draft4/pages/98339394/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

5.14 As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98339394/Common+Rules+and+Guidelines#18.-Multi-User-Authorization-Flow

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.

Hand-off back to the TPP

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98339394/Common+Rules+and+Guidelines#14.-Hand-off-back-to-the-TPP

Confirmation to User

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98339394/Common+Rules+and+Guidelines#16.-Confirmation-to-User

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.

Payment Notifications

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98339394/Common+Rules+and+Guidelines#17.-Payment-Notifications