Section

Subsection

Description

Action

https://openfinanceuae.atlassian.net/wiki/x/UAqTFQ

Across the multi-payment standards, several terms have been used to the multi-payment arrangements types, including Variable Recurring Payments (VRPs) and Fixed Recurring Payments (FRPs).

This has created confusion for implementers because the payment types supported in the API specification are defined using a different set of enumerations (Pushed Authorization Request Endpoint OpenAPI ):

• FixedPeriodicSchedule

• VariablePeriodicSchedule

• FixedOnDemand

• VariableOnDemand

• FixedDefinedSchedule

• VariableDefinedSchedule

As a result, confusion and uncertainty have been introduced to implementers when mapping the terminology used in the standards (e.g., VRP/FRP) to the actual payment type enums supported by the APIs and their associated behavioral rules.

Guidance has been provided to clarify how the terminology used in the standards maps to the specific Payment Types defined in the API specification.

See:
Standards v2.0 - final - errata4 (Multi-Payment Consent Control Parameters Guidance)

This guidance defines the relationship between the previously used terms (e.g., VRP and FRP) and the exact payment type enums supported by the APIs.

https://openfinanceuae.atlassian.net/wiki/x/UAqTFQ

Multi-Payments

The descriptions of the Control Parameters that the OFP enforces at the point of staging a consent request (Pushed Authorization Request Endpoint OpenAPI ) do not accurately reflect the logic implemented by the OFP. As currently written, the descriptions leave interpretation gaps for the various payment types aswell as gaps regarding which behaviors must be implemented by the TPP and which controls are technically enforced by the OFP.

Fixed Recurring Payments (FRPs) Consent

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

Periodic Payment Schedule (as per
Multi-Payments | 8.2.1 Periodic Payment Schedule
)

Consent Expiration Date & Time (as per
Multi-Payments | 8.4.1 Consent Expiration for FRPs (Fixed Recurring Consent))

Variable Recurring Payments (VRPs) - Fixed On-demand Consent

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

Consent Controls Parameters (as per
Multi-Payments | 8.3 VRP Consent Control Parameters
) as follows:

Maximum Cumulative Value of all payment initiations for the entire Consent validity period

Maximum Cumulative Number of all payment initiations for the entire Consent validity period

Maximum Cumulative Value of all payment initiations per Consent Control Period

Maximum Cumulative Number of all payment initiations per Consent Control Period

Consent Control Period & Start Date (as per
Multi-Payments | 8.3.2 VRP Consent Control Period & Start Date
)

