Life Insurance
- Andy Woollatt
1. Description
This page provides a detailed overview of the data requirements necessary for initiating a Life insurance quotation request within the UAE Open Finance framework. It must be read in conjunction with the https://openfinanceuae.atlassian.net/wiki/x/t5QlEw page to ensure alignment with the end-to-end quotation process.
The data outlined here includes both mandatory fields, which must be collected to generate a valid quote, and optional fields, which can enhance the accuracy and personalization of the quotation. TPPs can utilise this information to structure their data collection and submission process when requesting quotes from LFIs, either from all available institutions or based on user selection.
If pre-populated data from existing user insurance policy(ies) is used or will be leveraged during the quotation process, the https://openfinanceuae.atlassian.net/wiki/x/bJQlEw framework must also be referenced. This ensures compliance with UAE Open Finance data-sharing protocols and transparency in data utilisation.
1.1 Scope
The Life Insurance Quotation Process supports the following different levels of insurance cover:
1.1.1 Insurance Cover Options
Type of Insurance | Scope | Description |
|---|---|---|
Whole of Life Insurance | Provides lifetime coverage, meaning the policy remains active as long as premiums are paid. It guarantees a death benefit pay-out to beneficiaries upon the insured person's passing, regardless of when it occurs. | |
Level Term Insurance | A type of term life insurance where the sum assured remains constant throughout the policy term. If the insured person passes away during the term, the full benefit is paid out. | |
Decreasing Term Insurance | A type of term life insurance where the sum assured decreases over time while the premium remains constant. The pay-out reduces over the policy term, typically aligning with financial obligations that decrease over time, such as a mortgage. | |
Unit-Linked Insurance Plans (ULIPs) | Out of scope of the Standards due to the investment component of the life product. | |
Group Life coverage | Life insurance quotes for Group Life coverage, where the employer is the policyholder and the employee is the life assured, are out of scope of the standards |
1.2 Information Required for a Life Insurance Quotation
To request a life insurance quotation from each or selected LFIs, the TPP must obtain the following information from the User:
The life insurance coverage required
Who will be covered. If the Policyholder is not the Life Assured (or one of the Life Assured), confirmation of the relationship between the Policyholder and the Life Assured will be required.
Policyholder's personal details, including identity verification and employment details.
Details of each Life Assured, when the Policyholder is not the Life Assured or for joint life insurance policies.
Tobacco use history. Confirmation of whether the Life Assured currently uses or has previously used tobacco products. If ‘Yes,’ details of past or current tobacco use must be provided.
2. Life Insurance Data Sharing Clusters
As part of the Life insurance data sharing consent set-up between the TPP and user, the TPP must either:
Specify the data required from the user’s insurance account(s) to provide the requested service, or
allow the user to select which data clusters the TPP can access.
Both the TPP and the user must confirm the type(s) of insurance policy the TPP will access.
The agreed-upon data permissions, along with confirmation of the insurance type, must be included in the Pushed Authorization Request (PAR) body.
2.1 Data Cluster Permissions
The data permissions permitted for Life insurance are:
Data Cluster language | Permission | Permissions Language | Examples of Information available |
|---|---|---|---|
Your Insurance Policies |
| Your Insurance Policy ID and basic policy information | Provide policy identifiers to facilitate retrieval of other policy details. |
Your Customer Details |
| Your basic information | Provides your full name, address, contact details and date of birth |
| Your detailed information | Provides your full details held by the Insurance provider including your identity details, employment details. Your full name, address, contact details and date of birth will also be provided. | |
Your Product Details |
| Your Life detailed policy information | Provides all policy data held by the Insurance provider |
Your Premium Details |
| Your insurance premiums | Provides the details of the premium paid or being paid, along with confirmation of future renewal premiums when applicable. |
Your Claim Details |
| Your claims declared and submitted | Provides the details of any insurance claims declared during the insurance application and subsequently made. |
Your Medical Details |
| Your medical declarations | Provides the details of the medical declarations made during the insurance application and subsequently confirmed to the Insurance Provider |
Your Payment Details |
| Your Premium payment bank account details | Provides the bank account details used or being used to make the insurance premiums. |
3. Quote UX Guidelines & Data Capture
3.1 Insurance Quote Data Capture
The Quote dataset outlined in the tables below represents a broader set of data that may be required by LFIs to generate a quote. This comprehensive dataset accounts for variations in LFI quotation processes and differences in when specific data points are collected from the customer.
While TPPs may collect and include this data in the Quote API request body, there is no Open Finance Standards requirement for LFIs to utilize all provided data if it is not part of their quotation process.
Capturing and submitting a fuller dataset at the quotation stage aims to:
Improve the relevance and accuracy of the generated initial quote premium.
Minimize unexpected premium increases during the final application, reducing customer frustration and drop-offs.
Reduce the need for additional data collection by the LFI if the customer chooses to proceed with the quote.
Enable earlier detection by the LFI of potential underwriting issues that could result in the customer’s application being declined.
3.2 Quote UX Requirements & Guidelines
3.2.1 Language Requirements
TPPs MUST:
Provide user-facing channels that are bilingual, supporting both Arabic and English.
Ensure that data values in API requests are provided in English, as the Standards APIs do not support Arabic
3.2.2 Quote Data Capture Field Order
TPPs MAY:
Define the order in which required customer and insurance information is collected or presented for verification when a data-sharing arrangement exists, ensuring alignment with their commercial strategy and user experience preferences.
Control how conditional fields are displayed or omitted, allowing the presentation of the required fields to adjust dynamically based on the data entered by the customer in associated fields.
3.2.3 Enumeration Options
TPPs MAY:
Define how API enumeration options are presented to the User during the quote application process, as this falls within their remit and is not dictated by these Standards, allowing flexibility based on the TPP’s customer experience principles and commercial considerations.
3.2.4 Optional Data
TPPs MUST:
When a question is relevant to the customer and the data is available, the information must be captured and included in the Quote API request body even if 'No' is reflected in the 'Required' column within the Data Cluster tables.
3.3 Life Insurance Quote Data Clusters
The data provided within the tables reflect the following ‘Required’ states:
Mandatory Fields ("Yes" in the ‘Required’ Column)
Fields marked as "Yes" in the Required column are mandatory in the Quote API request body. If this data is missing, the API Hub will reject the request, or the LFI will be unable to generate a quote premium.Conditional Fields ("Conditional" in the ‘Required’ Column)
Fields marked as "Conditional" are required based on the customer’s response in an associated field. The Guidelines column specifies when this data must be provided. Failure to include required conditional data may prevent the generation of a quote premium due to missing information.Optional Fields ("No" in the ‘Required’ Column)
Fields marked as "No" are optional, as the question and data may not be relevant to all customers. If a field is not applicable, its absence will not trigger a 400 rejection response from the API Hub or prevent the LFI from generating a quote premium.
The Guidelines column, where applicable, will also reflect the options that must be presented to the customer for selection. These options are aligned with the enumerations within the Quote API request body.
The API Field column provides clarification on the Quote API request body field to which the customer’s response must be mapped by the TPP.
3.3.1 Life Policy Coverage Questions
3.3.1.1 Requirements When Policyholder and Life Assured are not the same
When the Policyholder of the life insurance cover is not one of the life assured:
the
IsPolicyholderLifeAssuredflag must be set to No (false).the
InsuranceCoverForfield must specify whether the coverage is for a Spouse or Child;an
LifeAssuredobject must be provided for each person covered under the life insurance policy.The
PolicyHolderobject must be provided.
| UX Field Label | Required | Guidelines | Quote API Field |
|---|---|---|---|---|
| Life Insurance Type & Coverage Requirement | Yes |
|
|
1.01 | Insurance Policy Type | Yes | The User must confirm whether they want Conventional or Takaful Life Insurance |
|
1.02 | Sole or Joint Coverage Required? | Yes | Confirmation whether the life coverage is required for a single person or jointly for multiple individuals. The options are: Sole or Joint |
|
1.03 | Will you be covered under this policy? | Yes | Confirmation (Yes or No) whether the Policyholder will also be the life assured or one of the life assured when a joint policy. |
|
1.04 | Relationship To Life Insured | Conditional | Required when the |
|
1.05 | Reason Different | Conditional | Required when |
|
1.06 | Type Of Life Insurance required? | Yes | The options are: Whole of Life Insurance, Level Term Insurance, Decreasing Term Insurance |
|
1.07 | Insurance Purpose | Yes | The options are: Personal Cover, Family Protection, Mortgage Cover |
|
1.08 | Sum Assured Amount | Yes |
|
|
1.09 | Sum Assured Currency | Yes |
|
|
1.10 | Policy Term Required | No |
|
|
1.11 | Cover Start Date | Yes |
|
|
1.12 | Is Loan Against Policy | Yes | Confirmation whether insurance cover is being taken out in connection with a loan / mortgage |
|
3.3.2 Life Assured Questions
| UX Field Label | Required | Guidelines | Quote API Field |
|---|---|---|---|---|
| Life Assured Details | Yes |
|
|
2.01 | Relationship to Proposer | Yes | Options are: Self, Spouse, Child |
|
2.02 | Salutation | No | Options are: Mr, Mrs, Miss, Ms |
|
2.03 | First Name | Yes |
|
|
2.04 | Middle Name | No |
|
|
2.05 | Last Name | Yes |
|
|
2.06 | Previous Name | Yes | Yes or No confirmation whether the Life Assured has been known by any previous names or aliases. |
|
2.07 | Previous Name Details | Conditional | Section required when the User confirms the Life Assured has been known by any previous names or aliases. Either Maiden Name field or Alias Name field must be populated |
|
2.07.01 | Maiden Name | No | The customer’s family name before they were married |
|
2.07.02 | Alias Name | No | Any name, whether legal or casual, that the customer uses or has used on any forms in addition to their birth name. This includes shortened versions of their name. |
|
2.08 | Gender | Yes | Options are: Male or Female |
|
2.09 | Date Of Birth | Yes |
|
|
2.10 | Marital Status | Yes | Options are: Single, Married, Divorced, Widowed |
|
2.11 | Mobile Number | Yes |
|
|
2.12 | Email Address | Yes |
|
|
2.13 | Nationality | Yes |
|
|
2.14 | Second Nationality | No |
|
|
2.15 | Country of Birth | No |
|
|
2.16 | Primary Language | No | Options available are: English, Arabic, Other |
|
2.17 | Residential Location | No |
|
|
2.18 | Address Details | Yes |
|
|
2.18.01 | AddressType | Yes | The type of address being provided. |
|
2.18.02 | Building Number | Yes | The house, unit, apartment, or villa number assigned to the property. For new developments where a building number has not been assigned, this can reflect the plot number. |
|
2.18.03 | Building Name | No | The name of the building or community where the address is located |
|
2.18.04 | Street Address | Yes | The street address or road name of the property |
|
2.18.05 | Area | Yes | The specific district, neighbourhood, or locality where the address is situated |
|
2.18.06 | PO Box | No | The P.O. Box number assigned for mail delivery |
|
2.18.07 | City | Yes | The municipality or city of the property |
|
2.18.08 | Emirate | Yes | The Emirate where the address is registered. Options are: Abu Dhabi, Ajman, Dubai, Fujairah, Ras Al Khaimah, Sharjah, Umm Al Quwain |
|
2.18.09 | Country | No | The country associated with the address |
|
2.19 | Life Assured Identity Details | Yes |
|
|
2.19.01 | Emirates Id Number | Yes |
|
|
2.19.02 | Emirates Id Expiry Date | No |
|
|
2.19.03 | Passport Number | No |
|
|
2.19.04 | Passport Issue Date | No |
|
|
2.19.05 | Passport Expiry Date | No |
|
|
2.20 | Life Assured Employment Details | Yes |
|
|
2.20.01 | Employment Type | Yes | Options available are: Private Salaried, Federal Government, Self Employed, Retired, Not Employed, Other |
|
2.20.02 | Job Title | Conditional | Required when the Employment Type is NOT Retired or Not Employed |
|
2.20.03 | Employer Name | Conditional | Required when the Employment Type is NOT Retired or Not Employed |
|
2.20.04 | Nature Of Employer Business | Conditional | Required when the Employment Type is NOT Retired or Not Employed |
|
2.20.05 | Employment Start Date | Conditional | Required when the Employment Type is NOT Retired or Not Employed |
|
2.20.06 | Income Currency | Conditional | Required when the Employment Type is NOT Retired or Not Employed |
|
2.20.07 | Monthly Income | Conditional | Required when the Employment Type is NOT Retired or Not Employed. Either Monthly Income or Annual Income must be populated. |
|
2.20.08 | Annual Income | Conditional | Required when the Employment Type is NOT Retired or Not Employed. Either Monthly Income or Annual Income must be populated. |
|
3.3.3 Life Assured Lifestyle Questions
| UX Field Label | Required | Guidelines | Quote API Field |
|---|---|---|---|---|
3.01 | Alcohol Questions | Yes |
|
|
3.01.01 | Do you consume alcohol? | Yes |
|
|
3.01.02 | If ‘Yes’ please provide the number of units* consumed each week. | Conditional | Required when the Life Assured consumes alcohol. |
|
3.02 | Smoking Questions | Yes |
|
|
3.02.01 | Do you currently smoke or used any tobacco product? | Yes |
|
|
3.02.02 | If ‘Yes’ , please confirm the type of tobacco product | Conditional | Required when the Life Assured currently smokes. Options available are: Tobacco, Cigarettes, Pipe, Shisha, E-Cigarettes, Vape, Chew Tobacco |
|
3.02.03 | Please confirm the quantity or frequency of tobacco used each day | Conditional |
|
|
3.03 | Previously Smoking Questions | Conditional | If the Life Assured does not currently use any tobacco products they must be asked whether they have previously used tobacco products |
|
3.03.01 | Have you previously smoked or used any tobacco product? | Conditional | Required if the Life Assured as confirmed that they do not currently smoke. |
|
3.03.02 | If ‘Yes’, please confirm the type of tobacco product you previously used | Conditional | Options available are: Tobacco, Cigarettes, Pipe, Shisha, E-Cigarettes, Vape, Chew Tobacco |
|
3.03.03 | Please confirm the quantity or frequency of tobacco previously used each day | Conditional |
|
|
3.04 | How long have you or did you smoke questions? | Conditional | Required when the Life Assured has confirmed that they currently or have previously smoked. |
|
3.04.01 | Number of years smoking | Conditional | Required when the Life Assured has confirmed that they currently or have previously smoked. |
|
3.04.02 | Number of months smoking | Conditional | Required when the Life Assured has confirmed that they currently or have previously smoked. |
|
3.04.03 | When did you stopped smoking? | Conditional | Required when the Life Assured has confirmed that they have previously smoked, but have stopped |
|
3.04.04 | Why did you stopped smoking? | Conditional | Required when the Life Assured has confirmed that they have previously smoked, but have stopped |
|
3.3.4 Policyholder Questions
If the Policyholder is also one of the insured persons, TPPs can pre-populate the information from the Life Assured section into the Policyholder section.
When the Policyholder is not one of the Life Assured the following information about the Policyholder must be captured:
| UX Field Label | Required | Guidelines | Quote API Field |
|---|---|---|---|---|
| Policyholder Details | Conditional | Required when the Policyholder is not one of the life assured |
|
4.01 | Salutation | No | Available options are: Mr, Mrs, Miss, Ms |
|
4.02 | First Name | Yes |
|
|
4.03 | Middle Name | No |
|
|
4.04 | Last Name | Yes |
|
|
4.05 | Previous Name | Yes | Yes or No confirmation whether the Policyholder has been known by any previous names or aliases. |
|
4.06 | Previous Name Details | Conditional | Section required when the User confirms the Policyholder has been known by any previous names or aliases. Either Maiden Name field or Alias Name field must be populated |
|
4.06.01 | Maiden Name | No |
|
|
4.06.02 | Alias Name | No |
|
|
4.07 | Gender | Yes | Available options are: Male or Female |
|
4.08 | Date Of Birth | Yes |
|
|
4.09 | Marital Status | Yes | Available options are: Single, Married, Divorced, Widowed |
|
4.10 | Mobile Number | Yes |
|
|
4.11 | Email Address | Yes |
|
|
4.12 | Nationality | Yes |
|
|
4.13 | Second Nationality | No |
|
|
4.14 | Place Of Birth | No |
|
|
4.15 | Primary Language | No | Options available are: English, Arabic, Other |
|
4.16 | Residential Location | No |
|
|
4.17 | Address Details | Yes |
|
|
4.17.01 | Address Type | Yes | Options available are: Permanent or Residential, Billing |
|
4.17.02 | Building Number | Yes | The house, unit, apartment, or villa number assigned to the property. For new developments where a building number has not been assigned, this can reflect the plot number. |
|
4.17.03 | Building Name | No | The name of the building or community where the address is located |
|
4.17.04 | Street Address | Yes | The street address or road name of the property |
|
4.17.05 | Area | Yes | The specific district, neighbourhood, or locality where the address is situated |
|
4.17.06 | PO Box | No | The P.O. Box number assigned for mail delivery |
|
4.17.07 | City | Yes | The municipality or city of the property |
|
4.17.08 | Emirate | Yes | The Emirate where the address is registered. Options are: Abu Dhabi, Ajman, Dubai, Fujairah, Ras Al Khaimah, Sharjah, Umm Al Quwain |
|
4.17.09 | Country | No | The country associated with the address |
|
4.18 | Policyholder Identity Details | Yes |
|
|
4.18.01 | Emirates Id Number | Yes |
|
|
4.18.02 | Emirates Id Expiry Date | No |
|
|
4.18.03 | Passport Number | No |
|
|
4.18.04 | Passport Issue Date | No |
|
|
4.18.05 | Passport Expiry Date | No |
|
|
4.19 | Policyholder Employment Details | Yes |
|
|
4.19.01 | Employment Type | Yes | Options available are: Private Salaried, Federal Government, Self Employed, Retired, Not Employed, Other |
|
4.19.02 | Job Title | Conditional | Required when the Employment Type is NOT Retired or Not Employed |
|
4.19.03 | Employer Name | Conditional | Required when the Employment Type is NOT Retired or Not Employed |
|
4.19.04 | Nature Of Employer Business | Conditional | Required when the Employment Type is NOT Retired or Not Employed |
|
4.19.05 | Employment Start Date | Conditional | Required when the Employment Type is NOT Retired or Not Employed |
|
4.19.06 | Income Currency | Conditional | Required when the Employment Type is NOT Retired or Not Employed |
|
4.19.07 | Monthly Income | Conditional | Required when the Employment Type is NOT Retired or Not Employed. Either Monthly Income or Annual Income must be populated. |
|
4.19.08 | Annual Income | Conditional | Required when the Employment Type is NOT Retired or Not Employed. Either Monthly Income or Annual Income must be populated. |
|
3.4 Additional Information Collected by the LFI During Underwriting
If the Customer elects to proceed with the life insurance application, the LFI will collect, where applicable, the following data as part of its underwriting process:
Full Medical history, health status and biometric data, including height and weight.
Family medical status and history of first-degree relatives.
Primary Care Physician details for the Life Assured.
Past or future travel plans.
Confirmation of whether the Life Assured participates in any hazardous activities or high-risk sports.
Any additional details relating to the Policyholder or Life Assured employment.
Military employment details, if the Life Assured is currently a member of the armed forces.
Details of any existing life insurance cover.
Confirmation and details of any previous life insurance applications that have been declined.
Beneficiary details for the life insurance policy.
@ CBUAE 2025
Open License and Contribution Agreement | Attribution Notice