Guides & tutorials
Complete walkthroughs that build the application around the API, not just the call.
Each guide builds what goes around an API call: an order fulfilled once, a refund flow, a renewal job. If you have not made an API call yet, start with the payments quickstart.
Where to start
Follow this order if you are building from nothing. Each guide leans on the one before it.
| Order | Guide | Level | What you get out of it |
|---|---|---|---|
| 1 | Accept a payment | Beginner | An order that is fulfilled exactly once, whatever the customer does |
| 2 | Mobile Money checkout | Beginner | The handling for a payment a human confirms on a handset |
| 3 | Integrate with React | Intermediate | A frontend that never touches your secret key |
| 4 | Handle refunds | Intermediate | A support flow that can give money back safely |
| 5 | Recurring billing | Intermediate | Subscriptions, renewals and dunning built on plain payments |
| 6 | Go live | Advanced | The checklist before you switch to production keys |
All guides
Related pages
- Accept a paymentThe order lifecycle around a payment, from creation to fulfilment.
- Mobile Money checkoutWhat really happens between the prompt and the confirmation.
- Integrate with ReactWhere the secret key lives in a React or Next.js app.
- Handle refundsDecide the amount, follow the refund, reconcile it.
- Recurring billingPlans, cycles, renewals and dunning on top of the Payments API.
- Migrate from another providerMove existing volume without double-billing or downtime.
Recipes are the other half
A guide explains a problem. A recipe is one finished implementation in one stack, ready to copy. When a guide tells you what the return page must check, the recipe shows you that page written in Next.js or Laravel.
Keep Konsole open while you follow a guide
Konsole shows every request going out and every webhook coming back, in real time. Most of the debugging these guides warn you about turns into a ten second read there.