How Claimful's protection fee is server-calculated

Every protection offer the widget shows comes from a server-issued quote, never a client-side formula. This document describes the inputs, the contract between merchant and Claimful, and the reasons we keep the math off the browser.

The inputs

The merchant integration sends Claimful three things on every checkout: the total order amount in integer cents, the consumer's region, and the list of items in the cart. Nothing else is required to produce a quote.

What the quote returns

The server returns a quote object containing a `quoteId`, a fee amount in integer cents, and an offer expiry timestamp. The widget displays the fee, the consumer opts in or declines, and the merchant confirms server-side using the `quoteId`. The fee math is never exposed.

Why we keep it server-side

Three reasons. First, the math depends on Claimful's protection coverage matrix which evolves; pinning it to a server endpoint means we can update it without shipping a new widget bundle. Second, server calculation means the consumer cannot tamper with the fee. Third, the fee is the contract — once issued, the quote is binding for the configured offer window.

What this means for refunds

The fee is the same regardless of refund outcome. A refund-request flow always works the same way: the consumer submits documents, the deterministic eligibility gate runs, AI triage produces a recommendation, and a human reviews any non-trivial outcome.