How Embedded Commercial Insurance Actually Works
Embedded insurance is the fastest-growing distribution channel in Indian insurance, and in 2026 it has moved well beyond bolting travel cover onto a flight booking. API-first infrastructure now lets banks, fintechs, lending platforms, e-commerce marketplaces and B2B SaaS providers offer commercial and SME insurance directly inside the customer journey, at the moment a business takes a loan, lists on a marketplace, leases equipment or onboards to a platform. The cover is presented in context, priced at the point of transaction, and bought in a few clicks rather than through a separate broking conversation.
The mechanics rest on a layer of insurance infrastructure providers, insurtechs that sit between the insurer and the distribution platform and expose the insurer's products as application programming interfaces. The platform calls the API to retrieve eligible products, quote a premium, capture the data needed to bind, issue the certificate of insurance, and increasingly to handle servicing and first-notice-of-loss. The infrastructure provider abstracts away the complexity of integrating with multiple insurers, so a lending platform can offer, say, property, liability or cyber cover to its SME borrowers without becoming an insurance specialist.
For the SME, the value is access. India's commercial-insurance penetration among small businesses is thin, not because the risks are absent but because the traditional distribution model, a broker and a separate purchase decision, never reached them efficiently. Embedded distribution meets the SME where it already is, at the point it is already thinking about its business, and removes the friction of a separate transaction.
The channel is genuinely expanding the market. The question for a serious risk professional is what is gained, what is lost, and what duties survive the move to the API.
The Regulatory Duties That Do Not Disappear at the API
A recurring misconception is that embedding insurance into a platform somehow lightens the regulatory load because the experience is digital and frictionless. It does not. The IRDAI framework that governs how insurance is sold in India applies to embedded distribution in full, and the duties are simply distributed across the parties in the API chain rather than removed.
Three obligations in particular survive the move to the API and deserve attention.
Intermediary registration. The party distributing the insurance has to be an authorised intermediary, a registered broker, corporate agent, web aggregator or similar, or the arrangement has to be structured through one. A platform cannot solicit and sell insurance simply because it has integrated an API; the regulated activity of distribution still has to sit with a regulated entity. The infrastructure provider and the platform have to allocate, clearly, who holds the licence and bears the intermediary's duties.
Product filing and approval. The product offered through the embedded channel has to be an IRDAI-approved product filed for the use case in question. Embedding does not create a licence to invent cover; the wording, terms and pricing flow from a filed product, and the embedded presentation has to be faithful to it. A neatly designed point-of-sale flow that subtly diverges from the filed terms is a compliance problem, not a feature.
Disclosure and suitability. The buyer must be told who the insurer is, what the key exclusions and conditions are, and how to claim. The conduct obligation to give the buyer the information needed to understand the cover does not weaken because the buyer is two clicks from a checkout. If anything, the conversion-optimised context makes faithful disclosure more important, because the buyer is least likely to read and most likely to assume.
Layered over all of this is the DPDP Act and Rules 2025: the API chain moves personal and business data between platform, infrastructure provider and insurer, and each transfer is a processing activity with controller and processor duties that have to be mapped and lawful.
Where the Coverage and Conduct Risk Hides
The reach of embedded commercial insurance is real, but for a corporate risk team or a broker the harder question is where the risk hides, because point-of-sale cover optimised for conversion has characteristic failure modes that differ from broker-placed cover.
The first and largest is under-cover by design. Embedded products are typically simplified and standardised so they can be sold in a few clicks. For a genuinely small, homogeneous risk, that simplification is fine. For a business with any complexity, multiple locations, meaningful stock values, specific business interruption exposure, contractual liability obligations, the standardised product may bind a sum insured that is inadequate, omit covers the business actually needs, or carry exclusions the buyer never registered. The average clause does not relax because the policy was bought through an app; an under-declared sum insured will reduce the claim just the same.
The second is the absence of advice at the point of sale. The traditional broker channel exists partly to ask the questions a buyer does not know to ask, about exposures, limits and gaps. An embedded flow optimised for conversion generally does not. The SME buys what is presented, not necessarily what it needs, and discovers the gap at a claim. The convenience of the channel is, from a protection standpoint, also its weakness.
The third is fragmentation and the lost programme view. An SME that buys cyber from one platform when it onboards, property from its bank when it borrows, and liability from a marketplace listing accumulates a set of disconnected policies with overlapping and conflicting terms, no coherent programme, and no one looking at the whole. Each purchase was rational; the aggregate is a mess.
The fourth is claims-time disappointment. The same frictionless experience that made buying easy can make claiming hard if the embedded product's servicing and first-notice processes are thin, or if the buyer cannot easily find who the insurer is and what the policy wording actually says.
For a broker or risk team, the practical posture is not to dismiss embedded cover, which is filling a genuine gap, but to treat any embedded product the way you would any other: read the wording, check the sum insured and limits against the exposure, identify the exclusions, and confirm the claims path. The channel changes how the cover is bought; it does not change what makes the cover good or bad.
What Brokers and Risk Teams Should Demand Before Relying on Embedded Cover
Embedded commercial insurance is going to keep growing, and the right response from professional buyers and their advisers is not to fight the channel but to bring professional scrutiny to it. A small set of demands turns an embedded product from a black-box convenience into something a risk team can responsibly rely on.
Demand the wording, not the marketing screen. The point-of-sale flow shows a simplified description; the cover is the filed policy wording. Before relying on an embedded product, obtain and read the actual wording, because that is what responds at a claim, and the gap between the screen and the wording is exactly where disappointment lives.
Check adequacy against the real exposure. Confirm that the sum insured, limits and covers offered match the business's actual exposure, not a one-size template. Where the embedded product is too thin, the right answer is to use it for what it covers and arrange the rest properly, not to assume the app sized it correctly.
Establish the chain and the duties. Identify the insurer, the registered intermediary, and the infrastructure provider, and confirm the product is filed and used within its filing. This is not box-ticking; it tells you who is accountable for the advice, the cover and the claim.
Confirm the claims and servicing path. Establish how a claim is notified, who handles it, and how the buyer reaches the insurer, before a loss rather than after. A frictionless purchase with a thin claims process is a poor bargain.
Map the data flows. Under the DPDP Act and Rules 2025, the movement of business and personal data through the API chain carries obligations; for a corporate buyer, knowing where its data goes is part of its own compliance.
The common thread is that embedded distribution does not remove the need to understand the cover; it makes that understanding harder to come by, because the wording sits behind an interface designed to convert rather than to inform. This is exactly where structured access to the underlying wordings becomes the difference between informed reliance and blind reliance. Sarvada gives commercial-insurance brokers and corporate risk teams structured, searchable access to insurer wordings and the intelligence around them, so an embedded or point-of-sale product can be read, compared and stress-tested against the exposure on the same footing as any broker-placed cover, rather than taken on trust from a checkout screen. Brokers and risk teams who want to bring real scrutiny to embedded commercial cover can Request Access to evaluate the platform.