Accept Paga
without building the integration
Paga is one of Nigeria's longest-running mobile money operators, with a wallet and a nationwide agent network. Its merchant collection tools cover wallet payments, bank USSD and payment links, which reach customers who have neither a card nor a smartphone banking app.
- NGN
- Region
- Nigeria
- Methods
- 4
- Credentials
- Server-side only
- PaymentHood fee
- None
- Status
- Live
Paga in summary
- Coverage
-
- Nigeria
Among the markets Paga serves — their own list is authoritative (opens in new tab).
- Currencies
-
- NGN
Among those supported. Which ones your account can charge in depends on its registered country.
- Fees
- Set and billed by Paga, who publish current rates on their own site (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 Paga'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, Paga'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.
Paga wallet
The customer authorises payment from their Paga wallet
Bank USSD
One-time-use bank shortcode collection
Payment links
A shareable link created through the payment request API
Cards
Card payment through Paga Checkout
What PaymentHood handles for you
A direct Paga integration is not just an API call. These are the parts every team ends up rebuilding — and the parts PaymentHood ships already done.
- Credentials
- Principal, credential and API key with request hashing, held server-side in PaymentHood
- Webhook security
- Signed payment notification, validated before an order is released
- Payment verification
- Server-side transaction status query against the Paga API before fulfilment
- Idempotent charge creation, so a retried request never double-charges a customer
- Automatic failover to another configured provider when Paga is unreachable
- One reconciliation view across Paga 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 Paga on your platform
Install the free PaymentHood plugin for your store, then enable Paga in your dashboard.
Connecting Paga takes three steps
Open your Paga account
Register directly with Paga and complete their onboarding. Funds settle from Paga into your own bank account — PaymentHood never holds merchant money.
Add the credentials to PaymentHood
Paste your Paga 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 Paga appears as a payment option. Test in sandbox, then switch to live.