Verifies, decides,
settles, and proves.
One rules engine adjudicates every line of insurance, then settles the approved claims over mobile money or bank rails. AXK does not underwrite. It carries no risk of its own.
- claim_id
- string
- rule
- rule_id
- settled_via
- mobile money
Insurers keep the risk. AXK verifies the claim, prices the decision against rules, settles the approved ones over mobile money or bank rails, and writes an audit trail every party can read.
The case, without a fake stat.
No client logos, no traction numbers, no manufactured rating. Here is the market AXK starts in, the evidence the rules engine reads, and the design choices that make it infrastructure rather than a claims tool for one line of business.
AXK does not underwrite risk and does not hold funds.
Insurers keep the risk on their own balance sheet. AXK verifies the claim, prices the decision against rules, and instructs settlement over rails that already exist. The money never passes through it.
Read the corporate recordown or have used mobile money
Source: FinScope Rwanda 2024, Access to Finance Rwanda.
day contractual deadline, routinely missed
Source: Rwanda Today, reporting on health-facility invoice delays, 2022.
licensed private insurers
Source: National Bank of Rwanda, List of Licensed Insurers, January 2025.
- Hospital electronic medical records (EMR)
- Police accident reports
- Weather station feeds and rainfall indices
- Civil registry (death records)
- Insurer policy and benefit tables
A document is a pointer to a fact, not the fact itself.
A policy is a promise. A claim is the day it gets tested.
The built world an insurer covers, on one engine.
Mobile money is the payout layer, not a roadmap item
Most claims infrastructure assumes a bank account at the far end. In the markets we serve the phone is the account. AXK settles over mobile money as a first-class rail, so a payout reaches a farmer or a patient without anyone opening anything.
Evidence comes from local systems, not a portal we ask you to fill in
The engine reads medical records, police reports, weather indices and civil registries. It fits the workflows institutions already run rather than asking them to migrate onto ours. A system that requires everyone to change first never starts.
The same rules engine adjudicates health, motor, agriculture, property and life
Claims logic is written against a common schema. A new line of business means new rules and new evidence sources, not a second product. That is what makes this infrastructure instead of a health-claims tool.
Privacy-first, with an audit trail a regulator can read
A claim decision needs the facts of the claim, not a copy of the patient file. Access is scoped to the party that needs it, and every decision is written append-only. The insurer can reconstruct any payout. The regulator can inspect the process without taking the insurer at its word.
Five steps, every line of business.
Submit
A claim is filed by the party closest to the event. A hospital files from the encounter.
- Provider portal
- Insurer API
- Index trigger
Verify
The rules engine checks three things at once: is the policy in force and does it cover this, do the supporting documents hold up against the systems that issued them, and does the claim look like fraud. Evidence is read from the source system, not from an attachment.
- EMR
- Police reports
- Weather index
Settle
A claim that clears the rules and the fraud model is approved without a reviewer. Settlement is triggered over the rails that already exist: mobile money to a person, bank transfer to an institution.
- Mobile money rails
- Bank rails
- Settlement ledger
Route
A claim that is incomplete, disputed or high-risk is not rejected. It is routed to a human with the verification already done, the missing evidence named, and the rule that stopped it attached.
- Review queue
- Exception rules
- Case notes
Prove
Every decision writes an append-only record: what was claimed, what evidence was read, which rule fired, who approved it, what settled and when. The insurer sees its own book.
- Audit log
- Insurer dashboard
- Regulator view
Bring us a claim, a policy, or a queue that's stuck.
We'll walk through the pipeline against your own claims, your own rules, and the rails you already settle over. No sales script.