Insurance website development: from quote to policy issuance
An insurance website displays a price, the customer pays for the order, but there is still no document. Support is looking for the payment, a manager is checking the application, and the customer clicks the button again. For a head of digital sales, insurance website development starts with a question: how can you connect quoting, payment and policy issuance so that everyone involved sees a confirmed outcome?
When commissioning a website, determine which decisions belong to the web application, which belong to the insurer’s system, and where a specialist steps in. This division defines the interface, integrations and acceptance criteria.
First, decide how far automation should go
For the first version, identify the specific insurance product, sales channel and outcome the customer should receive. This might be a request for a consultation, an agreed quote leading to payment, or an automated purchase process through the insurer’s system. The same “Apply” button can conceal very different development scopes.
If pricing requires an individual risk assessment, do not disguise an application as an instant purchase. Underwriting — assessing risk and deciding on insurance terms — remains within the process agreed by the insurer. The website shows the application’s review status and the next step.
| Launch format | What the business commissions | What to establish before estimating |
|---|---|---|
| Application handed over to a manager | A form, an enquiry queue, notifications and a CRM connection | Who is responsible, what data is needed and when the customer receives a response |
| Handover to the insurer’s existing service | Product pages and an agreed handover to the purchase process | Where the journey ends, how status is returned and who supports the customer |
| Purchase on your own website | Quoting, payment flow, document issuance and delivery through integrations | Whether the necessary API operations, test environments and failure handling are available |
Describe the scope of the first launch in terms of a completed sale of one product. If an external system does not provide confirmation of issuance, a customer account area will not close that gap. Check this dependency before commissioning development.
The calculator must return a reproducible quote
Determine the source of pricing: the insurer’s API, a separate calculation service or agreed rules. An API is an interface for exchanging data between systems. The designated server-side system confirms the amount before payment; the calculator in the browser is not enough.
The price should be linked to the calculation parameters, quote identifier and version of the terms applied. If the insurer sets a validity period for the quote, the website must take it into account. Changing a parameter requires recalculation, not replacing the amount in a payment request that has already been created. The customer sees what has changed and completes the agreed confirmation step.
An insurance calculator also needs a flow for cases where no result is available: the service is unavailable, the product does not support the entered parameters, or clarification is required. Choose an action for each case: retry the request, pass on the application or offer another channel. An “error” message with no way forward shifts a task to support that could have been resolved at the prototype stage.
The insurer’s product and compliance teams determine how contract terms are accepted, which confirmations are required, underwriting decisions, when cover begins and how long data is retained. The developer implements the agreed model and the way its steps are recorded, rather than setting universal insurance rules.
Do not treat payment and policy as a single status
Separate the quote, order, payment and document in the technical model. Each entity needs its own identifier and source of confirmation. The payment system reports the outcome of the financial transaction; the insurer’s system reports the outcome of issuance. CRM, or customer relationship management software, helps the team manage the process.
How to obtain the payment outcome
The browser returning to a “Thank you” page should not be the sole basis for changing the payment status. You need a server-side mechanism supported by the chosen provider: an event notification or a transaction check through the API. A webhook is a notification that an external service sends to the website’s server. Its origin and integrity are checked according to the provider’s documentation.
For example, Stripe’s webhook handling documentation describes signature verification, repeated deliveries and the absence of a guaranteed event order. This illustrates integration requirements; it is not a recommendation of a payment service for a Ukrainian merchant. The contractor must check equivalent mechanisms for your particular provider and agree on how the website will recover missed confirmations.
What to show before issuance is complete
Once payment is confirmed, the website proceeds to the next permitted step in the agreed model. If issuance takes place separately, the customer needs a pending status, an order number and a way to get help. Do not display “policy issued” until the corresponding confirmation is available. Likewise, a technical payment status does not, by itself, determine when insurance cover begins.
The policy issuance integration must return not only a file but also data that allows the outcome to be reconciled with the order. Agree on where the original document is stored, how to retrieve it again and who investigates discrepancies. A failed email must not turn a successful issuance into a new order.
Design for recovery, not another purchase
A hypothetical example: a customer pays for an order, the website receives confirmation, but the issuance request ends without a response. The response may have been lost after the document was created. To avoid a duplicate, check the outcome using the identifier before performing the agreed retry action.
Protection against duplicate operations is needed in several places: when creating a payment, receiving notifications and calling the issuance service. Idempotency means that repeating the same operation does not create a new business outcome. Stripe provides an idempotency key for API request retries; however, this does not replace tracking received events or guarantee the same behaviour from the insurer’s API.
When commissioning development, require a separate description of retry behaviour: which requests can be repeated, with which identifier, and how an unknown outcome is checked. If the API lacks the necessary protection, agree on an alternative: a status check, a uniqueness check or manual investigation. Disabling a button does not prevent server-side duplicates.
The operations team needs a discrepancy queue: “payment confirmed, issuance unconfirmed” and “document ready, delivery failed”. Each entry must have an owner and an available action. Compare providers’ terms separately: the article on the total cost of payment gateways helps distinguish a service’s transaction fees from the cost of integrating and supporting it.
Set access boundaries for documents
Access to documents is checked for the specific user and the specific object on every request. OWASP recommends least privilege, deny by default and permission checks on every request. A hidden button or a complex file address therefore does not replace server-side controls. During acceptance testing, check direct URLs, downloads and attempts to open another customer’s order.
Divide support roles by task as well: viewing payment status, resending an authorised notification or escalating a problem to a specialist. Full access to all data should not be a prerequisite for answering a simple question. Agree on separate rules for logs, analytics and deletion. Send permitted stages and identifiers to marketing events, not application forms or documents.
Use end-to-end scenarios for acceptance testing
A demonstration of a successful payment does not prove that the sales channel is ready. Insurance website acceptance testing must cover both the customer journey and support work after a failure. Prepare scenarios using test data and providers’ test environments.
- Run through the quote calculation, change a parameter and check which quote and amount the payment system receives.
- Test successful, declined and interrupted payments. Close the browser after payment and check the server-side outcome.
- Redeliver a notification and change the order of test events. Make sure the order is not duplicated and an older event does not reverse a confirmed status.
- Simulate an unknown outcome from the issuance service. Check outcome lookup, the discrepancy queue and continuation without another payment.
- Check delivery of the completed document, denial of access to another customer’s data and the actions available to each support role.
- Follow the same journey on a phone, using a keyboard and after reconnecting. Record whether the next step is clear.
Separately, check interface messages against the insurer’s product decisions. An interface state specification prepared before development helps agree in advance on waiting, failure and continuation. At acceptance, you need evidence of how the implemented website behaves, not just mock-ups.
Estimate the project by integrations, not page count
Start the project schedule with checks of documentation, test access and the operations available in the insurer’s systems. Then add a journey prototype, development, integration testing and support preparation. The timeline depends on the readiness of these dependencies and the speed of product approval.
In the budget, separate planning, design, calculator and data exchange programming, the payment flow, issuance and delivery, access control, testing and team training. Account separately for hosting, monitoring, paid services and subsequent integration updates.
GL.ua (Glyanets) develops Drupal websites, designs their interfaces and supports their continued development after launch. For an insurance channel, discussion of the platform must go hand in hand with checks of external systems: the CMS manages the web application but does not replace the insurer’s product logic.
To discuss insurance website development with GL.ua, prepare the product for the first launch, a diagram of the current purchase process and documentation for the available integrations. This provides a basis for discussing the scope of work, a prototype and a verifiable launch outcome.
Just one step to your perfect website



