Skip to content

Payouts ​

When a season's index triggers, a payout is the money owed to the policyholders in an affected area. This area runs payout runs (batches of computed payouts) and configures how money is sent, through payout methods and payout gateways.

Before you start ​

  • A completed analysis for the book,
  • policyholders enrolled,
  • and, to actually disburse, a payout gateway configured (see below).

Create a payout run ​

Choose Create run and pick a completed analysis, a year, and a season. The platform builds a preview: one row per eligible policyholder, each amount computed from their livestock (their TLU) and that season's index outcome. In plain terms, the payout is the index's payout rate applied to each policyholder's sum insured.

The run lifecycle ​

preview  →  approved  →  paying  →  completed        (or cancelled)
  • Preview: review and adjust. You can regenerate the preview, exclude or include individual rows, or cancel the run.
  • Approve: locks the run for payment.
  • Pay: disburse all pending at once, or row by row. Each time you pay, you pick a payout gateway (the default is preselected).
  • Completed once the payments are done.

Each row moves through pending → processing → paid (or failed), and can be excluded from the payable set while the run is still open.

Read a run ​

The run detail shows:

  • Headline figures: estimated total payout, beneficiaries, amount paid, and status, with a breakdown by pending, processing, paid, failed, and excluded.
  • Rows: each policyholder (a link to their record) with their phone, their area (a link), mobile-money provider, TLU, sum insured, the estimated payout and its rate, and the status. Row actions include Pay / Exclude / Include and an Estimated premium view.
  • Paid list export (PDF or Excel) of the paid rows, once at least one row is paid.

NOTE

The estimated premium on a row is the cost of cover from the current pricing product, shown for context only. It is not part of the payout and is never deducted from it.

NOTE

In the current build, disbursement runs through a Simulation gateway: money movement is simulated for testing rather than sent for real. Configure a real gateway (below) when the programme goes live.

Payout methods: how people receive money ​

A payout method is a recipient network or wallet a policyholder uses to receive money (for example OPay or MTN MoMo). The methods area is the catalogue of the networks used in your programme; active methods can be chosen on policyholder records and are copied onto each payout row. To add one, pick a network from the registry, give it a label, choose a country, and set it active.

Payout gateways: how the project sends money ​

A payout gateway is the integration or account the project uses to actually send money out. A gateway declares which methods and country it can serve, and one gateway is the default (preselected when you pay a run). A built-in Simulation gateway lets you test the whole flow without moving real money. To add one, choose a gateway type, label it, pick a country and the methods it pays, enter its credentials, and set it active (and optionally default).

TIP

Method vs. gateway: a method is where a person receives money; a gateway is what the project sends it through. Paying a run needs at least one active gateway, without one, the pay step is blocked.

How payouts connect ​

  • Policyholders: every row is a policyholder; excluding and including rows decides who is paid this run.
  • Index & pricing: a run is built from a completed analysis and its product. Each amount is the policyholder's sum insured (TLU times sum insured per TLU) multiplied by the index payout rate, so the drought index decides whether and how much each person is paid.
  • Dashboard: a run's totals feed the dashboard payout figures.

Troubleshooting ​

SituationWhat to do
Can't create a runThere's no completed analysis for the book, run a pipeline first.
Pay is blockedNo active payout gateway, configure one.
Paid-list export disabledNo rows are paid yet.