| Expand | ||||
|---|---|---|---|---|
| ||||
|
...
# | Step | Rules & Guidelines |
|---|---|---|
MPCS-1 | Multi-Payments Consent | Basic Consent Parameters TPPs MUST: 1.1 Enable Users to provide and review the parameters related to the initiation of a series of Multi-Payments they need to consent to. These parameters include:
Note: Depending on the use case the Payee details may not be displayed to the User in full. However, these need to be part of the payment request sent by the TPP to the LFI.
|
Fixed Recurring Payments (FRPs) Consent
| ||
Variable Recurring Payments (VRPs) - Fixed On-demand Consent
| ||
Variable Recurring Payments (VRPs) - Variable Recurring Consent
| ||
Variable Recurring Payments (VRPs) - Variable On-demand Consent
| ||
Variable Recurring Payments (VRPs) - Variable-defined Consent
| ||
Additional Consent Parameters 1.2 Set the Accepted Authorization Type (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft5/pages/109415230/Common+Rules+and+Guidelines#7.-Accepted-Authorization-Type). 1.3 Set the Authorization Time Window (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft5/pages/109415230/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.
1.4 Set the Risk Information Block (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft5/pages/109415230/Common+Rules+and+Guidelines#9.-Risk-Information-Block) | ||
1.5 Enable Users to provide explicit consent for the initiation of a series of future Multi-Payments of fixed or variable amounts based on a fixed periodic schedule or a variable schedule from their online payment account held at their LFI as per the payment parameters specified in the consent. | ||
Balance Check Permission 1.6 Optionally request permission to check the balance of the payment account before initiating a payment. | ||
MPCS-2 | Consent Staging | |
MPCS-3 | Hand-off to LFI | Example wording to use: ‘We will securely transfer to YOUR LFI to authenticate and authorize your payments setup“. |
MPCS-4 | Authentication | LFI Authentication Only As per the following sections: |
Centralized Authentication and Authorization (Federated) Only | ||
MPCS-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 payment Consent. 5.2 Retrieve from the OFP the 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 multi-payments, if this was not provided in the retrieved staged Payment Consent details as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft5/pages/109415230/Common+Rules+and+Guidelines#12.-Payment-Account-Selection-at-LFI
5.4 Only present additional screens, if necessary to allow the validation and confirmation of the payment Consent (e.g., Beneficiary adding & activation and Proxy lookup). 5.5 NOT earmark (i.e. block) any funds related to the payment Consent in the Users' payment account at the point of Consent authorization. 5.6 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/standardsv1draft5/pages/109415230/Common+Rules+and+Guidelines#13.-Check-Accepted-Authorization-Type. 5.7 Add to the payment Consent the IBAN of the Payee returned by the Proxy resolution process, if the multi-payments Consent was submitted for User Authorization with one or more Beneficiaries using a Proxy as the Payee Identification. In these cases, the Consent is thereafter tied to the IBAN(s) of the Payee(s) rather than the proxies themselves. This will allow the future multi-payments to be initiated to these IBAN(s) even if the Payee(s) change proxy between the time of the Consent and the initiation of multi-payments related to the Consent.
5.8 Present to Users the following minimum required information for authorizing the long-lived payments Consent:
5.9 Request Users to authorize the Multi-payments Consent, so that TPP can initiate payments from the payment account.
5.10 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 Multi-payments Consent. 5.11 Check the Authorization Time window is valid as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft5/pages/109415230/Common+Rules+and+Guidelines#20.-Check-Authorization-Time-Window 5.12 Change the state of the payment Consent from Awaiting Authorization to Authorized when all Authorizers (one or more) have authorized the payment Consent. 5.13 Update the payment Consent details stored in the OFP with all the information included in the payment Consent authorized by the User. |
OFP MUST: 5.14 Confirm back to the LFIs that the payment Consent details have been updated successfully. 5.15 Start tracking the Consent Control Parameters for the Control Period at the Control Period Start Date, if provided, or the Consent creation Date otherwise. The Control Period starts from 00:00:00 of the day and ends at 23:59:59 of the Control Period end day, calculated based on the Control Period type as defined in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft5/pages/109413991/Multi-Payments#8.3.2-VRP-Consent-Control-Period-%26-Start-Date. 5.16 Return back to the TPP in the payment Consent response the IBAN(s) of the Payee identification(s) returned by the Proxy resolution, if the payment Consent was submitted for User Authorization with one or more Payees using a Proxy as the Payee Identification. | ||
Multi-Authorization Journey Only | ||
MPCS-6 | Hand-off back to the TPP | |
MPCS-7 | Confirmation to User |
4. Balance Check
...
3.2 COP Service for Multi-Payments Consent
...
#
...
Step
...
Rules & Guidelines
...
MPBAL-1
...
Balance Check
TPPs MUST:
3.2.1 COP Service for fixed or variable-defined Beneficiaries
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
TTPs MUST: 3.2.1.1 Be able to |
...
use the COP Service as defined in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft5/pages/109413626/Single+Instant+Payment#3.3-Using-Confirmation-of-Payee-(COP). |
3.2.2 COP Service for variable Beneficiaries
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
TTPs MUST: 3.2.2.1 Verify variable beneficiaries related to a long-live multi-payments consent either through:
|
4. Balance Check
Prior to Payment Initiation, TPPs can optionally check the balance of the account for sufficient funds for the payment and display the balance to Users, subjec to have received Balance Check permission during the Multi-Payments Consent setup.
# | Step | Rules & Guidelines |
|---|---|---|
MPBAL-1 | Balance Check | TPPs MUST: 1.1 Be able to request balance information using the authorized Multi-payment Consent before initiating a payment. 1.2 Use this capability only in relation to the Payment initiation steps to follow. 1.3 NOT use this capability as an alternative for Account Information Service, for example, to satisfy use cases like Personal Finance Manager (PFM), where the account balance is being refreshed periodically. 1.4 Make the Balance Check request not earlier than 24 hours from when a scheduled payment is to be initiated. |
MPBAL-2 | Balance Check Request Processing | LFIs MUST: 2.1 Provide the OFP with the the information related to the balance of the User's account, which was used for authorizing the Multi-Payment Consent. This information MUST be the same information as defined under the Balances permission in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft5/pages/109415009/Customer+Data#6.3-Data-Cluster-Structure-%26-Language. |
OFP MUST: 2.2 Provide TPPs with all the available information in relation to the Balance Check request. 2.3 Send an appropriate error response to TPPs in case the Balance Check request was not successful. |
...
| Info |
|---|
Note: The parameters of the long-lived Multi-Payments Consent that Users are able to update depend on the use case and the business requirements of each TPP. There may be scenarios where the TPPs are fine to allow users Users to update one or more of the Consent parameters and other scenarios where Users are not allowed to make any changes to the Consent ParametsParameters. In any case, Users are always able to revoke their Consent. |
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
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:
|
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
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:
|
8.4 Consent Expiration Date & Time
...