Insurance customers increasingly use online platforms to compare premiums, coverage, exclusions, and policy benefits. An Insurance Web Aggregator provides a regulated interface through which customers can access information about products offered by different insurers.

However, starting an insurance comparison platform requires more than developing a website. The business must obtain registration from the Insurance Regulatory and Development Authority of India, commonly known as IRDAI, and satisfy the applicable eligibility, capital, personnel, technology, and compliance requirements. Understanding these requirements before investing in website development or marketing helps promoters prepare a suitable business structure and a consistent registration application.

In this article, CA Manish Mishra talks about How to Register as an Insurance Web Aggregator.

What Is an Insurance Web Aggregator?

An Insurance Web Aggregator is a registered insurance intermediary that maintains a website providing information and comparisons relating to insurance products offered by different insurers. Its activities must remain within the scope permitted under the applicable regulatory framework.

For example, a person looking for health insurance may compare policies based on premium, coverage, waiting periods, exclusions, and other features. The platform enables the customer to examine these differences before proceeding through the permitted purchase or enquiry process. An Insurance Web Aggregator does not become an insurance company merely because it facilitates access to insurance products. The insurer issues the policy and bears the insurance risk.

Legal Structure for Insurance Web Aggregator Registration

Insurance Web Aggregators are governed by the IRDAI (Insurance Web Aggregators) Regulations, 2017, read with subsequent amendments and applicable directions. The framework establishes requirements concerning registration, financial resources, personnel, website operations, customer information, and business conduct.

The IRDAI (Insurance Intermediaries) (Amendment) Regulations, 2026 introduced important changes to registration validity, annual fees, reporting, and related obligations. Applicants must therefore use the amended requirements rather than rely solely on older registration guides. The company or LLP must also comply with the laws governing its constitution, accounts, taxation, employment, technology, and other applicable matters.

Why Is Registration Required?

An insurance comparison platform can influence decisions that affect a customer’s financial protection. Information about price alone may be insufficient if material exclusions, deductibles, or waiting periods are not explained appropriately. Registration creates a framework for accountability. It requires the applicant to establish that its structure, financial position, management, and operating arrangements meet the prescribed conditions.

For promoters, the registration process also helps identify whether the intended commercial activities fit the web aggregator category. This assessment should take place before committing substantial resources to a business model that may require a different intermediary registration.

Eligibility Conditions for Insurance Web Aggregator Registration

Eligible Legal Structure

The regulatory framework recognises a company incorporated under the Companies Act and an eligible Limited Liability Partnership, subject to the prescribed conditions. The LLP route includes specific conditions concerning non-resident participation.

Promoters should examine ownership, investment, and management arrangements before deciding on the structure. Where foreign investment is proposed, the applicable investment rules and regulatory conditions require a separate review. Incorporating an entity does not itself authorise insurance web aggregation. The entity must also obtain the required IRDAI registration before commencing regulated activities.

Appropriate Business Objects

The applicant’s constitutional documents should appropriately describe insurance web aggregation as its main business. The framework restricts unrelated activities, making the objects clause and the actual operations important parts of eligibility.

An existing technology, consultancy, or marketing business should review its current activities before applying. Its proposed registration should be supported by a structure and business description consistent with the permitted scope. The Memorandum of Association or LLP agreement should therefore be reviewed before the registration documents are finalised.

Minimum Capital or Contribution

The prescribed minimum paid-up capital or contribution is ₹25 lakh. For a company, capital must be contributed in the manner permitted under the applicable framework; merely stating an authorised capital figure does not establish compliance.

The financial records should demonstrate that the required contribution has been made and properly recorded. Supporting certificates and statements should reconcile with the applicant’s accounts and banking records. Promoters should also plan for operating expenditure beyond the regulatory minimum. Website development, salaries, premises, training, and professional support require separate financial resources.

Maintenance of Net Worth

An Insurance Web Aggregator must maintain net worth at least equal to the prescribed minimum capital requirement. Capital and net worth are related but different concepts.

For example, a business may initially receive ₹25 lakh in capital but subsequently incur expenses and losses that reduce its net worth. Meeting the requirement at incorporation does not establish continuing compliance. Regular financial review helps management identify whether additional funding or corrective action is needed.

Appointment of a Principal Officer

