Accept OPay
without building the integration
OPay is a Nigerian fintech with one of the country's largest consumer wallet bases, and its Cashier API lets merchants accept payment from that wallet as well as by card, bank transfer, USSD and agent reference code. The wallet reach is the reason to add it — those customers are already funded.
- NGN
- Region
- Nigeria
- Methods
- 5
- Credentials
- Server-side only
- PaymentHood fee
- None
- Status
- Live
OPay in summary
- Coverage
-
- Nigeria
Among the markets OPay 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 OPay, 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 OPay'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, OPay'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.
OPay wallet
Payment from the customer's OPay balance, including QR
Cards
3-D Secure card payments
Bank transfer
Transfer confirmed against the order
USSD
Bank shortcode payment
Agent reference
A reference code paid at an agent location
What PaymentHood handles for you
A direct OPay integration is not just an API call. These are the parts every team ends up rebuilding — and the parts PaymentHood ships already done.
- Credentials
- Merchant ID with public and private keys and request signing, held server-side in PaymentHood
- Webhook security
- Signed callback, validated before an order is released
- Payment verification
- Server-side order query against the OPay API before fulfilment
- Idempotent charge creation, so a retried request never double-charges a customer
- Automatic failover to another configured provider when OPay is unreachable
- One reconciliation view across OPay 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 OPay on your platform
Install the free PaymentHood plugin for your store, then enable OPay in your dashboard.
Connecting OPay takes three steps
Open your OPay account
Register directly with OPay and complete their onboarding. Funds settle from OPay into your own bank account — PaymentHood never holds merchant money.
Add the credentials to PaymentHood
Paste your OPay 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 OPay appears as a payment option. Test in sandbox, then switch to live.