Research Report · April 2026

The Protection Layer
Is Moving to AI

AI platforms are taking ownership of the checkout — and the protection moment is moving with them. Inside a 58-respondent study of how agentic commerce is reshaping who owns the trust, the transaction, and the revenue.
58 Product, AI & Commerce Leaders · US · Software/Technology

For the last two decades, embedded protection — trip cancellation, purchase protection, extended warranty — has lived at the merchant's checkout. That is about to change.

In our survey of 58 product, AI and commerce leaders at enterprise AI platforms, incumbent merchants building AI, and vertical AI startups, a striking consensus emerged: as AI platforms move from pure discovery layers into native transaction owners, the protection moment is migrating with them. Most respondents aren't theorizing about this future — they're building for it this year, they want to own the user relationship, they have a clear design brief for what the experience should feel like, and a precise picture of what a partner-powered, white-label protection layer needs to deliver.

While the headline findings are remarkably consistent across the survey, three distinct buyer profiles emerged when we segmented by company type — each with different integration preferences, business cases, and strategic posture. See Takeaway 6 →

78%
Say the protection moment moves with the platform when AI owns checkout
64%
Rank embedded protection as a top-3 priority for their team this year
55%
Want fully white-label protection — the partner invisible to the end user
1

79% of AI Platforms Are Already Inside the Transaction — and Protection Is Moving With Them

AI platforms are no longer content to be discovery layers that hand users off to merchants. The majority already own or are actively building native transaction capability — and as they take over checkout, two valuable assets move with them: the protection moment, and the margin itself.

Most platforms already own — or are actively building — native transaction capability

Q1: "How would you describe the current role your AI platform plays in a user's purchase journey?"
By segmentVertical AI startups are furthest along (47% own end-to-end), Enterprise AI is earliest (38% still pure discovery) — a 31pt gap. See Takeaway 6 →

When AI platforms own checkout, the protection moment moves with them

Q6: "Today, the merchant or travel platform owns the protection offer at checkout. If your platform moves to owning checkout natively, what do you think happens to that protection moment — does it move with you, stay with the merchant, or disappear entirely?"

And the margin follows the checkout — 78% expect platform economics to replace merchant revenue-share

Q14: "As your platform moves further into owning the transaction, how do you see the commercial model evolving — do you expect margin to shift away from merchant revenue share toward platform economics, and what does that mean for how ancillary products like protection get priced and distributed?"

Key Insight

Only 21% of AI platforms still see themselves as a pure discovery layer. The remaining 79% are already inside the transaction in some form — and when asked where the protection offer goes next, 78% say it moves with the platform. A nearly identical 78% expect margin economics to migrate too. These are two independent survey questions, but the alignment is striking — suggesting checkout, trust, and money are moving as one structural shift, not three separate trends.

"If a platform owns native checkout, the protection offer naturally moves with it — the checkout moment is where trust is built."
— Head of AI / AI Product Lead, Enterprise AI Platform
"The commercial model is shifting from a commission-based retail model to a fee-based platform economics model. In an agentic world, the platform's value moves from 'selling products' to orchestrating transactions and trust."
— Product Manager / Head of Product, Incumbent Merchant Building AI
2

This Isn't Drift — and the Window Is Three Years

This shift isn't being forced by technology or pulled by regulation — it's a deliberate strategic bet. Two-thirds of respondents frame their current positioning as a chosen posture, 60% see native checkout within three years, and over half plan to become regulated financial intermediaries themselves. The single most-common answer to "when will this happen?" is actually "it depends" — a quarter of respondents won't commit to a date, instead listing conditions like payments infrastructure, fraud protection, and merchant trust. For protection partners, the window is measured in quarters, not years — and the partners that solve those conditions will determine the timeline.

67% say their current positioning is a strategic choice — not a technology or regulatory constraint

Q2: "What's driving that positioning — is it a strategic choice, a regulatory constraint, or a technology limitation?"

60% see native checkout within three years — but a quarter won't commit to a date

Q3: "Over what time horizon do you see your platform evolving toward completing purchases natively — and what would need to be true, technically or commercially, for you to fully own the checkout experience?"

Over half plan to become regulated financial intermediaries themselves

Q16: "As AI platforms take on more of the transaction relationship, where do you see your platform landing on financial regulation?"

Key Insight

