How Phew works

Phew is repair-first product protection, sold at the moment of purchase. A customer buying a bike, sports equipment or electronics sees a short offer in the checkout (“Add 1 year · 89 kr”), adds it with one click, and is covered against accidental damage and breakdown. When something breaks, Phew organises a repair first and only replaces the item if it can’t be repaired.

The parties

Party	Role
Customer	Buys the item and, optionally, the cover. Holds the policy and makes claims directly with Phew.
Merchant	The webshop selling the item. Shows the offer and passes the order to Phew. Earns commission.
Partner	A payment provider, bank, e-commerce platform or agency that integrates Phew for many merchants.
Phew	Prices the cover, issues policies, handles claims and repairs, and settles with merchants and partners.
Insurer	A licensed Nordic insurer underwrites the cover. Phew acts as the intermediary.

From checkout to claim

1. Classification. When the cart is ready, your integration sends the items to Phew. Phew classifies each product automatically and decides whether it can be covered. There are no product mappings or eligibility rules for you to maintain.

2. Offer. For items that can be covered, Phew returns the plans, prices and the documents the customer must see: the terms and the insurance product information document (IPID).

3. Opt-in. The offer appears in your drop-in SDK or iframe embed, or in your own UI if you build with the API. The customer chooses a plan or declines; the offer is never pre-selected.

4. Policy. When the order is paid, your integration calls POST /v1/policies with the offer, the chosen plan and the customer’s contact details. Phew emails the policy documents to the customer.

5. Changes. If the item is returned or the customer withdraws within the cooling-off period, you cancel the policy and the premium is refunded.

6. Claim. The customer claims directly with Phew. Phew assesses it and arranges a repair, a replacement, store credit or a cash settlement. You can follow claims through webhooks.

7. Settlement. Each month Phew issues a settlement statement with the premiums collected, cancellations and the commission earned.

Who collects the premium

There are two settlement models. The one you use is agreed during onboarding.

• Merchant collects. The premium is a line on the order and is paid with the rest of the basket. The monthly statement nets the premiums against the merchant’s commission. This is the usual model for webshops.
• Split at payment. A payment provider splits the premium out of the payment and routes it to Phew. This removes the monthly netting step and is described in Payment providers and banks.

What Phew never needs

Phew does not receive card numbers, bank account details of customers, or authentication data for payment instruments. Card data is out of scope for every integration. See Data protection.

Environments

Environment	Checkout API	Partner API	Keys
Sandbox	https://api.getphew.com/v1	https://partner-api.getphew.com/v1	sk_test_…
Live	https://api.getphew.com/v1	https://partner-api.getphew.com/v1	sk_live_…

The key decides the mode. Sandbox requests never create real policies, never email customers and never move money, so you can test the full flow, including claims and settlement events, without risk.