The applicant must appoint a Principal Officer who satisfies the prescribed qualification, training, and examination requirements. The role carries responsibility for the web aggregator’s activities and should be supported by clear authority within the organisation.

The proposed Principal Officer should understand the business model, customer journey, regulatory obligations, and internal controls. The position should not exist only to complete the application checklist. Management should define responsibility for regulatory communications, website information, staff supervision, customer complaints, and compliance monitoring.

Fit-and-Proper Requirements

The relevant promoters, directors, partners, shareholders, Principal Officer, and management personnel must satisfy the applicable fit-and-proper conditions. Applicants should prepare complete disclosures concerning matters covered by the prescribed forms and declarations.

Relevant proceedings, regulatory history, or other material information should be explained accurately where required. Incomplete or inconsistent disclosures can create questions about the reliability of the application and the suitability of the persons involved.

Designated Website

The applicant must have a designated website for its proposed web aggregation activities. The platform should be developed around the permitted business model and the applicable display, information, and customer-handling requirements.

The website described in the application should match the platform being developed. Its enquiry forms, comparison pages, communications, and supporting systems should form a consistent operating process. A general advertising website may require substantial changes before it is suitable for regulated insurance web aggregation.

Review of Other Registrations and Relationships

Existing intermediary registrations, referral arrangements, and group relationships must be examined against the applicable eligibility conditions. Promoters should identify all relevant businesses and relationships before filing.

Where another group entity operates in insurance intermediation, the proposed structure requires careful assessment of the applicable conditions and potential conflicts. A clear ownership and activity chart can help explain these arrangements during scrutiny.

Website and Technology Preparation

Product Comparison Information

The comparison interface should help customers understand meaningful differences between products. Premiums should be considered alongside relevant features, exclusions, eligibility conditions, and coverage restrictions.

For example, two policies with similar prices may have different deductibles or waiting periods. The design should avoid creating the impression that price alone determines suitability. Responsibility for reviewing and updating product information should be assigned clearly.

Customer Enquiry and Consent Journey

The business should document what happens when a customer submits an enquiry. This includes the information collected, its intended use, the proposed recipients, and the follow-up process.

Customer-facing explanations should correspond with actual system behaviour. A consent statement should not describe a limited use of information if the operating model involves wider sharing. Mapping the journey during development helps the technology and compliance teams work from the same understanding.

Information Security and Access Controls

Customer information should be protected through appropriate technical and organisational controls. Staff access should reflect their responsibilities, and important actions should be traceable.

The business should consider secure storage, access management, backups, incident handling, and vendor controls during development. Building security into the platform at the beginning is generally easier than redesigning systems after customer information has already been collected.

Testing Before Public Operation

The complete platform should be tested using sample information before regulated operations begin. Testing should cover comparison displays, enquiry submissions, customer communications, access permissions, and error handling.

The review should identify whether customers could misunderstand information or whether staff could use systems outside their intended role. Any issues should be corrected before the platform is used for live business.

Documents Required for Registration

Incorporation and Constitutional Documents

The applicant should prepare its incorporation certificate, Memorandum and Articles of Association or LLP agreement, PAN, registered office information, and relevant authorisations.

Names, addresses, and other particulars should be consistent across the application and supporting records. Where amendments or corrections are necessary, they should be addressed before filing. An existing entity should also review its historical activities and records for consistency with the proposed application.

Promoter, Director, and Partner Records

Relevant identity information, professional profiles, qualification records, ownership details, and declarations should be organised for the persons covered by the application.

The information should provide a clear account of who owns, controls, and manages the business. Layered ownership arrangements should be supported by appropriate charts and records. All disclosures should be checked against the current prescribed requirements.

Principal Officer Documents

The Principal Officer’s documents should establish the required qualifications, training, examination status, appointment, and other relevant particulars. The applicant should confirm that the proposed person meets the applicable conditions before relying on that appointment in the application. Discrepancies between certificates, identity records, and application details should be resolved or explained appropriately.

Financial Records and Certificates

Financial documents should establish the applicant’s capital and net-worth position. Supporting records may include financial statements, banking evidence, contribution records, and the prescribed certifications.

The figures should reconcile across the records. If a certificate uses a particular financial date, the supporting statements should make that position clear. A financial review should also consider how initial expenses affect continuing eligibility.