The strategic framing matters. When two-thirds of respondents say their current positioning is a chosen posture rather than a constraint, it implies the timing of the next phase is theirs to set. Combined with the 60% three-year horizon and 52% intent to become regulated intermediaries, the survey points to a market committing to a destination, not drifting toward one. For protection partners, that means positioning claimed now will be hard to displace later.

"It's a strategic choice — enables full control over user experience, data, and monetization."
— Head of AI / AI Product Lead, Enterprise AI Platform
"Over the next 2–3 years I expect platforms to gradually move toward native checkout as integrations with payment providers, identity verification, and fraud prevention mature."
— Product Manager / Head of Product, Incumbent Merchant Building AI
3

The Rare Triple-Win: Trust, Conversion, and Revenue in One Product

Embedded protection isn't a 2027 roadmap item. Nearly two-thirds of respondents rank it in their top three priorities this year, travel and retail are the early beachheads, and the business case is unusually broad — combining trust, conversion lift, and direct revenue in a single product. What unlocks the next tier of priority is rarely one thing — most platforms point to a combination of pilot proof, integration ease, and user demand.

Embedded protection is a top-3 priority this year for 64% of platforms

Q10: "How high a priority is enabling embedded insurance or protection integrations within your roadmap today?"
Multi-mention · does not sum to 100%

Travel leads the agentic commerce beachhead, with retail close behind

Q7: "Which verticals are you prioritizing first for agentic commerce — and why?"
Multi-select · does not sum to 100%

Trust and direct revenue tie as the #1 reasons to embed protection

Q15: "How do you see embedded protection contributing to your platform? (Select all that apply)"
By segmentSame chart, different motivations: Enterprise AI leads with revenue (88%), Vertical AI leads with trust (87%) — a 34pt gap on direct revenue alone. See Takeaway 6 →
Multi-select · does not sum to 100%

Ease of integration is the single biggest driver of prioritization

Q11: "When deciding which ancillary products or verticals to enable first, what's driving your prioritization? (Select all that apply)"

Most platforms cite multiple triggers — but proven ROI is the clearest single unlock

Q12: "What would move it up — or what would need to change for it to become a top priority?"

Key Insight

The data inverts a common assumption. Platforms aren't primarily motivated by margin. Asked what drives their prioritization across ancillary products, 78% point to ease of integration. Asked separately how protection contributes to their platform, 78% name building user trust. Two different questions, one converging picture. When asked what would unlock further priority, the most-cited single answer is "multiple factors must align" (28%) — typically a combination of pilot proof, integration ease, and user demand — and only 21% cite proven ROI alone. Partners who can ship behind a clean API and produce conversion-lift data from a design partner will find the door wide open.

"A proven lift in user retention or conversion from early protection pilots, plus clear partner readiness with simple APIs, would move it to top priority."
— Head of AI / AI Product Lead, Vertical AI Startup
"High-intent, repeat-purchase verticals like travel, food delivery, groceries, and consumer electronics — they combine frequent demand, clear decision criteria, and strong ROI from automation."
— Head of AI / AI Product Lead, Vertical AI Startup
4

71% Want the User in Control at Payment — So Protection Has One Moment to Land

Once the business case is made, the design question takes over — and here the answers are remarkably specific. AI platforms have converged on a clear view of how protection should feel inside an agent-driven journey: visible but not intrusive, surfaced at the moment of commitment, and never replacing the user's explicit consent at payment.

Even in agentic flows, the user stays in the loop — especially at payment

Q4: "When it comes to agentic purchases, how are you thinking about user control and trust?"
By segmentThe agent-UX philosophy splits dramatically: Enterprise AI prefers rules-upfront autonomy (50%), Incumbents want approve-each-transaction gating (63%) — a 39pt gap, the largest segment divergence in the survey. See Takeaway 6 →

62% want protection presented at checkout — as a clear opt-in, visible but not intrusive

Q8: "Thinking purely about user experience — if embedded protection were to live within your platform, how do you think it should be presented to the user? At what point in the interaction, in what format, and how prominently?"

Inside an agentic booking flow, final booking is the single most-cited placement

Q9: "If your platform were to design an embedded protection experience within an agentic flow — say, a user asks your AI to plan and book a trip to Mexico — what would that look like and where in the journey would it sit?"

Key Insight

The UX consensus has direct implications for product design. Only 29% of platforms want a fully autonomous agent that executes without transaction-level approval — the other 71% want the user to stay in control at payment, which means protection needs to fit into an explicit consent moment. Push it earlier and it feels premature; bolt it on afterward and it feels like an upsell. The winning pattern: a plain-language opt-in at the moment the user confirms payment, with optional contextual reinforcement during planning.

