paynow-billpaylisted

# Paynow BillPay integration BillPay lets a **vendor** (a reseller with a prefunded wallet) pay bills and buy services on behalf of customers, and lets an **offline biller** receive those payments. Most integrations are vendor integrations. Payment flows here move real money and are checked in a joint go-live test (UAT), so correctness matters more than speed. Most of the rules below exist because breaking them either double-charges someone or fails UAT. `references/full-reference.md` is the source of truth (verified against developers.paynow.co.zw, 21 Sep 2026). Everything else in this skill is derived from it. ## 1. Work out which API the user needs | The user is… | API | Start with | |---|---|---| | An app, fintech, bank, shop or agent selling tokens, airtime or bill payments to its customers | **Vendor API** | §3–§6 below, `references/vendor-workflows.md` | | A service provider (school, club, council, SACCO) that wants BillPay to collect payments for it and tell it who paid | **Biller API** | §7 below, `references/biller-api.md` | | An *online* biller that wants payments processed in its own system | Neither. Tell them Paynow prefers online biller integrations and they should contact Paynow support. | — | If the user's stack is clear from context (e.g. a Laravel repo), use the matching template without asking. Ask only when neither the stack nor the role can be inferred. ## 2. Setup and authentication 1. **Credentials come from Paynow.** Vendors need a user with th