Insurance your customers buy without leaving your app.
Your channel already owns the moment a customer books a trip or places an order. MicroFlow turns that moment into a policy, routes it to the right insurer, and settles your commission on the same reconciliation run. One integration, three markets live today.
One flow, from a moment inside your app to the commission on your account
Distribution that is already live in three markets.
Green SM sells trip, food delivery, and express delivery cover inside its app across Vietnam, Indonesia, and the Philippines. MicroFlow runs the distribution: cover embedded at the point of purchase, each sale routed to the right underwriter, and premiums reconciled automatically at period close. Underwritten by PVI in Vietnam and by regional carriers including Oona across Indonesia and the Philippines.
One embedded engine, three markets, multi-insurer from the first policy.

Everything between a customer tap and a settled account.
A channel plugs in once. MicroFlow handles the selling, the insurer rules, and the premium matching afterwards.
Multi-insurer routing.
01Every sale is sent to the right insurer by quota caps and allocation rules, so capacity is spread and no single insurer becomes a bottleneck as volume grows.
Embedded in the channel.
02Cover is offered inside your app the moment a customer books a trip or places an order, part of the flow they are already in, not a separate journey they have to go and find.
Speed to launch a cover.
03Product types for trip, food delivery, and express delivery are configured on the platform, so a new cover goes live on connections that already exist rather than a fresh build.
Real-time reconciliation.
04Premiums are matched to sales and each period is closed automatically, on a record you can audit, so commissions and payments come out right without a manual month-end.
One integration, then everything after is configuration.
The first question a partnerships team asks is what this costs their engineers. The answer is one integration, and it is the last one.
One integration
01Your app connects once to the platform. Issuance, routing, and reconciliation run on our side of that boundary, so your engineers own a single surface rather than one per insurer.
New cover, no new build
02Adding a cover type, a market, or an underwriter after you go live is a configuration on the platform, not another release on your roadmap.
Built on connections already live
03You are connecting to the same integration fabric that runs the live markets today, not to a first implementation being built around you.
A revenue line, not a cost line.
Distribution only works for a channel if the economics are legible. Three things are fixed by the model, whatever the commercial terms turn out to be.
Rates and terms are set per channel in the partnership conversation, not published here.
From first conversation to first policy.
Tell us about the channel.
01Where your customers buy, which moments cover naturally fits, and which markets you already run in.
We map the products.
02We match cover types and underwriters to your channel on the multi-insurer routing model, as volume grows.
Integrate once, then run.
03A single integration to the platform. MicroFlow carries issuance, routing, and reconciliation from there.
Go live and close clean.
04Sell inside your app, and let real-time reconciliation keep every period audit-clean from the first day.
Turn a moment in your app into a policy.
Tell us how your customers buy today, and we will show you where cover fits inside it and what it earns.
Underwriting partners · How we partner