Why Automatic No-Usage Refund Preserves the Insurance Bundle Margin (2026)

Summary

20–30% of travel-insurance policies cover trips that never happen. Under a bundled-eSIM model, that cohort represents the entire risk to bundle margin. YonoSIM's 30-day no-usage sweep auto-credits the insurer's ledger for every unused eSIM — a $500k/year preservation on a 250k-policy book, and the only feature that makes bundled connectivity actually profitable at scale.

The cancellation-cohort math

Industry data on travel-insurance policies (2024–2026): 20–30% of policies cover trips that get cancelled, deferred, or no-showed. Common causes: illness (~40% of cancellations), work conflict (~25%), family emergency (~15%), plan change (~20%). Most policies refund partial or full premium; the eSIM bundle is a separate line on the insurer's ledger and doesn't automatically follow the premium refund.

This creates a hidden margin leak. On a 250k-policy book with $8 wholesale eSIM cost:

Total eSIM provisioning cost: 250k × $8 = $2M/year
Cancellation cohort (25%): 62,500 unused eSIMs
Cost of the unused cohort: 62,500 × $8 = $500k/year
Without auto-refund: $500k comes out of insurer's bundle margin
With YonoSIM auto-refund: $500k preserved

Why competitors don't ship this

Because it's operationally expensive for the eSIM provider. Every auto-refund is a real MVNO cost — the plan was provisioned against upstream supply that can't fully be clawed back. YonoSIM absorbs that cost as a competitive differentiator (the auto-refund is baked into the retail margin structure). Airalo for Teams and Holafly treat unused eSIMs as retained margin — a rational business model, just not the right one for insurance bundles where the cancellation cohort is guaranteed to be large.

Reconciliation shape

The auto-refund flow is a standard webhook — reconciliation against the specific policy uses the metadata field carried on the original POST /v1/orders. Sample flow:

// 1. Policy issued — provision eSIM with metadata
POST /v1/orders
{
  "planId": "eu_5gb_30d",
  "customerEmail": "[email protected]",
  "metadata": { "policyNumber": "POL-2026-045123", "insurer": "acme_ins" }
}

// 2. Trip cancelled 45 days later — eSIM never activated
// YonoSIM refunds this via good-faith transactional policy

// 3. Insurer receives webhook
POST https://insurer.example.com/yonosim-webhook
{
  "type": "order.refunded",
  "data": {
    "id": "ord_ABC123",
    "amountUsd": 8.00,
    "reason": "auto_refund_no_usage",
    "metadata": { "policyNumber": "POL-2026-045123", "insurer": "acme_ins" }
  }
}

// 4. Insurer's PAS matches the refund to the policy, credits
//    the bundle margin ledger, optionally partial-refunds the
//    policyholder if eSIM was itemized separately

FAQ

QWhat does automatic no-usage refund actually do?

AIf an eSIM is provisioned but never activated within 30 days of purchase, YonoSIM cancels the eSIM upstream and credits the partner's prepaid balance for the full activation cost. Fires as an order.refunded webhook — the insurer's PAS reconciles it against the specific policy that generated the eSIM. No support ticket, no refund form, no discretionary review.

QWhy don't other eSIM providers ship this?

ABecause it's operationally expensive for the provider. Every auto-refund is real MVNO cost to the eSIM aggregator (the plan was provisioned against upstream supply). YonoSIM absorbs that cost as a differentiator; Airalo for Teams, Holafly, and MVNO wholesalers treat unused eSIMs as retained margin. For a consumer eSIM buy the difference is a few dollars per plan — for a 250k-policy insurance bundle it's $500k/year.

QDoes the 30-day window match cancellation-cancellation timing for travel insurance?

AWell enough for the majority of cases. Travel insurance cancellations cluster in the 60–7 days pre-trip window (bought early, cancelled early). Since the eSIM is typically provisioned at the same time the policy is issued, the 30-day window covers most cancellation events. Edge case: policies bought 90+ days ahead have their eSIM sweep-refund on the 30-day mark before the trip is even scheduled — that's fine, the ledger credit goes back to the insurer, and a fresh eSIM can be issued closer to the trip if needed.

QHow does the insurer reconcile the refund against the specific policy?

AYonoSIM's metadata field on POST /v1/orders carries the insurer's policy number. When the refund fires, the order.refunded webhook payload includes that same metadata — the PAS matches the refund to the policy, adjusts the insurer's internal margin accounting, and (for policies where the eSIM cost was passed on to the customer separately) fires a partial refund to the policyholder's payment method.

QDoes auto-refund work if the customer activated the eSIM but never actually used data?

AThe default policy is: activation counts as usage — if the eSIM was installed on a device and connected to a network, it doesn't refund even if zero bytes were consumed. This is intentional; installation itself consumes upstream provisioning that can't be recovered. Custom policies (refund on zero bytes even after activation) are available on Enterprise tier for insurers who want stricter policyholder-refund alignment.

QWhat's the P&L difference at insurer scale?

AFor a 250k-policy insurer at $8 wholesale eSIM cost with 25% cancellation cohort: without auto-refund, ~$500k/year of unused eSIMs eaten as bundle-margin loss. With YonoSIM auto-refund: $500k/year preserved. Scale linearly to Allianz Global Assistance's multi-million-policy footprint — the number becomes strategically meaningful, not just operationally nice.

Bottom line

Automatic no-usage refund is the single feature that makes travel-insurance connectivity bundles profitable at scale across the cancellation cohort. YonoSIM is the only major eSIM provider that ships it as an API feature — Airalo, Holafly, and MVNO wholesalers treat unused eSIMs as retained margin. For a 250k-policy insurer that's $500k/year in preserved bundle margin; the difference scales linearly with book size. Back to the Travel insurance hub.