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.
The SIP scope is targeted to domestic payee accounts (i.e. payee accounts offered by LFIs located in UAE) and payments in local currency as used by the local payment systems infrastructure for domestic payments.
This user journey requires a Single Use Consent of type Single Instant Payment Consent.
1.1 Payer and Payee Segments
The scope of the SIP bank service initiation related to the segments of payers and payees is shown below:
Payer | Payee | ||||
|---|---|---|---|---|---|
Consumers | SME | Corporates | Consumers | SME | Corporates |
|
|
|
|
|
|
1.2 Single Instant Payment (SIP) - Example User Story
User Story
As a User (Consumer, Business 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 payee.
2.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 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.
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. 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. Wireframes
3.1 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:
Note: Depending on the use case, the Payee details may not be displayed to Users in full. However, these still need to be part of the payment Consent request sent by the TPP.
|
Additional Consent Parameters TPPs MUST: 1.2 Set the Accepted Authorization Type (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160478#7.-Accepted-Authorization-Type). 1.3 Set the Authorization Time Window (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160478#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 (Please refer to https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160478#18.-Multi-User-Authorization-Flow).
1.4 Set the Risk Information Block (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160478#9.-Risk-Information-Block) | ||
TPPs MUST: 1.5 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 | As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160478#10.-Consent-Staging |
SIP-3 | Hand-off to LFI | As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160478#11.-Hand-off-to-LFI Example wording to use: ‘We will securely transfer to YOUR LFI to authenticate and make the payment“. |
SIP-4 | Authentication | As per the following sections: |
SIP-5 | Confirmation/ Authorization | 1. Standard Journey LFIs MUST: 5.1.1 Enable the account selection process as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160478#12.-Payment-Account-Selection-at-LFI 5.1.2 NOT allow Users to select a payment account from their list of available payment accounts that has insufficient funds for the SIP payment initiation. This only applies in case Users do not select their payment account when providing their Consent to TPPs. 5.1.3 Present to Users all the details in relation to the SIP payment Consent. 5.1.4 Present Users with the charges, if any, that will be applied for making the SIP payment related to the payment Consent. LFIs MUST include both the bank charges and the VAT, stated separately, if applicable. 5.1.5 Request Users to authorize the SIP payment Consent, so that a single instant payment can be initiated. 5.1.6 Present to Users the following minimum required information for authorizing the SIP payment Consent:
5.1.7 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 TPP and reject the SIP payment Consent. 5.1.8 Change the state of the payment Consent from Awaiting Authorization to Authorized, if the User authorized the SIP payment Consent and is the only required authorizer. |
2. Multi-Authorization Journey Only 5.2.1 As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160478#18.-Multi-User-Authorization-Flow | ||
SIP-6 | Payment Initiation | LFIs MUST: 6.1 Trigger the payment initiation process for the payment Consent immediately after the payment Consent has been fully authorized by all required authorizers (one or more). 6.2 Additionally apply all existing BAU payment account controls and limits such as single transaction value limit, total transaction value limit, 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 TPP in case the payment is rejected due to violating any of these limits. 6.3 Reject the payment initiation if the payment account identification was part of the payment Consent and the payment account has insufficient funds. The TPP MUST be notified about this rejection with an appropriate error message. 6.4 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 On-us payment. 6.5 Provide the TPP with all the available information in relation to the initiated payment instruction including the payment’s unique identifier Payment Transaction ID. The format of the Payment Transaction ID can be found in Payment API Specification, Retrieve a Payment, 6.6 Ensure that the Payment Reference provided in the payment Consent is made available to the Beneficiary’s account information in the case of “On-us” payments within the same LFI. |
SIP-7 | Hand-off back to the TPP | |
SIP-8 | Payment Status Update | |
SIP-9 | Confirmation to User | 1. Standard Journey 9.1.1 As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160478#16.-Confirmation-to-PSU |
SIP-10 | Payment Notifications | 10.1 As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160478#17.-Payment-Notifications |