Last checked
Check six things on the provider's own pages: a currency or country table, a channel list for your market, a compliance guide for your country, a sandbox, a go-live page and a date. Ignore plugin lists and blog posts. If one step is missing, treat the country as unconfirmed. Checked on 3 November 2026.
Imagine a client in Kampala forwards you a plugin page. It lists 13 countries, Uganda among them, so you promise a two week build. In week one you find the provider wants documents your client's company never filed.
Plugin authors write what worked for their own customers. A provider's page says what the provider will support. Those are different promises, and only the second one carries a contract.
This page gives a six step check that uses official pages only. It is the method behind every row on our African payment rails matrix.
To build with the result, the Payment Integration for Developers course teaches sandbox through go-live.
Get weekly developer tips
Join 25,000+ developers. Practical guides, job tips, and new content — straight to your inbox.
No spam. Unsubscribe anytime.
Imagine a developer in Kigali asks whether Paystack works for a Rwandan shop. Run the six steps.
The sources disagree. So Rwanda is unconfirmed: we publish no row, and we would tell the Kigali developer to ask Paystack support in writing before quoting the shop. Disagreement between a provider's own pages is a finding, not noise.
When you hit a red flag, ask the provider's support the exact question in writing, and keep the reply with the date.
Do not stop. Run a sandbox spike for one day: register, create keys, send one test charge. If the sandbox works, ask for the production document list before you quote the client. Then price the delay into the plan.
Read sandbox to production across African payment rails for the approval step on each rail, and Paystack mobile money provider codes for the codes, and Paystack Pesalink in Kenya for the bank transfer channel. If you want the integration done for you, see payments integration at Mctaba Labs. To learn it yourself, take the Payment Integration for Developers course.
STK push, C2B, B2C, callbacks and reconciliation, built in a live four-week course with code review.
See the payments course