"For a platform-owned checkout, the UX should focus on 'invisible security' — moving protection from a friction-filled sales pitch to an integrated trust signal."
— Product Manager / Head of Product, Incumbent Merchant Building AI
"Protection should be woven through the trip planning journey as intelligent guidance, then activated at the booking moment — not bolted on as a final popup."
— Head of AI / AI Product Lead, Enterprise AI Platform
5

The Partner Spec Is Written: Invisible, API-First, Full-Stack

When we asked platforms to describe the ideal embedded protection partner, the answer was remarkably consistent. They want a white-label product delivered through an API, with fast automated claims — and they want the partner to absorb the regulatory and underwriting burden so platforms can focus on the agent experience.

55% want fully white-label — the protection partner is invisible to the end user

Q18: "If your platform were to offer embedded protection through a partner, how would you want it branded and operated?"

79% prefer API-based integration — direct or via an orchestration layer

Q13: "When integrating third-party ancillary services into your transaction layer, what's your preferred technical model?"
Multi-mention · does not sum to 100%

API integration tops the list — mentioned by half of respondents — followed by transparent pricing and fast claims

Q17: "What would a compelling embedded protection partnership look like for your team — and is there anything that would be an immediate dealbreaker?"

Key Insight

The partnership model is crystallizing around three non-negotiables: brand invisibility (55% want the partner fully hidden), API-first delivery (79% combined for direct API or orchestration), and a full-stack partner that handles underwriting, licensing and claims. Recurring dealbreakers cited in open-text answers include manual claims, opaque pricing, checkout friction, and anything that pushes regulatory liability back onto the platform. Read together, these signals suggest that partners still leading with co-branded widgets or requiring users to leave the agent flow will face an uphill climb in this segment.

"Compelling partner gives us the underwriting and licensing. The product has to feel like ours. Deal-breakers are anything that breaks the agent experience or creates brand risk."
— Head of AI / AI Product Lead, Enterprise AI Platform
"A compelling partnership moves away from 'selling insurance' and toward 'enabling autonomous trust.'"
— Head of Strategy, Enterprise AI Platform
6

Three Buyer Profiles, Not One Market

The market isn't unified. When respondents are segmented by company type, what looks like one buyer splits into three — with fundamentally different views on integration, the role of protection, and how far into checkout they have already moved. The aggregate findings still hold; the product, packaging, and proof points required to win the deal do not.

Profile 01 · n=24
The Aggregator-in-Waiting
Enterprise AI platforms — foundation models, agent infrastructure, horizontal AI tools.
  • 88% see protection as direct revenuevs. 53% of Vertical AI
  • 50% prefer an orchestration layervs. 20% of Vertical AI
  • 38% still describe themselves as pure discovery todayvs. 7% of Vertical AI — they are the earliest in the journey
What defines them Still moving toward checkout, building for scale and revenue — 75% describe their positioning as a deliberate strategic choice, and they want partners who plug in invisibly behind their brand.
Profile 02 · n=19
The Cautious Augmenter
Incumbent merchants and platforms layering AI into existing flows.
  • 63% want users to approve every transactionvs. 25% of Enterprise AI
  • 53% describe their positioning as a strategic choicevs. 75% Enterprise AI and 80% Vertical AI — the lowest sense of strategic agency
  • 53% plan to stay as the distribution layervs. 29% of Enterprise AI
What defines them Leaning into agentic cautiously, with users in the loop — they want partners who can prove conversion lift and fit into existing checkout patterns.
Profile 03 · n=15
The Specialist Builder
Vertical AI startups built natively around a single use case.
  • 87% see protection as a trust buildervs. 75% of Enterprise AI
  • 60% prefer direct API integrationvs. 32% of Incumbents
  • 47% already own end-to-end checkoutvs. 21% of Enterprise AI — they are furthest along
What defines them Already at checkout, focused on a single use case — 80% describe their positioning as a deliberate choice, the most strategically confident of the three segments. They want direct, lightweight protection APIs they can wire into a polished UX.
Single-select · sums to 100%

The smaller they are, the further they have gone — Vertical AI startups are deepest into checkout, while Enterprise AI platforms are still earliest in the journey

Q1: "How would you describe the current role your AI platform plays in a user's purchase journey?"
Single-select · sums to 100%

