Commerce
Premium collection
How recurring premiums are charged, retried, and reconciled across payment methods.
On policy creation, a billing schedule is created from the plan's frequency (monthly, quarterly, annual). The collection engine handles everything from there.
Supported methods#
| Method | Gateway | Status |
|---|---|---|
| Card (debit/credit) | Paystack | MVP |
| Bank transfer | Paystack / Flutterwave | MVP |
| Payroll deduction | Internal schedule | MVP (HR channel only) |
| Direct debit mandate | Paystack Dedicated NUBAN | Phase 2 |
| Wallet | Flutterwave / Moniepoint | Phase 2 |
| Mobile money | MTN MoMo / Airtel Money | Phase 2 |
Recurring logic#
A daily job identifies policies due. On success the premium ledger updates, premium.paid fires, and the member is notified. On failure the engine retries at 24h, 72h, and 7d.
Grace and lapse#
After three failed attempts the policy enters a 7-day grace period. If still unpaid, it lapses and a policy.lapsed event fires. Your UI can offer in-app re-collection at any point.
Use
lapse_risk_score on the policy to drive proactive member outreach before the grace window even opens.