What is embedded insurance?
Embedded insurance puts cover inside the journey that creates the insurable event, instead of selling it as a separate product later. That distinguishes it from both traditional distribution (an agent initiates the sale) and web aggregation (the customer initiates a comparison).
The principle is the moment of need: relevance is highest when the insurable event is being created. Four examples:
| Journey | Cover | Offered |
|---|---|---|
| Ride booking | Accident cover | At booking |
| Personal loan | Credit life | At sanction |
| Phone checkout | Damage protection | In cart |
| Gig onboarding | Hospicash | At signup |
Why it's growing in India
The global embedded insurance market is forecast to grow from $18.1B in 2026 to $68.1B by 2031, a 30.4% CAGR, with API-first placements already 76% of online distribution (Mordor Intelligence). APAC super-apps and mobile-first platforms are the fastest adopters.
India adds four drivers of its own: enormous digital-journey volume (UPI, ONDC, digital lending), insurance penetration stuck at 3.7% of GDP (IRDAI, FY25), sachet product innovation, and a regulator actively pushing distribution reach.
How embedded insurance works (technical)
The architecture has three layers: the host platform (the lender, marketplace or app), an insurance API layer such as DeployIT, and 35+ insurers behind it. The API layer normalizes quotes, proposals, issuance and servicing so the host integrates once.
The journey anatomy is consistent across products:
- 1
Trigger event. The loan sanction, checkout or signup that creates the insurable moment.
- 2
Offer API. Eligibility and price returned in real time for that customer and context.
- 3
One-screen consent. Disclosure and consent captured without breaking the host flow.
- 4
Instant issuance. The policy issues with the transaction; documents are delivered digitally.
- 5
In-app servicing. Claims, endorsements and renewals inside the host experience.
Build options run from API-only (full control) to SDK components (days of front-end work) to hosted journeys (fastest to launch). Details on the integrations page.
The regulatory reality
Distribution must run under an IRDAI framework: corporate agents, brokers and ISNP holders can distribute; the host platform's role is defined by which registration it holds or partners with. Consent, premium disclosure and grievance requirements apply in full, and the choice between group and individual policy constructs shapes what can be embedded where.
A platform layer enforces disclosures and consent capture so host apps do not reinvent compliance per journey. The regulatory checklist lives on the compliance page.
Embedded insurance economics
The revenue model is commission per policy as fee income, with zero balance-sheet risk. A worked example: a digital lender doing 50,000 personal loans a month, at 25% attach, ₹2,400 average premium and roughly 20% commission, generates about ₹7.2 Cr of annualized fee income.
| Unit economics | Value |
|---|---|
| Offer cost | Approximately one API call |
| Customer acquisition cost | Near zero; the journey already exists |
| Margin | Commission minus platform fee |
There is also a retention argument: customers holding two or more products churn measurably less.
What separates winners
- Offer relevance beats offer volume. Watch attach rate and complaint rate together; a high attach rate with rising complaints is a program eating its own trust.
- One-screen offers, invisible issuance. KYC reuse and no 40-field forms.
- Servicing in-app. The claims experience decides whether embedding builds or burns trust.
- Compliance as product, not paperwork. Disclosure UX done well converts better.
Launch playbook
- 1
Pick the moment. Choose the highest-intent event in your journey, the one that creates the insurable risk.
- 2
Pick the product. Sachet covers to start, comprehensive products for depth once the channel proves out.
- 3
Integrate. Sandbox on day 1, pilot in 3-4 weeks, scale in 6-8.
- 4
Measure. Attach rate, claim NPS, repeat-purchase lift and complaint rate.
Map your highest-intent moments
A working session on where embedded cover fits your journeys and what it would earn.
Embedded insurance examples in India
Five public patterns, each with a clear trigger and a product that fits it:
- Credit life on digital personal loans. Trigger: loan sanction. Works because the cover protects the exact liability being created.
- Device protection at electronics checkout. Trigger: cart. Works because damage risk is top of mind at purchase.
- Trip cover on travel OTAs. Trigger: booking confirmation. Works because the trip dates define the risk window.
- Hospicash for gig-worker platforms. Trigger: onboarding. Works because income protection is the gig worker's sharpest need.
- Cyber cover bundled with digital banking. Trigger: account opening or upgrade. Works because the bank relationship is where the exposure lives.
Related reading: glossary entries for embedded insurance, sachet insurance, attach rate and ISNP.
Frequently asked questions
What is embedded insurance with an example?
Insurance sold inside another purchase, e.g., a ₹49 damage-protection cover offered in a phone checkout, issued instantly with the order.
Is embedded insurance regulated in India?
Yes. Distribution must run under IRDAI frameworks (corporate agency, broking, ISNP) with mandated disclosures and consent.
Do platforms need an insurance licence to embed insurance?
The distributing entity needs an IRDAI registration; technology platforms like DeployIT keep the journeys compliant under that registration.
What attach rates does embedded insurance achieve?
Context-dependent: 18-30% in lending journeys, 3-6% in commerce checkouts on well-designed implementations.
How is embedded insurance different from bancassurance?
Bancassurance is a bank channel selling insurer products; embedded insurance is any digital journey offering contextual cover via APIs. Banca journeys can themselves be embedded.