Skip to main content

Stops

Stopping your policy​

Once a policy is active (meaning SIGNED or STARTED), you can stop that policy to end the coverage. You can decide to stop at any time between the policy start date and its end date, which is calculated as your policy start date plus the contract duration as defined in your product configuration. Your policy becomes STOPPED and automatic workflows will no longer run for that policy, except for billing if there are still funds to balance out. When stopping a policy on a past date, your customer may be refunded because of pro-rata calculations. You can also choose to not refund customers for specific stop reasons - for example if you stop the policy because of non payment. Find out more about product customization here.

You can also elect to suspend your policy. A SUSPENDED policy will not be billed for its suspended time, but automatic workflows will continue running. You can then decide to reactivate the policy, at which point it will become STARTED once again.

Stop configuration​

You can configure how and when policies should stop. For each product, you determine a list of stop configurations that contain:

  • the stop reason
  • stop date limits, such as allowing stops in the past or in the future
  • refund behavior, so whether the customer should be refunded for this specific stop reason
  • how long this stop reason is valid for: for example, you might let customers stop with FULL_CANCELLATION only for the first two weeks their policy is active

A stop reason can also require the client-submitted stop date to fall within a window around today — a minimum offset, a maximum offset, or both — so a reason known to attract retroactive abuse (unjustified refunds, loss of collected premiums) can be restricted to future dates only, or a reason meant only for near-term use can be closed off beyond a certain point. For example, a reason configured with a minimum offset of one day rejects any stop date before tomorrow, even the current day; one configured with a maximum offset of 30 days rejects any stop date beyond that — both with INVALID_STOP_REASON_DETAILS. Stop dates are still checked against the other stop date limits above (policy start, and whether the future is allowed at all) — whichever rule the requested date violates first is the one returned.

A stop reason can instead anchor its date limit to the policy's next renewal date rather than today. Configured this way, the reason is only usable while today is strictly before the renewal date minus that duration — for example, a two-month notice period rejects the reason with INVALID_STOP_REASON_DETAILS from the moment exactly two months remain before renewal, not only once fewer than two months remain. Such a reason takes no stop date as client input at all: the effective stop date is always the policy's next renewal date, since renewal is the only date the reason is meant to apply to.