Business Plan

The business plan should explain the proposed products, customers, insurer arrangements, delivery methods, staffing, technology, expenses, and revenue assumptions.

Financial projections should be realistic and supported by the operating model. A plan projecting rapid growth should explain how the business will fund technology, personnel, service support, and compliance. The application should describe the proposed business as it will actually operate.

Website and Internal Process Documents

Prepare the website information, system descriptions, customer journey, procedures, and other materials required under the current checklist or requested during scrutiny. Internal documents should explain how information is updated, enquiries are handled, customer records are protected, and complaints are escalated. Generic policies should be adapted to the applicant’s actual systems and responsibilities.

Step-by-Step Registration Procedure

Step 1: Confirm the Appropriate Registration Category

Begin by defining the proposed activities and comparing them with the permitted scope of an Insurance Web Aggregator. A comparison platform, insurance broker, corporate agent, and Insurance Marketing Firm operate under different frameworks. The intended service should determine the registration route. Resolving this question early helps prevent expensive changes to the structure and website later.

Step 2: Complete Naming and Incorporation Preparation

Applicants should follow the current process for obtaining any required No Objection Certificate for the proposed name and completing incorporation formalities. The constitutional documents should support the permitted business, and ownership and management arrangements should be recorded clearly. The proposed name, entity details, and business description should remain consistent throughout the registration process.

Step 3: Arrange Capital and Financial Certification

Bring in the required contribution through properly documented channels and complete the associated corporate formalities. Arrange the financial review and prescribed certifications. Confirm that the capital and net-worth position meets the requirements after considering relevant expenses and losses. Maintain adequate resources for the period before the business begins generating revenue.

Step 4: Appoint Eligible Personnel

Identify the Principal Officer and other personnel needed for the proposed activities. Verify the applicable qualification, training, examination, and authorisation conditions. Assign practical responsibilities and establish reporting lines. The organisation should be able to explain who manages compliance, customer handling, website information, and regulatory correspondence. Where telemarketing is proposed, its separate personnel and permission requirements need attention.

Step 5: Develop the Website and Operating Systems

Build the platform around the proposed regulated activities. Prepare the comparison interface, enquiry process, information security controls, and supporting records. The website should be reviewed together with the business plan and internal procedures. Each should describe the same customer journey and operating arrangements. Complete testing before public operation.

Step 6: Prepare and Submit the Application

The prescribed application framework uses Form A, supported by the documents identified in Form B and the applicable regulations. Applicants should use the current amended forms and submission instructions. Proposed outsourcing or telemarketing arrangements should be addressed specifically where relevant. Complete the applicable payment and retain the acknowledgement. A full copy of the submitted application should be maintained for future reference.

Step 7: Respond to Regulatory Queries

IRDAI may request further information, clarification, or supporting documents. Each response should address the question directly. If the information changes an earlier statement, explain the reason and update all affected records. Maintain a tracker showing outstanding requests, responsible persons, deadlines, and submission acknowledgements.

Step 8: Complete Approval Formalities

Complete the payments and other requirements communicated by the authority within the specified period. Before commencing business, review the registration certificate and any conditions carefully. An application acknowledgement or incorporation certificate does not replace the required registration. Management should confirm that all applicable conditions have been addressed.

Step 9: Establish Readiness to Commence Business

The final preparation stage should confirm that staff, systems, records, customer communications, and complaint-handling arrangements are ready. Conduct a practical review of the complete operating process. Staff should understand their permitted activities and escalation responsibilities. Commercial launch plans should reflect both registration status and operational readiness.

Registration Validity Under the 2026 Structure

The 2026 amendments replaced the earlier periodic renewal model with continuing registration subject to annual fee payment and compliance, until suspension or cancellation.

Continuing registration does not remove the need to meet the applicable operating conditions. Financial requirements, personnel obligations, reporting, fees, and business conduct remain relevant throughout the registration period. Existing web aggregators holding earlier certificates should examine the applicable transition requirements rather than assume that no further action is necessary.

How Long Does Registration Take?

The overall timeline depends on incorporation readiness, personnel eligibility, capital documentation, website development, application completeness, and regulatory queries. Preparation and regulatory examination should be planned separately.

