Accept DPO Pay
without building the integration
DPO Pay is a pan-African payment gateway operating in more than 20 African countries. It accepts card and mobile money payments in a wide range of local currencies, which makes it the practical option for merchants selling across several African markets from one storefront rather than standing up a separate gateway per country.
- KES
- TZS
- UGX
- RWF
- ZMW
- BWP
- ETB
- ZAR
- NGN
- USD
- EUR
- GBP
- Region
- Pan-Africa
- Methods
- 2
- Credentials
- Server-side only
- PaymentHood fee
- None
- Status
- Live
DPO Pay in summary
- Coverage
-
- Kenya
- Tanzania
- Uganda
- Rwanda
- Ethiopia
- Zambia
- Malawi
- Zimbabwe
- Botswana
- Namibia
- Mozambique
- Mauritius
- South Africa
- Nigeria
- Ghana
- Côte d'Ivoire
Among the markets DPO Pay serves — their own list is authoritative (opens in new tab).
- Currencies
-
- KES
- TZS
- UGX
- RWF
- ZMW
- BWP
- ETB
- ZAR
- NGN
- USD
- EUR
- GBP
Among those supported. Which ones your account can charge in depends on its registered country.
- Fees
- Set and billed by DPO Pay, and published on their pricing page (opens in new tab). PaymentHood adds nothing on top, at any volume.
- Official resources
- Website (opens in new tab) · Developer docs (opens in new tab)
Written against DPO Pay's own documentation on . This page deliberately states no fees, no counts and no completeness claims, because those change without notice — for anything you are about to build on, DPO Pay's own documentation (opens in new tab) is the authority.
What your customers can pay with
Every method below runs through the same PaymentHood checkout. Turning one on or off is a dashboard setting, not a code change.
Cards
Visa and Mastercard credit and debit cards
Mobile money
The regional wallets in each market DPO covers
What PaymentHood handles for you
A direct DPO Pay integration is not just an API call. These are the parts every team ends up rebuilding — and the parts PaymentHood ships already done.
- Credentials
- Company token and service credentials, held server-side in PaymentHood
- Webhook security
- Callback validated and reconciled against the transaction record before the order is released
- Payment verification
- Server-side transaction verification against DPO before fulfilment
- Idempotent charge creation, so a retried request never double-charges a customer
- Automatic failover to another configured provider when DPO Pay is unreachable
- One reconciliation view across DPO Pay and every other provider you run
- Provider credentials never reach the storefront or the customer's browser
- Adding or switching a provider later is a dashboard change, not a re-integration
Use DPO Pay on your platform
Install the free PaymentHood plugin for your store, then enable DPO Pay in your dashboard.
Connecting DPO Pay takes three steps
Open your DPO Pay account
Register directly with DPO Pay and complete their onboarding. Funds settle from DPO Pay into your own bank account — PaymentHood never holds merchant money.
Add the credentials to PaymentHood
Paste your DPO Pay API credentials into the PaymentHood dashboard. They are stored server-side and never exposed to your storefront.
Enable it at checkout
Install the PaymentHood plugin for your platform, paste your PaymentHood API key, and DPO Pay appears as a payment option. Test in sandbox, then switch to live.