Calls to external systems go through a shared queue: with the data subject’s consent, retries after a failure and a request log. Each connection is set up for the insurer, because the contracts with operators and the account credentials belong to the insurer.
The address, keys and certificate of each system are set in the organization settings. The platform never calls registries in its own name.
A request the registry did not answer stays in the queue and is retried, and diagnostics show the cause of the failure.
A request about a person is sent only with that person’s consent and is logged together with the response.
Events for the accounting system and partners are first saved in the database and only then sent, so they are not lost on a restart.
Contract registration and data checks in national databases. Registration obligations are set for five countries.
Credit history and client checks with the data subject’s consent, sanctions lists with portfolio rescreening.
Online premium collection with card saving and reconciliation of operations with the gateway. Acquiring is connected under the insurer’s contract with the bank.
Signing of reports and documents on the server and with an employee’s key, timestamping and signature verification.
Accounting events from the full event dictionary are passed to accounting. The insurer maps events to accounts on its own.
Messages to clients and employees from the insurer’s templates in the recipient’s language.
Scoring models inside the system and claim notification parsing by a language model with a closed list of fields passed.
Cursor-based export of datasets to the warehouse with an audit of every export.
Banks, marketplaces and aggregators connect through the Partner API, webhooks and the purchase widget.
Tell us which registries, banks and accounting systems you work with. We will assess the connection and the timeline.