About AutoPayKe
The product, the chain and the account API behind the AutoPayKe apps.
AutoPayKe moves money between M-Pesa, Kenyan banks and USDC on Avalanche. People and businesses use the app to top up from M-Pesa, pay any Till or PayBill, pay farmers in bulk and cash out. The same system is open to developers over a JSON API.
What you can build
Show live pricesQuote the exact fee for any amount before your customer commits, from the same settings every charge uses.Check live coverageKnow which operators, Tills, PayBills and limits work right now, instead of hard-coding a list.Collect paymentsCreate a link anyone can pay by M-Pesa, with the money landing in your AutoPayKe balance.Top up a balanceStart an M-Pesa prompt and follow it, stage by stage, until the money is credited.
How the API is organised
| Area | Auth | What it covers |
|---|---|---|
| Capabilities | Public | Countries, methods, operators and limits that are live now |
| Fees | Public | Published prices and itemised quotes |
| Payment links (payer) | Public | Viewing and paying a link, following the payment |
| Top-ups | Bearer | Money in by mobile money, card or bank transfer |
| Balance | Bearer | What an account holds, can send and can withdraw |
| Payout accounts | Bearer | Saved M-Pesa numbers and bank accounts, with name checks |
| Payment requests | Bearer | Creating and cancelling payment links |
Principles
- One price, everywhere. The docs, the app's confirm screen and the charge all read the same fee settings. If a price changes, every one of them changes together.
- No card details, ever. Cards are paid on a hosted checkout. Any request that contains a card number is refused before it reaches business logic.
- Coverage is data. Methods come and go as partners go live or pause. Ask /capabilities rather than assuming.
- We never hold the money. Balances live in each person's own smart wallet on Avalanche C-Chain. See On-chain contracts.