Embedded insurance
A bank, marketplace or car dealer sells insurance on its own website. The purchase widget is embedded with one line of code, and the Partner API provides policy calculation, issuance and cancellation on behalf of the partner. The partner learns about contract events through signed webhooks.
Plan Professional and Enterprise plans.
What is inside
- Premium calculation, product list, policy issuance and cancellation on behalf of the partner
- Public and secret partner API keys with permissions and request origin checks
- Webhooks on policy issuance, activation, cancellation, expiry and change
- HMAC signature, redelivery and protection against requests to the internal network
- An embeddable purchase widget with the same questionnaire as in the portal
- Sales attribution and partner commission
- Protection against repeated requests with an idempotency key
Conditions
The partner receives keys in the insurer’s back office. The insurer sets the product set and the key permissions.
Frequently asked questions
How long does it take to embed the widget?
The widget is connected with a script on the partner’s page and a public key. The questionnaire and products come from the insurer’s builder.
How does the partner learn about policy events?
Through webhooks: issuance, activation, cancellation, expiry and change. Every notification is signed with HMAC and redelivered after a failure.
Is it safe to give a partner API access?
Each key has its own permissions and request origin check. The secret key works only on the partner’s server.
Use cases with this feature
Other features
Shall we show the system on your products?
We will build your product in the builder, take a policy from quote to claim and estimate the implementation cost for your lines of business and countries.