Overview

Who the key belongs to, its limits and today's usage, the balance payouts are paid from, and the bank codes payouts accept.

Send KES to M-Pesa, Airtel Money, Till (Buy Goods), PayBill and Kenyan bank accounts, paid from your USDC balance. Quote first, then create, then follow the status.

Check who owns a phone number or bank account before you pay it.

Everything that moved money in the workspace (API payouts and anything else on the account), with receipts you can send to recipients or auditors.

A record of everything that happened to your objects. The same events your webhooks receive; read them here to catch up after downtime.

Manage where we send events, from code. The Console does the same; use whichever suits your deploys.

Test-only helpers: top up your test balance and force a test payout into any status. They answer NOT_FOUND to live keys.

Where money can come from and go to right now: countries, methods, mobile money operators and per-transaction limits.

The prices AutoPayKe publishes, and an itemised quote for any amount, the same figures the app charges against.

The public side of a payment link: what the payer sees, paying it, and following the payment. No account is needed to pay.

Money in: add funds to an AutoPayKe balance from mobile money, card or bank transfer, then follow the top-up until it is credited.

What the account holds, what it can send and withdraw, and anything on hold.

Saved places to send money out to: mobile money numbers and bank accounts, with the name on the account checked before you save it.

References to cards used for top-ups: brand and last four digits only. Cards are saved by the hosted checkout, never by posting card details.

Ask anyone to pay you: create a link, share it, and see when it's paid. The payer side is under Payment links (payer).