A promoter who has not finalised the structure or completed the platform cannot assess the total launch period solely from the application filing date. A useful progress update identifies the current stage, outstanding documents, responsible person, and next milestone. Approval should not be promised within a fixed period.

Compliance After Registration

• Financial Monitoring: The business should review capital, net worth, expenses, and cash flow regularly. Early identification of financial pressure gives management time to arrange additional resources or take corrective action. Regulatory financial requirements should remain part of routine management reporting.

• Website Information and Content Controls: Assign responsibility for maintaining accurate product information and reviewing significant website changes. The business should have a process for identifying outdated information, correcting errors, and maintaining relevant records of updates.

• Staff Conduct and Customer Communications: Personnel should understand their permitted role and the boundaries of the registration. Customer communications should be clear, accurate, and consistent with the business’s authorised activities. Complaints and operational errors should be escalated through an established process.

• Regulatory Reporting and Annual Payments: Maintain a compliance calendar covering annual fees, regulatory submissions, certifications, and other applicable obligations. The 2026 amendments also strengthen reporting and introduce specified annual disclosures for certain foreign-owned or larger web aggregators. Applicability should be assessed against the business’s circumstances.

• Changes in the Business: Proposed changes to ownership, management, personnel, website arrangements, or activities should be reviewed before implementation. Where approval or intimation is required, the prescribed process should be completed. Corporate approval alone may not satisfy the applicable regulatory conditions.

Common Mistakes to Avoid

A frequent mistake is developing the platform before confirming that web aggregation is the appropriate category. This can require costly changes to the website, staffing, and proposed agreements.

Other problems include inadequate financial planning, inconsistent records, incomplete personnel documents, unclear ownership, and delayed query responses. Applicants should also avoid relying on outdated descriptions of registration validity and fees. The application and business plan should reflect the requirements applicable at the time of filing.

Conclusion

Registering as an Insurance Web Aggregator requires coordinated preparation across legal structure, capital, personnel, technology, and documentation. A clear operating model and consistent records make the proposed business easier to assess and help reduce avoidable clarification.

The responsibilities continue after registration. Maintaining financial eligibility, accurate information, secure systems, responsible customer communication, and timely regulatory compliance is essential to operating the platform properly.

Frequently Asked Questions (FAQ’s)

Q1. What does an Insurance Web Aggregator do?

Ans. An Insurance Web Aggregator provides a regulated website interface for comparing insurance products and accessing information about products offered by different insurers, within its permitted scope.

Q2. What is the minimum capital requirement?

Ans. The prescribed minimum paid-up capital or contribution is ₹25 lakh. The applicable net-worth requirement must also be maintained.

Q3. Can an LLP apply for registration?

Ans. An eligible LLP may apply, subject to the prescribed conditions. Its partner composition and any non-resident participation require examination before selecting this route.

Q4. Is a Principal Officer required?

Ans. Yes. The applicant must appoint a Principal Officer who meets the prescribed qualification, training, examination, and other applicable conditions.

Q5. Can the business start after incorporation?

Ans. Incorporation alone does not authorise regulated insurance web aggregation. The required IRDAI registration must be obtained before commencing such activities.

Q6. Is registration still renewed every three years?

Ans. The 2026 amendments replaced the earlier periodic renewal model with continuing registration subject to annual fees and compliance. Earlier certificate holders must examine the applicable transition provisions.

Q7. Can a web aggregator issue insurance policies as an insurer?

Ans. No. The insurer issues the policy and bears the insurance risk. The web aggregator acts as an intermediary within its authorised scope.

Q8. Is regulatory capital included in the application fee?

Ans. No. Capital is contributed to the business. Application fees, annual regulatory fees, professional expenses, and operating costs are separate.

Q9. Can an Insurance Web Aggregator undertake telemarketing activities?

Ans. Yes, subject to the required IRDAI permission and compliance with applicable telemarketing rules. The business must also meet the prescribed personnel, training, examination, and customer communication requirements.

Q10. What factors can delay Insurance Web Aggregator registration?

Ans. Incomplete documents, financial discrepancies, pending personnel qualifications, website deficiencies, and delayed responses to regulatory queries can extend the process. Accurate preparation and timely responses help reduce avoidable delays.