...
# | Step | Rules & Guidelines |
|---|---|---|
IP-1 | Single IP details collection | TPPs MUST: Enable Users to provide the parameters related to the IP payment order they want to initiate. These parameters include:
|
International-FX & International Payments Only
| ||
IP-2 | Single IP Consent | Basic Consent Parameters TPPs MUST: 2.1 Enable Users to review the parameters related to the IP they need to consent to. These parameters include:
|
International-FX & International Payments Only
| ||
Additional Consent Parameters TPPs MUST: 2.2 Set/clear the ‘Is Single Authorization’ flag as appropriate (as per Common Rules and Guidelines | 7. Is Single Authorization flag). 2.3 Set the Authorization Expiration Date Time (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800446/Common+Rules+and+Guidelines#8.-Authorization-Expiration-DateTime) 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 (Please refer to https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800446/Common+Rules+and+Guidelines#18.-Multi-User-Authorization-Flow). 2.4 Set/clear the “Is Pay By Account” flag as appropriate in the case the initiated payment is a payments at POS or e-commerce payment. 2.5 Set the Risk Information Block (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800446/Common+Rules+and+Guidelines#9.-Risk-Information-Block) | ||
TPPs MUST: 2.6 Enable Users to provide explicit consent for the initiation of a single IP payment order from their online payment account held at their LFI as per the payment details specified in the payment Consent. | ||
IP-3 | Consent Staging | |
IP-4 | Hand-off to LFI | Example wording to use: ‘We will securely transfer to YOUR LFI to authorize and make the payment“. |
IP-5 | Authentication | LFI Authentication Only LFIs MUST: 5.1 Enable Users to perform authentication with their LFIs, as per the following sections: 5.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 5.3 As per Centralized Authentication and Authorization | ||
IP-6 | Authorization | LFIs MUST: 6.1 Enable Users to authenticate using Multi-Factor Authentication (MFA) in order to review and authorize the single IP Consent. 6.2 Retrieve from the OFP the single IP Consent details staged by the TPP and present relevant details to Users. 6.3 Allow Users to select a payment account for the initiation of the single IP, if this was not provided in the retrieved staged payment Consent details, as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800446/Common+Rules+and+Guidelines#12.-Payment-Account-Selection-at-LFI
6.4 Verify that the authorization status of the chosen payment account aligns with the TPPs' Is Single Authorization flag as per Common Rules and Guidelines | 7. Is Single Authorization flag. |
International-FX Only 6.5 Use the reference information provided in the IP Consent to identify the User's preferred forward FX rate agreement (e.g. future contract) related to User's account profile with the LFI, if this was included in the IP Consent. 6.6 Provide to the User the details of any forward FX rate agreement (e.g. future contract) they have in place in relation to the selected payment account and use this for the currency conversion required for the transaction. 6.7 Display to the User the details related to the Forward FX rate agreement, if applicable
6.8 Provide the same actual (deal) FX rate and charges as it would be offered to the User via the LFIs' other channels such as mobile or online banking, if the User has no FX agreement with the LFI. | ||
6.9 Display to Users the TPP Trading Name of the TPP that initiated the single IP Consent.
6.10 Present to Users the following minimum required information for authorizing the single IP payment Consent:
6.11 Refresh the Actual FX Rate if the remaining time has expired (if applicable) 6.12 Request Users to authorize the single IP payment Consent, so that a single IP payment can be initiated. 6.13 Provide Users the ability to cancel 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 single IP payment Consent. 6.14 Change the state of the single IP payment Consent from Awaiting Authorization to Authorized, when all Authorizers (one or more) have authorized the payment Consent. 6.15 Update the single IP payment Consent details stored in the OFP. | ||
OFP MUST: 6.16 Check the Authorization Time Window is valid as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800446/Common+Rules+and+Guidelines#19.-Check-Authorization-Time-Window. 6.17 Confirm back to the LFIs that the single IP payment Consent details have been updated successfully. | ||
Multi-Authorization Journey Only | ||
IP-7 | Hand-off back to the TPP | |
IP-8 | Payment Initiation | TPPs MUST: 8.1 Submit to OFP the IP payment initiation requests with the same parameters as per the IP Payment Consents authorized by Users. 8.2 Submit to OFP the IP payment initiation request immediately after they receive the IP Payment Consent authorization confirmation. This is required in the case that there is FX conversion related to the International Payment AND the FX rate included in the IP Payment Consent was the actual rate (i.e. deal rate) and not indicative rate or a fixed rate related to a future contract agreement. The IP payment initiation request MUST be received by the LFI within the https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800530/Limits+and+Constants#Actual-FX-Rate-SLA. 8.3 Impose a payment limit of 15000 AED for all first-time payments made to a new beneficiary.
|
OFP MUST: 8.3 Allow the TPPs to submit the individual payment initiation requests under the Payment Consents authorized by Users, without any additional MFA or authorization from Users. 8.4 Check that the received payment initiation request relates to a valid IP Payment Consent authorized by the User. The Consent MUST be in the Authorized state. The OFP MUST reject an IP payment initiation message related to an IP Payment Consent in a different state and respond back to the TPP with the appropriate error message/code. 8.5 Check the payment initiation request parameters against the authorized IP Payment Consent. All parameters MUST match exactly.
8.6 Send the IP payment initiation request to the LFI for initiating a single International Payment using the payment parameters included in the payment initiation request including:
8.7 Submit to the LFI the IP payment initiation request immediately after they receive the IP Payment request from the TPP. This is required in the case that there is FX conversion related to the International Payment AND the FX rate included in the IP Payment Consent was the actual rate (i.e. deal rate) and not indicative rate or a fixed rate related to a future contract agreement. The IP payment initiation request MUST be received by the LFI within the https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800530/Limits+and+Constants#Actual-FX-Rate-SLA. Note: In cases where the IP Payment request has not been received within the https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800530/Limits+and+Constants#Actual-FX-Rate-SLA and the FX in the authorized IP Consent was not related to a future contract rate, the LFI is expected to use a different FX rate for the transaction. This rate will be provided back to the TPP in the IP Payment response message. This scenario can also occur in the exceptional circumstances of the IP Consent authorization being provided to the LFI just at the point of the FX deal cut-off time. This is more prominent to occur in cases where the LFI is not using the CLS system. Similarly, the same scenario can occur in situations where the IP Consent was authorized at the cut-off time of the underlying payment system causing the payment to be executed in the next available window on the following date with a different value date. | ||
LFIs MUST: 8.8 Trigger the payment initiation process for the payment Consent immediately after receiving the payment initiation request from the OFP.
8.9 Additionally 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. LFIs MUST send an appropriate error response to the OFP in case the payment is rejected due to violating any of these limits. 8.10 Reject the payment initiation if the payment account selected for the payment has insufficient funds. The OFP MUST be notified about this rejection with an appropriate error message. 8.11 Subject to successful BAU checking, validation and payment processing, proceed with the execution of the payment by submitting the payment to the underlying payment rails. 8.12 Provide the OFP with all the available information in relation to the initiated payment instruction including the payment’s unique identifier Payment Transaction ID. | ||
OFP MUST: 8.13 Send an appropriate error response to the TPPs in case the payment is rejected due to violating any of the LFIs' BAU payment accounts checks or limits. 8.14 Send to the TPP the appropriate error message in case the payment initiation was rejected by the LFI due to insufficient funds in the selected payment account. 8.15 Provide the TPP with all the available information in relation to the initiated single IP instruction including the payment’s unique identifier Payment Transaction ID. | ||
IP-9 | Payment Status Update | |
IP-10 | Hand-off back to the TPP | |
IP-11 | Confirmation to User | |
IP-12 | Payment Notifications |
...