...

Below is a detailed breakdown of the average expected fees over five years for each tier of Bank and Insurer:

...

3. API Hub Fees, LFI to TPP Fees and TPP to End User Fees

To enable the regulatory-mandated pricing model, it may be operationally necessary for Nebras to establish VRP or direct debit arrangements with both LFIs and TPPs. If requested, the LFIs / TPPs MUST comply with the collections mechanisms and requirements from Nebras.

3.1 Service Initiation Functionalities

...

API Hub fees will be set at 2.5 fils per API call for all payment initiation use cases

LFIs to TPPs charges

LFIs to . If a payment transaction occurs within 2 hours of a Balance Check call or a Confirmation of Payee call, both the Balance Check and Confirmation of Payee calls will be charged separately at 0.5 fils each (instead of 2.5 fils), in addition to the 2.5 fils fee applied for the payment initiation call

LFIs to TPPs charges

LFIs to TPPs charges are summarized below:

...

1. LFIs are prohibited from imposing additional charges on end users for transactions initiated by Open Finance APIs related to data sharingservice initiation. However, charges for non-Open Finance API-initiated payments may be applied according to the product tariff agreed with the customer.

2. Fees will only be applied to successful transactions. 

3. Each payment within a bulk payment is considered an individual transaction by commercial model for billing purposes, and charged accordingly, ensuring that charges are accurately and fairly applied.

4. The fees applied to transactions remain the same, regardless of whether the payment is processed through AANI or a fallback rail.

TPP to End Users

TPPs to End Users charges are summarized below:

...

1. Fees will only be applied to successful transactions.

2. Each payment within a bulk payment is considered an individual transaction by commercial model for billing purposes, and charged accordingly, ensuring that charges are accurately and fairly applied.

3.1.2 Corporate

...

Payments

Target Segment

Corporate

Note:

• Corporate Customers are defined as individuals or entities with an annual revenue over AED 100 Mn.

Relevant Open Finance Functionalities

...

Note: Each page consists of a maximum of 100 lines

• An API call is charged for every 100 lines of transaction data, with a maximum age span of 13 months per call. If an API call returns more than 100 lines of transaction data, it will be

...

• considered as multiple

...

Note: LFIs are prohibited from imposing additional charges on end users for chargeable API calls related to data-sharing use cases under Open Finance.

Note: The fixed rate of 2.5 fils per page will be applied for each individual call, while LFIs are permitted to charge only for update requests.

TPPs to End Users

TPPs to End Users charges are summarized below:

...

Call Type

...

Definition

...

LFIs to TPPs Charges

...

Attended Call

...

Attended API calls represent the manual initiation of data requests, requiring active user involvement and consent for each request.

...

• Free for up to 15 calls per customer per day

• Pricing is market determined for any call exceeding that threshold

...

Unattended Call

...

Unattended API calls represented automated initiation of data requests which can be used for scenarios such as data refresh.

...

• Free for up to 5 calls per customer per day

• Pricing is market determined for any call exceeding that threshold

Note: API calls are limited to 100 lines of data, with an age span of 13 months per call.

Note: LFIs are prohibited from imposing charges beyond the set threshold. TPPs will pay the determined fee to the LFI, which includes the API Hub charge.

3.2.2 Other Data Sharing Functionalities

Target Segment

...

• calls and charged accordingly, including within LFI to TPP allowances and fees. Within the pagination structure of a transactional data API call, there can be 100 lines of data present per page.

3.2.2 Other Data Sharing Functionalities

Target Segment

Retail & SME

Relevant Open Finance Functionalities

Below is a list of all the relevant Open Finance functionalities:

• Banking Customer and Product Details

  • Confirmation of Payee

  • Payment Status

  • Customer Record

  • Product Record

• Bank Metadata Details

  • Direct Debit

  • Standing Orders

  • Overdrafts

API Hub fees

API Hub fees will be set at 2.5 fils per API call.

LFIs to TPPs fees