Consent Expiration Date & Time (as per
Multi-Payments | 8.4.3 Consent Expiration for Unscheduled VRPs (Fixed and Variable On demand Con...
)

Variable Recurring Payments (VRPs) - Variable Recurring Consent

Periodic Payment Schedule (as per
Multi-Payments | 8.2.1 Periodic Payment Schedule)

Consent Controls Parameters (as per
Multi-Payments | 8.3 VRP Consent Control Parameters
) as follows:

Maximum Payment Amount per payment initiation

Maximum Cumulative Value of all payment initiations for the entire Consent validity period

Maximum Cumulative Number of all payment initiations for the entire Consent validity period

Consent Expiration Date & Time (as per
Multi-Payments | 8.4.2 Consent Expiration for Periodic Scheduled VRPs (Variable Recurring Consen...)

Variable Recurring Payments (VRPs) - Variable On-demand Consent

Consent Controls Parameters (as per
Multi-Payments | 8.3 VRP Consent Control Parameters
) as follows:

Maximum Payment Amount per payment initiation

Maximum Cumulative Value of all payment initiations for the entire Consent validity period

Maximum Cumulative Number of all payment initiations for the entire Consent validity period

Maximum Cumulative Value of all payment initiations per Consent Control Period

Maximum Cumulative Number of all payment initiations per Consent Control Period

Consent Control Period & Start Date (as per
Multi-Payments | 8.3.2 VRP Consent Control Period & Start Date)

Consent Expiration Date & Time (as per
Multi-Payments | 8.4.3 Consent Expiration for Unscheduled VRPs (Fixed and Variable On demand Con...)

Variable Recurring Payments (VRPs) - Fixed-defined Consent & Variable-defined Consent

Fixed-defined Payments & Variable-defined Payments & Schedule (as per
Multi-Payments | 8.2.3 Fixed defined & Variable defined Payments & Schedule)

Consent Expiration Date & Time (as per
Multi-Payments | 8.4.4 Consent Expiration for Fixed defined & Variable defined Consent)

For each Multi-Payment type described within this section, the rules regarding the specific required control parameters are replaced with Standards v2.0 - final - errata4 (Multi-Payment Consent Control Parameters Guidance)

https://openfinanceuae.atlassian.net/wiki/x/UAqTFQ

Multi-Payments

The descriptions of the Control Parameters that the OFP enforces at the point of staging a consent request (Pushed Authorization Request Endpoint OpenAPI ) do not accurately reflect the logic implemented by the OFP. As currently written, the descriptions leave interpretation gaps for the various payment types aswell as gaps regarding which behaviors must be implemented by the TPP and which controls are technically enforced by the OFP.

VRPs Only

TPPs MUST:

1.12 NOT submit any payment initiation requests of amount more than the maximum payment value per payment initiation, if specified in the long-lived Payment Consent for VRPs.

1.13 Keep track of the cumulative value of all payment initiations and NOT submit any VRP payment initiation requests that will result in exceeding the maximum limit, if specified in the long-lived Payment Consent for the VRPs.

1.14 Keep track of the maximum cumulative number of all payment initiation and NOT submit any VRP payment initiation requests that will result in exceeding the maximum limit, if specified in the long-lived Payment Consent for the VRPs.

1.15 Keep track of the cumulative payment value of all payment initiations per time window and NOT submit any VRP payment initiation requests that will result in exceeding the maximum limit, if specified in the long-lived Payment Consent for the VRPs.

1.16 Keep track of the cumulative payment volume of payment initiations per time window and NOT submit any VRP payment initiation requests that will result in exceeding the maximum limit, if specified in the long-lived Payment Consent for the VRPs.

Required consent control parameters as outlined within this section are inaccurate as aligned with expected requirements and the Open Finance APIs

FRPs Only

OFP MUST:

2.4 Check the Fixed Recurring Payment initiation request parameters against the Fixed Recurring Payment Consent. More specifically, the OFP MUST:

• Check the cumulative Total Number of payment initiations including the submitted payment initiation request is less than the Total Number of Payments as defined in the authorized long-lived Fixed Recurring Payment Consent.

2.5 Increment the cumulative total number of payments after the payment has been successfully executed and received payment status confirmation from the creditor Bank. The initial value of this parameter should be zero for each authorized Fixed Recurring Payment Consent.

Required consent control parameters as outlined within this section are inaccurate as aligned with expected requirements and the Open Finance APIs

VRPs Only

OFP MUST:

2.7 Check the payment initiation request parameters against the authorized long-lived VRP Payment Consent. More specifically, the OFP MUST check the following:

• The cumulative Total Value of all payment initiations including the amount of the submitted payment initiation request is less or equal to the Maximum Cumulative Value of all payment initiations defined in the authorized long-lived Payment Consent (For Variable Recurring and Variable On-demand Consent types).

• The cumulative Total Number of all payment initiations including the submitted payment initiation request is less or equal to the Maximum Cumulative Number of all payment initiations defined in the authorized long-lived Payment Consent (For Variable Recurring Consent and Variable On-demand Consent types).

• The cumulative Total Value of all payment initiations per Consent Control Period including the amount of the submitted payment initiation request is less or equal to the Maximum Cumulative Value of all payment initiations within the Consent Control Period as defined in the authorized long-lived Payment Consent (For Variable Recurring Consent and Variable On-demand Consent types).

• The cumulative Total Number of all payment initiations per Consent Control Period including the submitted payment initiation request is less or equal to the Maximum Cumulative Number all payment initiations within the Consent Control Period as defined in the authorized long-lived Payment Consent (For Variable Recurring Consent and Variable On-demand Consent types).

• 2.9 Increment the cumulative Total Number and the cumulative Total Value of payments under the VRP Consent after the payment resource has been created and it is in ‘Pending’ status and has not been rejected. This will prevent multiple payments being initiated that could exceed the Maximum values of the respective Consent Control parameters. The initial value of the cumulative Total Number and the cumulative Total Value of payments should be zero for each authorized VRP Consent.

• 2.10 Increment the cumulative Total Number and the cumulative Total Value of all payment initiations per Control Period after the payment resource has been created and it is in ‘Pending’ status and has not been rejected. This will prevent multiple payments being initiated that could exceed the Maximum values of the respective Consent Control parameters. The cumulative Total Number and the cumulative Total Value of all payment initiations per Control Period are reset to zero when a new Consent Control Period starts at 00:00:00 of the first day of the Control Period.

For each Multi-payment type described within this section, the rules regarding the specific required control parameters are replaced with Standards v2.0 - final - errata4 (Multi-Payment Consent Control Parameters Guidance)

https://openfinanceuae.atlassian.net/wiki/x/UAqTFQ

Multi-Payments

The descriptions of the Control Parameters that the OFP enforces at the point of staging a consent request (Pushed Authorization Request Endpoint OpenAPI ) do not accurately reflect the logic implemented by the OFP. As currently written, the descriptions leave interpretation gaps for the various payment types aswell as gaps regarding which behaviors must be implemented by the TPP and which controls are technically enforced by the OFP.

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 Limits and Constants.

• 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 Limits and Constants.

• 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 Limits and Constants.

• The Consent Control Period Type & Start Date (as defined in Multi-Payments)

• 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 Limits and Constants.

• 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 Limits and Constants.

For each Multi-payment type described within this Section, the rules regarding the specific required control parameters are replaced with Standards v2.0 - final - errata4 (Multi-Payment Consent Control Parameters Guidance)

Fixed Recurring Payments (FRPs)

Fixed Recurring

Periodic (Recurring) Payments

Fixed Periodic Payments (FixedPeriodicSchedule)

Variable Recurring Payments (VRPs)

Variable Recurring

Variable Periodic Payments (VariablePeriodicSchedule)

Fixed On-demand

On-Demand Payments

Fixed On-Demand Payments (FixedOnDemand)

Variable On-demand

Variable On-Demand Payments (VariableOnDemand)

Fixed-defined

Defined Payments

Fixed Defined Payments (FixedDefinedSchedule)

Variable-defined

Variable Defined Payments (VariableDefinedSchedule)

Combined Payments (Recurring Payments with a One-Time Setup)

Combined

Combined Payments (Recurring Payments with a One-Time Setup)

Combined Payment - Single Instant Payment & Multi Payment

Not applicable

Was a non-multi-payment type

Single Future Dated Payment

Single Future Dated Payment

MaximumCumulativeValueOfPayments

• This optional control parameter defines the maximum cumulative value of payments that may be initiated over the lifetime of the consent. This control limit is independent of:

  • the maximum cumulative number of payments, where defined

  • any maximum cumulative value of payments per period

• As a result, it does not need to match the calculated total derived from the number of periods multiplied by the maximum cumulative value per period.

MaximumCumulativeNumberOfPayments

• This optional control parameter defines the maximum cumulative number of payments that may be initiated over the lifetime of the consent. This control limit is independent of:

  • the maximum cumulative value of payments, where defined

  • any maximum cumulative number of payments per period

• As a result, it does not need to match the calculated total derived from the number of periods multiplied by the maximum cumulative number per period.

PeriodType

• A mandatory parameter that defines the length of the recurring period to which the maximum cumulative value of payments per period and/or the maximum cumulative number of payments per period applies.

• The supported period options are Day, Week, Month, and Year.

PeriodStartDate

• A mandatory parameter that defines when the weekly and monthly recurring period starts.

• When the PeriodType is Day or Year, this value defines the date from which payments may be initiated.

Controls.MaximumIndividualAmount

• When provided, this parameter defines the maximum individual payment amount permitted over the lifetime of the consent.

• The payment amount specified in a payment initiation request MUST be equal to or lower than this value.

• Also see: Common Rules and Guidelines

Controls.MaximumCumulativeValueOfPaymentsPerPeriod

• When provided, this parameter defines the maximum cumulative value of payments that may be initiated within the defined period.

• This control limit is independent of the maximum cumulative number of payments per period, where defined, and MUST be greater than the MaximumIndividualAmount when that parameter is provided.

Controls.MaximumCumulativeNumberOfPaymentsPerPeriod

• When provided, this parameter defines the maximum cumulative number of payments that may be initiated within the defined period.

• This control limit is independent of the maximum cumulative value of payments per period, where defined.

ExpirationDateTime

TPPs MUST either:

• allow Users to manually enter or select the date at which the Variable On Demand consent will end, or

• pre-populate the value for Users based on the specific business case and the receiving beneficiary party.

MaximumCumulativeValueOfPayments

• This optional control parameter defines the maximum cumulative value of payments that may be initiated over the lifetime of the consent. This control limit is independent of:

  • the maximum cumulative number of payments, where defined

  • any maximum cumulative value of payments per period

• As a result, it does not need to match the calculated total derived from the number of periods multiplied by the maximum cumulative value per period.

MaximumCumulativeNumberOfPayments

• This optional control parameter defines the maximum cumulative number of payments that may be initiated over the lifetime of the consent. This control limit is independent of:

  • the maximum cumulative value of payments, where defined

  • any maximum cumulative number of payments per period

• As a result, it does not need to match the calculated total derived from the number of periods multiplied by the maximum cumulative number per period.

PeriodType

A mandatory parameter that defines the length of the recurring period to which the maximum cumulative value of payments per period and/or the maximum cumulative number of payments per period applies. The supported period options are Day, Week, Month, and Year.

PeriodStartDate

• A mandatory parameter that defines when the weekly and monthly recurring period starts. When the PeriodType is Day or Year, this value defines the date from which payments may be initiated.

Amount

• A mandatory parameter that defines the fixed payment amount to be initiated when requested.

• See: Common Rules and Guidelines

Controls.MaximumCumulativeValueOfPaymentsPerPeriod

• When provided, this parameter defines the maximum cumulative value of payments that may be initiated within the defined period.

• This control limit is independent of the maximum cumulative number of payments per period, where defined, and MUST be greater than the Amount when that parameter is provided.

Controls.MaximumCumulativeNumberOfPaymentsPerPeriod

• When provided, this parameter defines the maximum cumulative number of payments that may be initiated within the defined period.

• This control limit is independent of the maximum cumulative value of payments per period, where defined.

ExpirationDateTime

TPPs MUST either:

• allow Users to manually enter or select the date at which the Fixed On Demand consent will end, or

• pre-populate the value for Users based on the specific business case and the receiving beneficiary party.

MaximumCumulativeValueOfPayments

• Although this control parameter may be provided, the periodic schedule parameters are the primary control mechanism.

• When this parameter is provided, its value MUST equal the maximum individual amount multiplied by the number of payments to be initiated over the lifetime of the consent.

MaximumCumulativeNumberOfPayments

• As this mandatory, TPPs MUST calculate and provide the total number of payments that will be initiated over the schedule.