Overview

The policy is the individual insurance contract — one per product sold in an emitted order. It is born at the order's emission, registered with the insurer and becomes the source of truth about the coverage: the insurer's policy number, the term, the effective coverages, the decomposed premium and the event trail.

Policy lifecycle

How to read the diagram: dashed outline = transient status that emits no webhook · blue = issuance confirmed (emits a webhook) · green = natural end of term (no webhook) · red = canceled (emits a webhook).

Status	Meaning
issuance_requested	Policy created at the order's emission; issuance was requested from the insurer and awaits confirmation.
issued	The insurer confirmed the issuance. The external_policy_number (policy number at the insurer) becomes available. Coverage is in force.
cancellation_requested	A cancellation was requested and awaits the insurer's confirmation. Coverage remains in force until the cancellation is confirmed.
canceled	The insurer confirmed the cancellation. The premium refund, when due, is computed and processed automatically.
finished	The policy term ended naturally (term.end_date). Terminal status, without an event — the end of term is known since issuance.

Premium refund on cancellation

When a cancellation is confirmed, QI Tech determines the refund basis and computes the amount automatically, over the gross premium (gross_premium_amount):

• Within 7 calendar days of the issuance confirmation (issued) — cooling-off right: full premium refund.
• After 7 days: refund proportional to the unelapsed coverage period (pro rata).

The refund is computed at the cancellation confirmation and executed to the payer by QI Tech itself.

Endpoints

Endpoint	Description
GET /v1/insurance/policies/{policy_key}	Retrieves one policy.
GET /v1/insurance/policies?order_key=	Lists the policies of an emitted order.
POST /v1/insurance/policies/{policy_key}/cancel	Cancels a policy individually.