What is parametric insurance?

Parametric insurance is a type of insurance that pays automatically when predefined conditions (triggers) are met, such as rainfall below a certain level or wind speed above a threshold. Unlike traditional insurance, it requires no claims process, no adjusters, and no damage assessment. Payouts are calculated using pre-agreed formulas based on data from trusted sources.

How fast are parametric insurance payouts?

Parametric insurance payouts typically arrive within 24-72 hours after a trigger event is detected, compared to 3-12 months for traditional insurance claims. This speed is critical for disaster response, allowing affected communities to access funds during the crisis rather than months afterward.

How does blockchain help with parametric insurance?

Blockchain enables automatic execution through smart contracts, transparent and auditable records, cross-border payments without traditional banking infrastructure, and reduced costs through lower overhead. Smart contracts automatically trigger payments when data oracles verify that threshold conditions are met.

What is a trigger threshold in parametric insurance?

A trigger threshold is the predefined condition that activates an insurance payout. Examples include rainfall below 150mm triggering drought coverage, wind speeds above 120 km/h for hurricane coverage, or water levels exceeding 3 meters for flood coverage. When data sources verify the threshold is exceeded, the smart contract automatically executes payment.

Who benefits from parametric insurance?

Parametric insurance particularly benefits smallholder farmers, vulnerable communities in climate-affected regions, and populations without access to traditional insurance. Over 50 million farmers globally are covered by index-based insurance, and more than $1.4 billion in parametric payouts have been delivered to developing countries between 2007-2023.

What is basis risk in parametric insurance?

Basis risk is the mismatch between what a parametric trigger measures and the actual losses people experience. It has two forms: negative basis risk, where a community suffers real losses but the index does not cross the trigger threshold, so no payout occurs; and positive basis risk, where a payout is triggered even though little damage occurred. Careful trigger design, better data sources, and multi-variable indices reduce basis risk but never eliminate it entirely.

How does parametric insurance relate to Loss and Damage in climate negotiations?

Parametric insurance is one of the financial tools discussed under the UNFCCC Loss and Damage agenda for climate impacts that go beyond what adaptation can prevent. Programs such as the Global Shield against Climate Risks, regional risk pools like African Risk Capacity (ARC), CCRIF in the Caribbean, and PCRAFI in the Pacific use parametric triggers to deliver rapid finance to vulnerable countries after climate disasters. It complements, but does not replace, grant-based loss and damage funding.

How are parametric insurance premiums calculated?

Parametric premiums are based on expected loss: the probability of each trigger event multiplied by the payout it would produce, summed across all covered events. Insurers then apply a loading factor, typically 1.3 to 1.8 times expected loss, to cover data costs, capital reserves, administration, and profit. Lower trigger thresholds mean more frequent payouts and higher premiums; higher thresholds reduce premiums but increase the risk that real disasters go uncovered.

What is the difference between sovereign and sub-sovereign parametric insurance?

Sovereign parametric insurance is purchased by national governments, often through regional risk pools such as ARC, CCRIF, or PCRAFI, with payouts flowing to the national treasury for disaster response. Sub-sovereign or micro-level programs cover states, municipalities, cooperatives, or individual farmers directly, often distributed through mobile money. Sovereign programs offer scale and lower premiums; sub-sovereign programs put money closer to affected communities but face higher distribution costs.

Development Log

Version History

A complete record of platform updates, new features, and fixes for the Parametric Insurance Simulator — Climate Risk Edition.

Maintained by Web3 Certification Board Inc. (W3CB)·Current version: v2.4.0·11 releases

＋ Added◈ Changed✕ Fixed

＋Added

Embed mode

Add ?embed=true to any URL. The simulator removes its navigation header, site footer, disclaimer modal, and cookie consent banner — leaving only the simulation interface. A small "Powered by W3CB" attribution strip replaces the full footer. Works on any page: the home screen, individual scenarios, education centre, or methodology page.

Scenario deep linking

Two equivalent patterns: /?embed=true&scenario={id} auto-redirects to /scenario/{id}?embed=true via a client-side handler, or use the long-form URL directly. All 9 scenarios supported. Intended use: LMS course modules embed a specific scenario matching the lesson context without requiring learners to navigate from the home screen.

PostMessage completion events

When a learner clicks Finish at the end of the debrief review in embed mode, the simulator fires window.parent.postMessage with type "w3cb_scenario_complete". Payload includes: scenarioId, scenarioName, triggered (boolean), payoutAmount (USD), riskScore (0–1), coverageTier, and timestamp (ISO 8601). Platforms can use this to record completion, update a gradebook, or surface a custom overlay — without any server-side API dependency.

Embed integration guide

New developer documentation page at /embed. Covers: basic iframe code, responsive wrappers, all supported URL parameters, the full PostMessage listener with annotated payload spec, CSP domain allowlist configuration (for institutional IT teams), nginx config example, and live test URLs for all 9 scenarios.

Frame-ancestors CSP header

Content-Security-Policy: frame-ancestors * is emitted by the Express API server (production) and Vite dev server (development). Allows the simulator to be framed by any origin — a prerequisite for institutional embedding without requiring IT exceptions on every platform. The invalid X-Frame-Options: ALLOWALL header was removed (browsers ignore it; CSP is the correct mechanism).

◈Changed

Compact scenario header in embed mode

When ?embed=true is active, the back button is hidden (navigating to "/" inside an iframe is disorienting) and the header is centred. Scenario icon, name, region, and complexity badges remain visible to give learners clear context.

✕Fixed

Embed state persists across internal navigation

useEmbedMode now stores an embed flag in sessionStorage (w3cb_embed_active) the first time ?embed=true is seen, so header/footer/modals stay suppressed even if a learner clicks an internal link that drops the query parameter.

Deep-link handler is now reactive

EmbedDeepLinkHandler's effect dependencies were corrected so /?scenario=xxx redirects work on any URL change, not just the initial mount.

Completion modal suppressed in embed mode

The in-app "Scenario Complete" modal no longer renders inside an iframe. The w3cb_scenario_complete postMessage is the single completion signal — letting host LMS platforms drive their own post-completion UI without conflict.

Production framing headers moved to Express

Content-Security-Policy: frame-ancestors * is now set by Express middleware so it applies to production deployments, not just the Vite dev server. The invalid X-Frame-Options: ALLOWALL value was removed.

Embed docs security & accuracy corrections

PostMessage listener example now requires origin validation (prevents spoofed completion events). CSP guidance clearly distinguishes frame-ancestors (set by us) from frame-src (set by the host). Added a third-party iframe storage-partitioning caveat for Safari ITP / Chrome. SEOHead now implements noIndex, keeping /embed out of search results.

Commits: adbc87d