...
# | Step | Rules & Guidelines |
|---|---|---|
FDCS-1 | Single Future Dated Payment Consent | Basic Consent Parameters TPPs MUST: 1.1 Enable Users to provide and review the parameters related to the SIP 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/standardsv1draft2/pages/52528830/Common+Rules+and+Guidelines#7.-Accepted-Authorization-Type). 1.3 Set the Authorization Time Window (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft2/pages/52528830/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 Expiration Date & Time to be the end of day (23:59:59) of the Requested Execution Date. This will allow the TPP to have a valid consent to be used for retries when looking for recovery from certain erroneous scenarios. 1.5 Set the Risk Information Block (as perhttps://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft2/pages/52528830/Common+Rules+and+Guidelines#9.-Risk-Information-Block) 1.6 Enable Users to provide explicit consent for the initiation of a Single Future Dated payment from their online payment account held at their LFI as the payment parameters specified in the consent. | ||
FDCS-2 | Consent Staging | |
FDCS-3 | Hand-off to LFI | Example wording to use: ‘We will securely transfer to YOUR LFI to authenticate and authorize your payment setup“. |
FDCS-4 | Authentication | LFI Authentication Only As per the following sections: |
Centralized Authentication and Authorization (Federated) Only As per https://openfinanceuae.atlassian.net/wiki/ spaces/standardsv1draft2/pages/52527741/Authentication+and+Authorization#4.-Decoupled-CIBA | ||
FDCS-5 | Confirmation/ Authorization | LFIs MUST: 5.1 Enable Users to authenticate using Multi-Factor Authentication (MFA) in order to review and authorize the long-lived Single Future Dated Consent. 5.2 Retrieve from the OFP the Future Dated Payment Consent details staged by the TPP using the unique Consent Identifier. 5.3 Allow Users to select a payment account for the initiation of the Future Dated Payment, if this was not provided in the retrieved staged Payment Consent details as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft2/pages/52528830/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/standardsv1draft2/pages/52528830/Common+Rules+and+Guidelines#13.-Check-Accepted-Authorization-Type. 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 Long-lived Single Future Dated Consent:
5.8 Check the Authorization Time window is valid as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft2/pages/52528830/Common+Rules+and+Guidelines#20.-Check-Authorization-Time-Window 5.9 Change the state of the payment Consent from Awaiting Authorization to Authorized when all Authorizers (one or more) have authorized the payment Consent. 5.10 Update the Future Dated Payment Consent details stored in the OFP with all the information included in the Future Dated Payment Consent authorized by the User. |
OFP MUST: 5.11 Confirm back to the LFIs that the Future Dated Payment Consent details have been updated successfully. | ||
Multi-Authorization Journey Only | ||
FDCS-6 | Hand-off back to the TPP | |
FDCS-7 | Confirmation to User | |
FDCS-8 | Payment Notifications |
...