This space is deprecated and no longer supported. Please use the latest available version here.
Single Instant Payments
- Chris Michael
- Alexandros Dimitrakoudis
- Warren Handley
1. Description
This bank service request enables TPPs to initiate domestic Single Instant Payments (SIPs), with the Users' consent, from the Users' online payment accounts held at the LFI to a business or a personal beneficiary. The SIPs are to be executed immediately. TPPs are then further able to retrieve the status of the submitted payment order.
This user journey requires a Single Use Consent of type Single Instant Payment Consent.
1.1 Debtor and Creditor Segments
The scope of the SIP bank service initiation related to the segments of Debtors and Creditors is shown below:
Debtor | Creditor | ||||
|---|---|---|---|---|---|
Consumer | SME | Corporate | Consumer | SME | Corporate |
1.2 Single Instant Payment (SIP) - Example User Story
User Story
As a User (Consumer, SME or Corporate),
I want to provide my consent to a TPP to use my payment account for initiating a Single Instant Payment of a fixed amount to a domestic beneficiary account owned by a business or an individual,
so that I can pay the relevant beneficiary immediately.
2. User Journey
Users can initiate, by providing their consent to TPPs, a payment order to their LFIs to make a one-off single payment of a specific amount to a specific Creditor.
3. Customer Experience
A prototype of this journey showcasing a Single Instant Payment example can be seen here https://www.figma.com/proto/dGPBDz7AXnVmzUFdoUKk8Q/Prototypes-for-CBUAE-docs?page-id=6061%3A413&node-id=6424-3489&viewport=167%2C246%2C0.1&t=wV5rF0hiFZXPQrmq-1&scaling=scale-down&content-scaling=fixed&starting-point-node-id=6424%3A3489.
3.1 Standard Journey
This is applied in cases where:
a) the payment order submitted by TPPs to LFIs is incomplete, such as where the Users' account selection has not yet occurred. In these scenarios, the UAE Open Finance Standard considers that Multi-Factor Authentication (MFA) only needs to be obtained once, as part of the initial interaction between LFIs and the Users. The fact that Users have to then carry out account selection or provide other information does not invalidate the MFA just performed by the LFI. Equally, the display of the account balance by the LFI as part of the account selection process in the payment initiation journey SHOULD not require an additional application of MFA. The application of MFA is a matter for individual LFIs. This is also applicable to the CAAP journey as defined in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210797711.
b) the payment order submitted by TPPs to LFIs has all the require information for the payment, but, an additional step in the LFIs' journeys may be required to display supplementary information to Users, as defined in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800446/Common+Rules+and+Guidelines#22.-Supplementary-Information. LFIs MUST determine the situations where this supplementary information is required, under consideration that the principle of maintaining parity between the Open Finance journeys and LFIs' online channel journeys MUST be applied. Thus, if supplementary information is not provided within the LFIs' online channels directly to Users, then it MUST NOT be provided during an Open Finance Service Initiation request journey. LFI’s MUST also ensure that this information does not constitute an obstacle or additional check on the Consent provided by the User to the TPP.
3.1.1 User selects LFI at the TPP and account at the LFI
3.1.2 Rules & Guidelines
# | Step | Rules & Guidelines |
|---|---|---|
SIP-1 | Single Instant 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:
|
| Additional Consent Parameters TPPs MUST: 1.2 Set/clear the “Is Single Authorization” flag as appropriate (as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800446/Common+Rules+and+Guidelines#7.-Is-Single-Authorization-flag). 1.3 Set the Authorization Expiration DateTime (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). 1.4 Set/clear the “Is Pay By Account” flag as appropriate in the case the initiated payment is a payment at POS or e-commerce payment. 1.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: 1.6 Enable Users to provide explicit consent for the initiation of a SIP payment order from their online payment account held at their LFI as per the payment details specified in the payment Consent. | |
SIP-2 | Consent Staging | |
SIP-3 | Hand-off to LFI | Example wording to use: ‘We will securely transfer to YOUR LFI to authenticate and make the payment“. |
SIP-4 | Authentication | LFI Authentication Only LFIs MUST: 4.1 Enable Users to perform authentication with their LFIs, as per the following sections: 4.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 4.3 As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210797711. | ||
SIP-5 | Authorization | LFIs MUST: 5.1 Enable Users to authenticate using Multi-Factor Authentication (MFA) in order to review and authorize the Single Instant Payment (SIP) Consent. 5.2 Retrieve from the OFP the Single Instant Payment (SIP) Consent details staged by the TPP and present relevant details to the User. 5.3 Allow Users to select a payment account for the initiation of the Single Instant Payment (SIP), 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
5.4 Verify that the authorization status of the chosen payment account aligns with the “Is Single Authorization” flag specified by the TPPs, as per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800446/Common+Rules+and+Guidelines#7.-Is-Single-Authorization-flag. |
5.5 Display to Users the TPP Trading Name of the TPP that initiated the Single Instant Payment (SIP) Consent.
5.6 Present to Users the following minimum required information for authorizing the Single Instant Payment (SIP) Consent:
5.7 Request Users to authorize the Single Instant Payment (SIP) Consent, so that a single instant payment can be initiated. 5.8 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 Instant Payment (SIP) Consent. 5.9 Change the state of the Single Instant Payment (SIP) Consent from Awaiting Authorization to Authorized, when all Authorizers (one or more) have authorized the payment Consent. 5.10 Update the Single Instant Payment (SIP) Consent details stored in the OFP. | ||
OFP MUST: 5.11 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. 5.12 Confirm back to the LFIs that the Single Instant Payment (SIP) Consent details have been updated successfully. | ||
Multi-Authorization Journey Only | ||
SIP-6 | Hand-off back to the TPP | |
SIP-7 | Payment Initiation | TPPs MUST: 7.1 Submit to OFP the payment initiation requests with the same parameters as per the Payment Consent authorized by the User.
|
OFP MUST: 7.2 Allow the TPPs to submit the individual payment initiation request under the Payment Consent authorized by the User, without any additional MFA or authorization from the User. 7.3 Check that the received payment initiation request relates to a valid Payment Consent authorized by the User. The Consent MUST be in the Authorized state. The OFP MUST reject a payment initiation message related to a Payment Consent in a different state and respond back to the TPP with the appropriate error message/code. 7.4 Check the payment initiation request parameters against the authorized Payment Consent. All parameters MUST match exactly.
7.5 Send the SIP payment initiation request to the LFI for initiating an instant payment using the payment parameters included in the payment initiation request including:
| ||
LFIs MUST: 7.6 Trigger the payment initiation process for the payment Consent immediately after receiving the payment initiation request from the OFP.
7.7 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. 7.8 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. 7.9 Subject to successful BAU checking, validation and payment processing, proceed with the execution of the payment by either submitting the payment to the underlying payment rails or executing internally as Intra-bank payment. 7.10 Provide the OFP with all the available information in relation to the initiated payment instruction including the payment’s unique identifier payment Transaction ID. 7.11 Ensure that the Creditor Reference provided in the SIP payment initiation is made available to the Creditor’s account information in the case of intra-bank payments within the same LFI. | ||
OFP MUST: 7.12 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. 7.13 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. 7.14 Provide the TPP with all the available information in relation to the initiated Single Instant Payment (SIP) instruction including the payment’s unique identifier payment Transaction ID. | ||
SIP-8 | Payment Status Update | |
SIP-9 | Confirmation to User | |
SIP-10 | Payment Notifications |
3.1.3 Journey Variations
3.1.3.1 User selects account at the TPP & LFI provides Supplementary Information
3.1.3.2 User provides bank details at the TPP & LFI provides Supplementary Information
3.1.3.3 User selects account at the TPP & merchant is the user facing entity using a TPP for Open Finance payments
3.2 Fast-track Journey
In cases where all the information for a complete payment order (including the Users’ account details) is passed from TPPs to LFIs, once Users have been authenticated, the payment is initiated and Users MUST be directed back to the TPPs' domains without any further steps taking place in the LFIs' domains.
3.2.1 User selects account at the TPP
3.2.2 Rules & Guidelines
# | Step | Rules & Guidelines |
|---|---|---|
FTSIP-1 | Single Instant Payment Consent | |
FTSIP-2 | Consent Staging | |
FTSIP-3 | Hand-off to LFI | |
FTSIP-4 | Authentication | |
FTSIP-5 | Authorization | Fast-track Journey Only LFIs MUST: 5.1 Retrieve from the OFP the Single Instant Payment (SIP) Consent details staged by the TPP. 5.2 Display to Users the TPP Trading Name of the TPP that initiated the Single Instant Payment (SIP) Consent.
5.3 Display as minimum the Payment Amount, Currency and the Creditor Account Name to make the User aware of these details. These details MUST be displayed as part of the authentication journey on the LFIs’ Authentication screen without introducing additional confirmation screens (unless supplementary information is required). 5.4 Displaying the balance of users' payment account (not shown on the user journey) as part of the authentication process. If users are redirected to authenticate using an app, thereby fulfilling one authentication factor. In this scenario, showing the balance does not mandate additional strong customer authentication. However, displaying the balance in other cases is optional for LFIs. 5.5 Maintain consistent minimum and maximum payment limits, matching those available in the Standard Journey and their various other direct online platforms. 5.6 Inform Users about their “point of no return” for making the payment and that their payment will be made after authentication occurs. Example wording: ‘Authenticate to make payment”. For recognition based biometrics (e.g. Face ID) which can be more immediate, the biometric authentication should be invoked after a call to action to allow the User the ability to view the details of the payment that needs to be authorized. 5.7 Inform Users about accepting their T&Cs when proceeding from the “point of no return” for making the payment. 5.8 Enable Users to authenticate using Multi-Factor Authentication (MFA) in order to authorize the Single Instant Payment (SIP) Consent. 5.9 Ensure their authentication has no more than the number of steps that the User would experience when directly accessing the LFI channel. MFA Authentication MUST be the only action required by Users at the LFIs (unless supplementary information required as defined in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1dot1final/pages/210800446/Common+Rules+and+Guidelines#22.-Supplementary-Information). 5.10 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 Instant Payment (SIP) Consent. |
OFP MUST: 5.11 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. 5.12 Change the state of the Single Instant Payment (SIP) Consent from Awaiting Authorization to Authorized, when all Authorizers (one or more) have authorized the payment Consent. 5.13 Update the Single Instant Payment (SIP) Consent details stored in the OFP. 5.14 Confirm back to the LFIs that the Single Instant Payment (SIP) Consent details have been updated successfully. | ||
FTSIP-6 | Hand-off back to the TPP | |
FTSIP-7 | Payment Initiation | |
FTSIP-8 | Payment Status Update | |
FTSIP-9 | Confirmation to User | Fast-track Journey Only TPPs MUST: 9.1 Display to Users the information received from the LFIs. This information may include:
9.2 Display any of the following information regarding initiation and execution of the payment, if received by the LFIs:
|
FTSIP-10 | Payment Notifications |
3.2.3 Journey Variations
3.2.3.1 User provides bank details at the TPP
© CBUAE 2024
Open License and Contribution Agreement | Attribution Notice
Please try out our Advanced Search function.