Consumers

SME

Corporates

Consumers

SME

Corporates

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:

• User Payment Account or User LFI (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

• 39160988/Common+Rules+and+Guidelines#2.-

• User-Payment-Account-Selection).

• Payment Amount & Currency (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

• 39160988/Common+Rules+and+Guidelines#3.-Payment-Amount-%26-Currency).

• Payee Identification details (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

• 39160988/Common+Rules+and+Guidelines#4.-Payee-Identification).

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.

• Payer Note (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

• 39160988/Common+Rules+and+Guidelines#5.-Payer-Note) (Optional).

• Payment Reference (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages

• /39160988/Common+Rules+and+Guidelines#6.Payment-Reference).

Additional Consent Parameters

TPPs MUST:

1.2 Set the Accepted Authorization Type (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages

/39160988/Common+Rules+and+Guidelines#7.-Accepted-Authorization-Type).

1.3 Set the Authorization Time Window (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

39160988/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 (Please refer to https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

39160988/Common+Rules+and+Guidelines#18.-Multi-User-Authorization-Flow).

1.

4 Set the Consent Expiry Date accordingly if the Authorization Time Window is set to more than 1 day. This is to avoid the consent expiring before all necessary authorizations are completed. Otherwise, the default value of the Consent Expiry Date MUST be set to the same day (i..e current day). The Consent Expiry Time MUST always be set to 23:59:59 of the Consent Expiry Date.

1.

5 Set the Risk Information Block (as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

39160988/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

As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages

/39160988/Common+Rules+and+Guidelines#10.-Consent-Staging

SIP-3

Hand-off to LFI

As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

39160988/Common+Rules+and+Guidelines#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

LFIs MUST:

4.1 Enable Users to perform authentication with their LFIs, as per the following sections:

• https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39158936/Authentication+and+Authorization#2.-Redirection

• https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39158936/Authentication+and+Authorization#3.-Decoupled-Redirection

• https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39158936/Authentication+and+Authorization#4.-Decoupled-CIBA

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.

SIP-5

Confirmation/ Authorization

Standard Journey

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 using the unique Consent Identifier and present to Users all the details included in this.

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/StandardsDraft01/pages

/39160988/Common+Rules+and+Guidelines#12.-Payment-Account-Selection-at-LFI

• 5.3.1

• NOT allow Users to select a payment account from their list of available payment accounts that has insufficient funds for the Single Instant Payment (SIP

• ) initiation. This only applies in case Users do not select their payment account when providing their Consent to TPPs.

• 5.

• 3.2 Reject the Single Instant Payment (SIP) initiation, if the payment account identification was part of the Single Instant Payment (SIP) payment Consent provided to the TPPs and the payment account has insufficient funds. The OFP MUST be notified about this rejection with an appropriate error message.

5.4 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/StandardsDraft01/pages/39160988/Common+Rules+and+Guidelines#13.-Check-Accepted-Authorization-Type.

5.5 Add to the Single Instant Payment (SIP) Consent the IBAN of the Payee returned by the Proxy resolution process, if the Single Instant Payment (SIP) Consent was submitted for User Authorization using a Proxy as the Payee Identification. The Consent is thereafter tied to the IBAN of the Payee rather than the proxy itself.

• 5.5.1 Return back to the OFP in the payment Consent response the IBAN of the Payee identification returned by the Proxy resolution.

5.6 Present to Users the following minimum required information for authorizing the Single Instant Payment (SIP

) Consent:

• User Payment Account

• Payment Amount & Currency

• Payee Identification details including:

  • Payee Name

  • Payee IBAN (& alias if specified)

  • Payee Account Holding LFI

• Payer Note (Optional)

• Payment

• Reference

• Fees & VAT (if applicable): These are the charges that may be applied to the User account for making the payment in relation to the Single Instant Payment (SIP)

• Consent. If applicable, both bank charges and VAT MUST be presented and stated separately, prior to the User Consent authorization.

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 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 Single Instant Payment (SIP

) Consent.

5

.9 Check the Authorization Time window is valid as per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/39160988/Common+Rules+and+Guidelines#20.-Check-Authorization-Time-Window

5.10 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.11 Update the Single Instant Payment (SIP) Consent details stored in the OFP with all the information included in the Single Instant Payment (SIP) Consent authorized by the User.

OFP MUST:

5.12 Confirm back to the LFIs that the Single Instant Payment (SIP) Consent details have been updated successfully.

Multi-Authorization Journey Only

5.

13 As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

39160988/Common+Rules+and+Guidelines#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

Single Instant Payment (SIP) 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, 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.

6.3 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.

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

Intra-

bank payment.

6.5 Provide the

OFP 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

the UAE Open Finance Standard specifications.

6.6 Ensure that the Payment Reference provided in the

Single Instant Payment (SIP) Consent is made available to the Beneficiary’s account information in the case of

Intra-

bank payments within the same LFI.

OFP MUST:

6.7 Return back to the TPP in the Single Instant Payment (SIP) Consent response the IBAN of the Payee identification returned by the Proxy resolution, if the Single Instant Payment (SIP) Consent was submitted for User Authorization using a Proxy as the Payee Identification.

6.8 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.

6.9 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.

6.10 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-7

Payment Status Update

As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

39160988/Common+Rules+and+Guidelines#15.-Payment-Status-Update

SIP-8

Hand-off

back

to

the

TPP

As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

39160988/Common+Rules+and+Guidelines#14.-Hand-off-back-to-the-TPP

SIP-9

Confirmation to User

As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages/

39160988/Common+Rules+and+Guidelines#16.-Confirmation-to-

User

SIP-10

Payment Notifications

As per https://openfinanceuae.atlassian.net/wiki/spaces/StandardsDraft01/pages

/39160988/Common+Rules+and+Guidelines#17.-Payment-Notifications