Strategic agency or legacy constraint — AI-native segments overwhelmingly call their position a choice, while Incumbents are split between strategy and technology limits

Q2: "What's driving that positioning — is it a strategic choice, a regulatory constraint, or a technology limitation?"
Single-select · sums to 100%

Enterprise AI wants autonomy. Incumbents want approval. The agent UX is not one design.

Q4: "When it comes to agentic purchases, how are you thinking about user control and trust?"
Multi-mention · does not sum to 100%

Why they want protection: revenue, conversion, or trust — segments lead with different motivations.

Q15: "How do you see embedded protection contributing to your platform? (Select all that apply)"
Single-select · sums to 100%

Three different integration architectures — there is no single "API standard" for embedded protection in agentic commerce

Q13: "When integrating third-party ancillary services into your transaction layer, what's your preferred model?"
Single-select · top 3 of 4 options shown (~3% omitted)

Different stomachs for regulation — Incumbents prefer to stay distribution-only, while Enterprise AI platforms split toward becoming regulated themselves

Q16: "As AI platforms take on more of the transaction relationship, where do you see your platform sitting in five years from a regulatory standpoint?"
Multi-mention · does not sum to 100%

Enterprise AI casts a wide vertical net; Incumbents and Verticals concentrate their bets

Q7 / S4: "Which verticals are you prioritizing first for agentic commerce?"

Key Insight

The structural finding holds across every segment: protection is moving with checkout. But the buying criteria diverge sharply depending on where each segment sits in that journey. Enterprise AI platforms — earliest in the journey, scale-oriented — want a revenue-share orchestration partner who disappears behind their brand. Incumbents — already at checkout, conversion-focused — want proof of conversion lift and integration patterns that match how their existing platforms work. Vertical AI startups — already at checkout, trust-focused — want a direct API they can wire into a single, polished user experience. There is no single embedded protection play. There are three — three distinct products, three distinct integration models, and three distinct GTM motions.

"We don't want a side-by-side experience. We want one cohesive product where insurance is part of how the agent thinks, not bolted on at the end."
— Head of AI, Vertical AI Startup
"It needs to feel native to our existing checkout — same approval flow, same pricing display. Anything that asks our user to learn a new pattern is a non-starter."
— Product Manager, Incumbent

Meet the Shift — Don't Miss It

AI platforms are building the next transaction layer right now, and they have told us exactly what they need: an API-first, fully white-label embedded protection partner that handles underwriting, licensing and claims so they can focus on the agent experience. The structural shift is universal — the right packaging, integration model, and proof points differ by buyer profile. The window to be the default choice is open today, and it is closing fast.

Talk to our embedded protection team →

Methodology

58
Qualified respondents
US
Geography
Apr 2026
Survey period
86%
Direct decision-making authority over checkout (S3)

Who We Spoke To

Respondent Roles

S1: "Which of the following best describes your primary role?"

Company Type

"Which category best describes your company?"

Company Scale

S6: "How would you describe the scale of the business your AI platform sits within?"

AI Platform Architecture

S5: "How would you describe the AI platform you work on?"

Transaction Status Today

S2: "Does your AI platform currently facilitate, or plan to facilitate within the next 12 months, a financial transaction or checkout process?"
Multi-select · does not sum to 100%

Verticals Served

S4: "Which of the following sectors does your AI platform currently serve or plan to serve within the next 12 months? (Select all that apply)"

Screening & qualification: Respondents were screened to confirm their AI platform currently facilitates — or plans to facilitate within 12 months — a financial transaction, that embedded protection has come up in internal discussions, and that they have direct decision-making authority or significant influence over checkout architecture. Specifically, on screening question S3, 86% (50/58) reported direct decision-making authority and 14% (8/58) reported significant influence over checkout architecture. Early-stage startups were disqualified; all respondents work in Mid-stage, Scaled, or Enterprise businesses.

Open-text categorization: Each free-text response was read and categorized manually by primary theme.

Segmentation analysis (Takeaway 6): Respondents were grouped by company category as reported on screening question S5 — Enterprise AI platform / infrastructure (n=24), Incumbent building AI features (n=19), and Vertical AI startup (n=15). Segment-level percentages are directional; with n=15 in the smallest segment, a single respondent shifts that segment's value by 6.7 points. Differences smaller than approximately 15 percentage points should be read as suggestive rather than definitive.

0