Flow A: Quote and Pay (prepaid)
Three calls: register, quote, pay. Inshuwa collects the premium through a gateway and the policy is issued automatically once the payment confirms — there is no separate issue call on this flow.
Use it when the customer accepts a price before buying, or when a quotation must persist in your system. If your account settles outside the platform, use flow C instead.
Set it once and every Try it out below is authenticated. It stays in this browser's local storage and is never sent anywhere but the API.
Step 1: Register the policyholder and vehicle
Keep the id from the response — it is the {id} in the next request, and the clientId on the quotation.
/policyholders/{id}/vehiclesPlayground
Authorization
Variables
Body
Send make, model, year, registration number, chassis number and the motorRiskCategoryId — read the categories from Products and pricing.
Step 2: Create the quotation
The response contains the quoteId. Include duration per the product's durationType.
To price the same vehicle across several products in one call:
/quotations/motor/comparisonPlayground
Authorization
Body
Step 3: Pay the premium — this issues the policy
Send payment.mobileMoneyAccountNumber for mobile money, or payment.cardDetails for card (the response carries a redirectUrl for the 3DS step). reference is your own unique transaction reference.
/payments/{quoteId}/payPlayground
Authorization
Variables
Body
The call comes back Pending while the payer approves it on their handset. When the payment confirms, the quotation becomes an issued policy — you do not call an issue endpoint.
Step 4: Poll until it settles
The transaction status carries the issued policy once the payment succeeds. That is your signal that cover is in force.
/payments/transactions/{reference}/statusPlayground
Authorization
Variables
Do not treat Pending as sold
Nothing is on cover until the status reads Success and a policy comes back with it. Poll, or handle the webhook.
Next: Policies and documents.