Collect payments
Accept Mobile Money, card, and bank transfer payments with Wajub — four integration approaches from zero-code to full API.
Wajub offers four integration approaches for collecting payments. The right one depends on how much control you need over the UI and how much code you want to write.
First payment in under 5 minutes
Jump straight to the Payments Quickstart — initialize, redirect, verify, and listen for the webhook. Come back here when you're ready to compare integration modes.
Related pages
Not sure which to choose?
Read How to accept a payment — choose your integration for a decision matrix comparing all four approaches by complexity, customisation, and use case.
Payment methods
Wajub supports Mobile Money, card, and bank transfer across 13+ African countries. See Payment methods & channels for the full country × operator coverage matrix, and Phone number formats for the E.164 requirements per operator.
API resources for Payments
Payments shares one API with every other product — these are the resources this product actually calls. Full parameters and responses are in the API Reference.
| Method | Endpoint | Used for |
|---|---|---|
POST GET DELETE | /payments | Create, list, retrieve, cancel a payment |
POST GET | /refunds | Issue and track refunds |
GET | /disputes | Chargebacks and dispute evidence |
POST GET | /customers | Returning-customer records |
POST GET | /payment-links | No-code Payment Links |
No product-specific header is required for standard Payments calls. If this payment is
attributed to a Sync subaccount, add X-Sync: acc_… — see Sync → API
resources.
After the payment
| Need | Where |
|---|---|
| Get real-time status updates | Webhooks |
| Refund a payment | Refunds |
| Handle a dispute or chargeback | Disputes |
| Manage returning customers | Customers |
| Understand webhooks vs polling | Webhooks vs Polling |
Related pages
Was this page helpful?