All Banking customer and product details aswell as bank metadata details will not incur charges from LFIs to TPPs

TPPs to End Users

The customer details and confirmation of payee use case will not incur charges from TPPs to the End User.

3.2.3 Life and Non-Life Insurance Data Sharing and Quotation Functionalities

Target Segment

Retail

Relevant Open Finance Functionalities

Below is a list of all the relevant Open Finance functionalities:

• Banking Customer Details

  • Confirmation of Payee

  • Payment Status

• Bank Metadata Details

  • Direct Debit

  • Standing Orders

  • Overdrafts

• Insurance Data Request

  • Insurance Consent

• Insurance Quotation Request

API Hub fees

API Hub fees will be set at 2at 2.5 fils for data sharing and 12.5 fils per call for quotes. This charge is independent from the number of quotes included in the API call.

LFIs to TPPs fees

The customer details and confirmation of payee use case will not incur charges from LFIs to TPPs.Note: LFIs are prohibited from imposing additional charges on end users for chargeable API calls related to data-sharing use cases under Open Finance.request of insurance data won’t be chargeable by LFIs for both Life and Non-Life insurance types

TPPs to End Users

The customer details and confirmation of payee use case will not incur charges from TPPs to the End User.

...

TPPs are only permitted to charge broker commissions and must be licensed brokers to provide quotes.

The request of insurance data and quotes will not be chargeable by TPPs for both Life and Non-Life

...

insurance types.

3.2.4 Corporate Data

Target Segment

Retail Corporate

Relevant Open Finance Functionalities

Below is a list of all the relevant Open Finance functionalities:

• Insurance Corporate Data Request:

  • Insurance Consent

• Insurance Quotation Request

API Hub fees

...

• • Accounts Details

  • Balance and Transaction Details

  • Scheduled Payment Details

  • Direct Debits Details

  • Beneficiaries Details

API Hub fees

API Hub fees will be set at 122.5 fils per call for quotes.
This charge is independent from the number of quotes included in the API call .

LFIs to TPPs fees

The request of insurance data won’t be chargeable by LFIs for both Life and Non-Life insurance types

Note: LFIs are prohibited from imposing additional charges on end users for chargeable API calls related to data-sharing use cases under Open FinanceFor Corporate Data use cases, a fee of 40 fils per request will be charged by the LFI to the TPP. For large data requests, a fee of 40 fils will be applied for every 100 lines of data.

TPPs to End Users

TPPs are only permitted to charge broker commissions and must be licensed brokers to provide quotes.

Charges will be market determined.

3.2.4 Corporate Treasury Data Functionalities

Target Segment

Corporate

Relevant Open Finance Functionalities

Below is a list of all the relevant Open Finance functionalities:

• Corporate Treasury Data:

  • Accounts Details

  • Balance and Transaction Details

  • Scheduled Payment Details

  • Direct Debits Details

  • Beneficiaries Details

API Hub fees

API Hub fees will be set at 2.5 fils per API call

LFIs to TPPs fees

Corporate Treasury Data use case will incur a charge of 40 fils for every 100 lines of data, to be charged by the LFI to the TPP.

Note: LFIs are prohibited from imposing additional charges on end users for chargeable API calls related to data-sharing use cases under Open Finance.

TPPs to End Users

The Corporate Treasury Data use case will involve charges for the end user, which will be applied by the TPP and determined by market conditions.

3.3 Timeline

The below timeline defines the start date for each of the five years, which exclusively affects LFI to TPP Fees, as outlined in the table below:

Note: Start dates are provisional and subject to change

4. Chargeable API Calls

...

API Specification

...

API End Point

...

API Operation

...

The Corporate Data use case will involve charges for the end user, which will be applied by the TPP and determined by market conditions.

3.3 Timeline

The below timeline defines the start date for each of the five years, which exclusively affects LFI to TPP Fees, as outlined in the table below:

Note: Start dates are provisional and subject to change

4. Chargeable API Calls

* one to one limitation between discovery and confirmation

...