Page Comparison

TTPs MUST:

8.2.3.1 Either allow Users to specify the below set of parameters or pre-populate them for the Users based on the specific use-case or the requirements of their receiving beneficiary customer:

A. For Fixed-defined Payments

• Fixed Predefined Payment Schedule: This is a list of pre-defined pairs of dates and payment amounts. TPPs MUST use this schedule and for each pair of (date, amount) a payment of the associated amount will be initiated on the specific date. For example:

  • For a Fixed Predefined Payment Schedule of { (1st Jan-24, AED 10), (15th Apr-24, AED 50), (25 Sep-24, AED 1000), } the following payments will be initiated by the TPP:

    • Payment of 10 AED on the 1st Jan-24

    • Payment of 50 AED on the 15th Apr-24

    • Payment of 1000 AED on the 25th Sep-24

B. For Variable-defined Payments

• Variable Predefined Payment Schedule: This is a list of pre-defined pairs of dates and payment amount limits. TPPs MUST use this schedule and for each pair of (date, amount limit) a payment of amount less or equal to the associated amount limit, will be initiated on the specific date. For example:

  • For a Variable Predefined Payment Schedule of { (1st Jan-24, AED 10), (15th Apr-24, AED 50), (25 Sep-24, AED 1000), } the following payments will be initiated by the TPP:

    • Payment of 5 AED on the 1st Jan-24 - (i.e. 5 AED < 10 AED)

    • Payment of 25 AED on the 15th Apr-24 - (i.e. 25 AED < 50 AED)

    • Payment of 999 AED on the 25th Sep-24 - (i.e. 999 AED < 1000 AED)

8.2.3.2 Limit the entries in the Fixed Predefined Payment Schedule & Variable Predefined Payment Schedule to https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/edit-v2/210800530#Max-Fixed-defined-%26-Variable-defined-Schedule-Entries.

8.2.3.3 Limit each date in the Fixed Predefined Payment Schedule & Variable Predefined Payment Schedule to be less or equal to https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800530/Limits+and+Constants#Max-Consent-Validity-Period.

8.2.3.4 Limit each payment amount or amount limit in the Fixed Predefined Payment Schedule & Variable Predefined Payment Schedule to be less or equal to https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/edit-v2/210800530#Max-Fixed-defined-%26-Variable-defined-Payment-Amount.

8.2.3.5 Allow entries in the Fixed-defined & Variable-defined Payment Schedule to have the same date or payment amount or amount limit.
8.2.3.6 Enforce different dates in each entry of a Fixed-defined & Variable-defined Payment Schedule

TTPs MUST:

 8.3.1 Either allow Users to specify the below set of parameters or pre-populate them for the Users based on the specific use-case or the requirements of their receiving beneficiary customer:

• The Maximum Payment Amount per payment initiation: This is required if the payment amount is variable instead of fixed. This is related to VRPs that use the Long-lived Consent of the type Variable Recurring Consent and Variable On-demand Consent. This is the maximum amount a variable payment related to the Consent can take. All payment amounts must be smaller or equal to this value. This is limited to https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800530/Limits+and+Constants#Max-VRP-Payment-Amount.

• The Maximum Cumulative Value of all payment initiations for the entire Consent validity period. This is related to all types of VRP payments. Every payment amount related to the Consent that is successfully initiated and executed is added to the Total Cumulative Value of the Consent which cannot exceed the Maximum Cumulative Value agreed with the User at the point of consent. Any payment amount resulting to a Total Cumulative Value exceeding the Maximum MUST be rejected by the TPP and the LFI. This is limited to https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800530/Limits+and+Constants#Max-VRP-Consent-Cumulative-Value.

• The Maximum Cumulative Number of all payment initiations for the entire Consent validity period. This is related to all types of VRP payments. Every payment initiation related to the Consent that is successfully initiated and executed is added to the Total Cumulative Number of payment initiations of the Consent which cannot exceed the Maximum Cumulative Number agreed with the User at the point of consent. Any payment initiation resulting to the Total Cumulative Number of initiations exceeding the Maximum MUST be rejected by the TPP and the LFI. This is limited to https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800530/Limits+and+Constants#Max-VRP-Consent-Cumulative-Payments.

• The Consent Control Period Type & Start Date (as defined in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210798542/Multi-Payments#8.3.2-VRP-Consent-Control-Period-%26-Start-Date)

• The Maximum Cumulative Value of all payment initiations per Consent Control Period. This is related to VRPs that use the Long-lived consent of the type Variable On-demand Consent and Fixed On-demand Consent. During each repeating Consent Control Period, the Total Cumulative Value of all payment initiations under Variable On-demand Consent and Fixed On-demand Consent MUST NOT exceed the Maximum Cumulative Value agreed by the User during the Consent. The Total Cumulative Value is reset on every new Consent Control Period. This is limited to https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800530/Limits+and+Constants#Max-VRP-Cumulative-Value-per-Control-Period.

• The Maximum Cumulative Number of all payment initiations per Consent Control Period. This is related to VRPs that use the Long-lived consent of the type Variable On-demand Consent and Fixed On-demand Consent. During each repeating Consent Control Period, the Total Cumulative Number of all payment initiations under Variable On-demand Consent and Fixed On-demand Consent MUST NOT exceed the Maximum Cumulative Number agreed by the User during the Consent. The Total Cumulative Number of payment initiations is reset on every new Consent Control Period. This is limited to https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800530/Limits+and+Constants#Max-VRP-Cumulative-Payments-per-Control-Period.

TTPs MUST:

8.3.2.1 Either allow Users to manually enter/specify the below parameters or pre-populate them for Users based on the specific use-case or the requirements of their receiving beneficiary customer:

• Control Period: This is a rolling Period as defined in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210798542/Multi-Payments#8.2.2-Period-Type-%26-Start-Date. During each rolling Period specific Consent Control limits are applied. The rolling Control Period may occur one or more times during the Long-lived Consent duration depending on the Period Type and the Control Period Start Date. For example, for a Consent of expiry after 30 days, a Consent Control Period of 1 Day may be repeating up to 30 times, depending on the Period Start Date. Similarly, for a Consent of expiry after 1 year a Control Period of 1 Week may be repeating up to 52 times depending on the Period Start Date.

• Control Period Start Date: This is the first date of the rolling Control Period, as defined in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210798542/Multi-Payments#8.2.2-Period-Type-%26-Start-Date. The Control Period Start Date is optional and if not set by TPPs, the OFP MUST align the starting point of the Control Period to the Consent creation Date. The Control Period Start Date, if specified, MUST take values of dates in the future. This capability allows Users to select a day in the future when they want to start initiating Fixed or Variable On-Demand payments instead of from the consent creation date. This date MUST less than https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210798542/Multi-Payments#8.4.3-Consent-Expiration-for-Unscheduled-VRPs-(Fixed-and-Variable-On-demand-Consent).