← Back

Country payment guide

Accept payments in Nigeria

Nigeria needs careful PSP selection because cards, bank transfers, USSD, wallets, pay-by-bank flows, and local settlement can behave differently by provider. Small merchants should compare Paystack, Flutterwave, bank-led options, and other local or regional PSP routes based on onboarding fit, dispute handling, settlement, developer support, and business category acceptance.

Which PSPs and payment routes can you explore in Nigeria?

Existing research for Nigeria includes Paystack, Flutterwave, Interswitch, Unified Payment Services (UP), OPay, PalmPay. Explore their products and local payment methods, then use your business and company location to narrow the enquiries.

No local company, or no clear contact route?

These are research leads, not approval or industry-support guarantees. Tell us the market and your company location so we can help you explore further.

8Channel recordsPublic directory entries
AfricaRegionNG
Medium, verify entity and documents, Usually requires a local entityOnboardingFrom structured fields
T+1, Real-time / T+0SettlementVerify on detail pages

Curated market guide

Nigeria PSP routes to verify first

Which PSPs, wallets, and bank routes should a merchant ask first for Nigerian cards, wallets, bank transfer, and local aggregators?

4
local_psp_or_aggregator · curated

Nigerian PSP / aggregator shortlist

PaystackFlutterwaveMonnify (TeamApt Limited)SeerBit

Use when you need cards, bank transfer, wallets, and payment links through a local PSP evaluation.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
acquirer_or_bank · curated

Bank/acquirer or switch route

InterswitchUnified Payment Services (UP)UBA U-CollectGlobal Accelerex

Use when direct acquiring, local switch connectivity, or bank merchant services are important.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
direct_scheme_or_wallet · curated

Wallet and local aggregator route

OPayPalmPayPagaMoniepoint

Use when wallet or agent-network adoption matters and direct merchant or PSP partner access must be verified.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
international_psp · curated

Cross-border Africa PSP route

FincraKlashaKorapayPayaza Africa Limited

Use when the merchant is cross-border or multi-country and needs Nigeria plus broader Africa coverage, subject to KYB checks.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
KYB prep

Documents to prepare

  • Company registration and Nigerian entity or foreign onboarding question
  • Beneficial-owner and signatory ID
  • Website/app URL and product category
  • Bank account and settlement-currency requirements to verify
  • Refund, dispute, and fraud-monitoring process
Due diligence

Questions to ask

  • Can my current merchant entity onboard for this market, or is a local company required?
  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
Contact route fallback

If the official contact route is unclear

If public contact details are not specific enough, ask LocalPayMap to identify the right official form, PSP sales route, or local acquiring partner before committing engineering work.

  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?

Merchant questions before choosing a provider

Use these questions to separate customer payment fit from PSP onboarding, settlement, pricing, support, refunds, disputes, and compliance details.

How customers may pay locally

Cards, bank transfer, pay-by-bank, USSD, wallets, and account-transfer style flows can all matter. The mix depends on whether the merchant sells ecommerce, digital goods, subscriptions, marketplace services, or offline-to-online products.

Local entity and settlement checks

Ask whether Nigerian incorporation, local bank account, BVN or director documentation, local settlement, or cross-border settlement is required. Confirm NGN settlement, reserves, FX, and payout timing.

PSP selection notes

Compare Nigerian PSPs, African regional PSPs, bank or switch routes, wallet options, and global PSPs where available. The strongest route is not always the cheapest; reliability, reconciliation, and support often matter more.

Documents and KYB checks

Prepare company registration, beneficial owner details, tax or bank documents when the provider asks for them, website review, product category, refund and chargeback policy, expected volume, and customer support details. Treat this as a readiness checklist, not a guarantee that every provider will request the same package or approve the account.

Integration checklist

Confirm these items before committing engineering time or signing provider terms.

Merchant checklist before integration

Use these questions before committing engineering time or signing a provider contract.

  • Confirm cards, bank transfer, USSD, wallet, and pay-by-bank coverage.
  • Ask if Nigerian entity or local bank details are required.
  • Verify NGN settlement, cross-border payout, reserves, and FX handling.
  • Check refunds, failed payments, chargebacks, and reconciliation exports.
  • Confirm developer docs, sandbox, webhooks, payment links, and support SLA.
  • Request official pricing or a written provider quote.

How customers actually pay here

The most common online payment in Nigeria is a bank transfer. Buyers move money from their banking app to a merchant account or virtual account, and the payment is matched automatically, which is why so many checkouts show a transfer option first. The interbank instant payment service operated by the national switch is what makes this feel immediate. Cards are widely used too, with Verve as the domestic scheme alongside Visa and Mastercard. Wallets such as OPay, PalmPay, Paga and Kuda have taken large user bases, particularly among younger and mobile-first buyers. USSD payments still matter because they work on basic handsets. Cash and cash on delivery persist in ecommerce, and agent networks handle cash in and out for people far from a branch.

  • Instant bank transfer is the most common way buyers pay online.
  • Verve is the domestic card scheme and sits alongside Visa and Mastercard.
  • Wallets including OPay, PalmPay, Paga and Kuda have very large user bases.
  • USSD payments still reach buyers without a smartphone.
  • Agent networks handle cash in and out for people far from a bank branch.

Next actions

Next actions for Nigeria

Use these internal paths to move from market research to provider outreach without assuming eligibility, pricing, settlement, or local-entity access.

Questions merchants ask

Which Nigeria payment methods should be checked first?

Cards, bank transfer, USSD, pay-by-bank, and wallet routes are common checks, but the priority depends on customer segment and provider coverage.

Are Paystack and Flutterwave the only options?

No. They are major regional PSPs, but merchants may also compare bank-led, switch, local gateway, and aggregator routes depending on their needs.

Do foreign merchants need a Nigerian entity?

Some provider routes may support foreign merchants, while others require local company or banking details. Confirm this before integration.

What should SaaS or subscription merchants ask?

Ask about recurring billing support, card tokenization, failed-payment retries, authorization rules, chargebacks, and renewal reconciliation.

Can public PSP pricing be used as final pricing?

No. Public pricing is useful for screening only; final pricing depends on sector, volume, route, settlement, and contract.

Do I need a local company to accept payments in Nigeria?

Not always. Several local gateways onboard businesses registered abroad for card and bank transfer collection, subject to their own accepted country list and enhanced checks. What generally requires a local entity is naira settlement into your own local bank account, virtual account numbers in your name, and some wallet and agent products. Ask each provider about your country of registration before you build anything.

Which payment method should I add first in Nigeria?

Add a local gateway first, because one integration gives you bank transfer, cards, USSD and wallets together. Within the checkout, make instant bank transfer the most visible option, since that is the habit most buyers already have. Enable Verve alongside Visa and Mastercard so domestic cards route locally, then confirm which specific wallets are live on your account.

How long does settlement take in Nigeria?

Naira settlement to a local account typically runs on a short rolling cycle defined in your contract, and new merchants often start slower until history builds. Foreign-currency payout is different: it depends on your provider's permissions and on currency availability, so it can take noticeably longer. Ask for the cycle in writing for each currency, including holiday handling and first-payout timing.

Public sources