How to Accept Payment on a Nigerian Website

Most guides on this topic stop at "install the plugin". That is the easy half. The decisions that determine whether payments help or hurt your business are which channels you offer, how your checkout is laid out, how confirmation reaches your order system, and what happens when money and orders disagree.

This guide treats payment as a system rather than a button. The individual channels have their own articles; here the focus is choosing and assembling the whole thing for a Nigerian website.

What you need before you can accept a single naira

Payment providers in Nigeria verify businesses before they release full settlement and higher limits. Gathering these first saves a launch delayed by paperwork:

• Business registration. A CAC business name or limited company, with the registration documents to hand. Requirements differ for a business name and a company; check the current position with the Corporate Affairs Commission.
• A corporate bank account in the business name, matching the registration documents.
• Director or owner identification and, in most cases, a BVN linked to the settlement account.
• A working website with real content, including contact details, a physical address, and clear refund, delivery and terms pages. Providers check these.
• A business email on your own domain. A free webmail address slows verification and weakens trust.
• Tax identification where the provider requests it.

Sole traders sometimes start on a personal account and a starter tier. It works for testing, but commercial volume through a personal account risks restrictions and makes bookkeeping painful. Register the business early.

Which payment channels should a Nigerian website offer?

In brief: a Nigerian website should offer bank transfer and card as standard, add USSD when its customers include people without cards or data, and consider pay-on-delivery only for physical goods within a delivery network it controls. Everything else is a special case.

Do not offer every option. Three well-ordered choices convert better than seven. Put the channel most of your customers use first.

Four ways to connect payments to your website

Most Nigerian businesses should use a plugin or a hosted checkout. Direct API work is justified when money must be split between vendors, held in wallets, charged on a schedule, or tied to a multi-step order process. That decision, and not the gateway brand, is what changes a quotation from hundreds of thousands to millions of naira.

How to choose a payment gateway: a decision framework

1. List your required channels. If USSD or recurring debits matter to you, shortlist only providers that support them for your customers' banks.
2. Check settlement speed and currency. Next-working-day local settlement is the common pattern; confirm the current cycle, and confirm how foreign-currency transactions settle if you take them.
3. Read the published fee schedule yourself. Percentages, caps on local transactions, international rates, transfer-out fees and any charges for virtual accounts. Model them against your real average order value.
4. Test the support channel before you need it. Send a pre-sales question and time the reply. Payment support quality shows up on your worst day, not your best.
5. Read the developer documentation. If your developer can find webhook verification, refunds and test cards in five minutes, integration will be smooth.
6. Check the failure experience. Make a deliberately failing test payment and see what the customer is told.
7. Confirm compliance fit. Your business category may have restrictions; ask before you build.
8. Check the exit. Can you export a full transaction history? Can you run two providers at once so a bad day does not stop sales?

Running a primary and a backup gateway is common practice for businesses whose revenue depends entirely on online payment. The cost is a second integration; the benefit is not being offline when a provider has an incident.

Designing a checkout Nigerian customers complete

The technical integration rarely loses money. The checkout does. Practical rules that suit Nigerian buying behaviour:

• Show the total in naira, including delivery, before the payment step. Surprise delivery charges are a leading cause of abandonment.
• Do not force account creation. Offer guest checkout with an optional account afterwards.
• Ask for a phone number, treat email as optional. Phone is the identity Nigerian customers actually use, and it is how you will contact them about delivery.
• Order the payment methods by real usage. If transfer carries most of your value, put it first.
• Label methods in plain language. "Pay with transfer (account number generated for this order)" beats "Bank transfer".
• Keep the form on one screen on mobile. Most of your traffic is a mid-range Android phone on mobile data.
• Show trust signals near the pay button: business address, phone number, refund policy, delivery timeline.
• Confirm loudly. A visible success screen plus a WhatsApp or SMS message stops "did my payment go through?" enquiries.
• Handle failure gracefully. Keep the cart, explain the likely reason, and offer another channel.
• Never ask for a bank PIN or full card details outside the gateway's own form. Anything else looks like fraud to a cautious Nigerian buyer.

Confirmation, settlement, refunds and reconciliation

Confirmation. Never trust the browser. The customer's device returning to a success page proves nothing. Your server must receive a webhook, verify its signature, then independently call the gateway's verify endpoint with the transaction reference and compare the amount in kobo before fulfilling anything. Handle repeated events idempotently, and run a scheduled job that re-checks pending transactions in case a webhook was missed while your server was down.

Settlement. Money sits in your gateway balance, then settles to your corporate bank account on the provider's schedule. Do not treat the gateway balance as available cash until it has landed.

Refunds. Decide the policy before launch: what is refundable, within how long, and to which account. Refunds go back to the originating card or account, never to a different account a customer supplies by message. Publish the policy; providers check for it during verification anyway.

Reconciliation. Once a week, match three things: gateway transactions, bank settlements and your own order records. Differences come from refunds, chargebacks, failed-but-charged transactions, manual payments and fees. A business that reconciles weekly finds a problem while it is one transaction; a business that reconciles yearly finds a spreadsheet.

Records. Customer names, phone numbers and transaction histories are personal data under the Nigeria Data Protection Act 2023. Limit who can export them, secure the admin area properly, and check current NDPC guidance for your obligations. This is not legal advice.

What changes for Nigerian businesses

Transfer often beats card on value. Many Nigerian sellers see card used for smaller, impulse-level purchases and transfer used for larger, considered ones. A checkout that assumes card-first, as most international templates do, works against that pattern.

Trust must be earned on the page. Nigerian buyers have good reason to be careful online. A visible address, a working phone number, a real refund policy and a professional site do more for conversion than any discount.

Exchange rates affect your stack, not your prices. Hosting, SaaS subscriptions and some payment tooling are billed in dollars. Naira prices to customers are stable, but your costs move. Budget with a buffer.

Connectivity and power shape the flow. Sessions get interrupted. Save carts, allow customers to resume, and make order confirmation reachable by WhatsApp rather than only by email.

Chat is part of checkout. A large share of Nigerian orders start or end in a WhatsApp conversation. Payment links that confirm automatically let you keep the conversation without going back to screenshots.

Pay on delivery is a commercial decision, not a technical one. It raises conversion and raises losses from refused deliveries. Limit it by value, by location and by customer history.

Fraud looks different here. Chargeback risk on local cards is lower than in Western markets, while confirmation fraud, fake transfer alerts and refund-to-another-account requests are the live risks. Design controls for the risks you actually face.

Example (hypothetical): a Port Harcourt training academy

Example (hypothetical): A professional training academy in Port Harcourt runs six-week certification courses priced between ₦120,000 and ₦450,000, with an option to pay in two instalments. Enrolment currently happens by WhatsApp; the admin officer posts the company account number, receives screenshots, and updates a spreadsheet. Two courses a month, roughly 40 students each.

The problems. Screenshot verification consumes hours around each enrolment deadline. Instalment tracking is manual and unreliable. Students who want to pay by card, particularly corporate sponsors, have no option. Nobody can say at a glance who has paid in full.

What it builds. The website gets an enrolment page per course with a hosted checkout offering transfer and card. Each student gets an account; a dedicated virtual account is generated for students on instalment plans so any payment is attributed automatically to their balance. Webhooks update enrolment status; a student's dashboard shows amount paid and amount outstanding. Corporate sponsors receive a payment link per invoice. The admin officer's spreadsheet is replaced by a paid-status report.

What changes (illustrative, not a claim). Enrolment confirmation stops depending on an officer being awake. Instalments reconcile themselves. Corporate clients, who previously delayed while requesting an invoice, pay from a link. The academy pays gateway fees it did not pay before and, in return, stops paying in administrative hours and missed places. The build is a modest custom web application rather than a store platform, because the instalment and enrolment logic is specific to the business.

What it costs to accept payments (indicative)

All figures are indicative 2026 ranges; actual quotes vary with scope, vendor and exchange rate. Compare two or three written quotations on identical scope, and verify provider fees from their current published schedules.

When comparing quotations, insist that each one states whether webhook verification, server-side re-verification, refund handling and a reconciliation report are included. Quotes that omit them are not cheaper; they are smaller.

Implementation checklist

• CAC registration and corporate bank account in place
• Gateway account verified, settlement account confirmed
• Channels chosen and ordered by expected usage
• Integration method decided: plugin, link, hosted checkout or API
• Delivery charges calculated and shown before payment
• Guest checkout enabled, phone number captured
• Webhook endpoint live, signature verified, events idempotent
• Server-side verification before fulfilment, amount compared in kobo
• Order states visible to customers and staff
• Confirmation message sent by WhatsApp or SMS
• Refund, delivery and terms pages published
• Test transactions completed on card, transfer and USSD, including failures
• Weekly reconciliation routine assigned to a named person
• Admin access restricted and customer data handled under NDPA 2023
• Backup plan if the primary gateway has an incident

Mistakes to avoid

• Fulfilling orders on the browser's success page. Reason: it can be reached without a real payment; only server-side verification proves money moved.
• Offering card only. Reason: it ignores the channel many Nigerian customers prefer for higher-value purchases.
• Hiding delivery cost until the last step. Reason: it is one of the most reliable ways to lose a completed cart.
• Forcing account creation before payment. Reason: first-time buyers abandon rather than register.
• Using a personal bank account for business settlement. Reason: it risks restrictions, complicates accounting and looks unprofessional on statements.
• Skipping the refund and terms pages. Reason: providers check for them, and customers read them before trusting a new site.
• Leaving nobody responsible for reconciliation. Reason: mismatches compound silently until they are expensive to unravel.
• Choosing a gateway on fees alone. Reason: settlement speed, support and documentation quality cost you more in a bad week than a fractional difference in rate.
• Building custom payment logic without idempotency. Reason: duplicate webhooks create duplicate orders, duplicate dispatches and refund disputes.

Conclusion

Accepting payment on a Nigerian website is a sequence of decisions, not an installation. Register the business and open a corporate account first, because verification is the slow part. Offer transfer and card as standard, add USSD when your customers need it, and order the options by what people actually use. Choose the lightest integration that fits your flow, then spend the engineering effort where it matters: verified webhooks, server-side confirmation, clear order states and a weekly reconciliation someone owns. Get those right and payment becomes invisible, which is exactly what a customer at checkout wants it to be.

If you are adding payments to a new or existing Nigerian website, or your current setup still depends on screenshots and manual checks, Linestech can design the checkout, integrate the gateway and build the confirmation and reconciliation around it.

Frequently asked questions

Do I need a registered company to take payments on my website?

You need business documentation for full settlement and higher limits, and CAC registration is the usual route. A business name registration is often enough to start; a limited company may be required for certain categories or higher volumes. Confirm current requirements with your chosen provider and the Corporate Affairs Commission.

How long does it take to add payments to an existing website?

On a mainstream platform with an official plugin, configuration and testing can be done in a day or two once your gateway account is verified. A custom site with a hosted checkout typically takes a few days to a couple of weeks. Verification of the business is usually the slowest step, so start it first.

Can I take payments without a website at all?

Yes. Payment links generated from your gateway dashboard let you take payment in WhatsApp, Instagram or email with automatic confirmation. It is a good starting point for service businesses, though a website gives you catalogue, search visibility and a checkout you control.

Which is cheaper, a plugin or a custom integration?

A plugin is cheaper to build and maintain. A custom integration is justified only when you need behaviour a plugin cannot provide, such as splitting payments between vendors, holding balances, charging instalments or tying payment to a multi-step approval process. Pay for complexity you need, not complexity you might need.

How do I handle a customer who says they paid but my system shows nothing?

Search the gateway dashboard by amount, date and reference before anything else. If the gateway has no record, ask the customer for the transaction reference from their bank, not a screenshot. Most cases are a payment to the wrong account, a failed transaction that was reversed, or a webhook your system missed, which a re-check job should have caught.

Should I pass gateway fees on to customers?

Most Nigerian consumer businesses absorb them, because an added fee at the last step reduces completion. B2B and high-value services sometimes state fees separately. If you do pass them on, show the total early rather than adding it at the payment step.

Can one website use two payment gateways?

Yes, and businesses dependent on online revenue often do. One is primary, the second is a fallback when the first has an incident or a channel is unavailable. The cost is a second integration and a second reconciliation stream; the benefit is that a provider outage does not stop sales.

What is the safest way to take deposits and balance payments?

Generate a separate transaction for each stage, each with its own reference, and record both against the order. For repeat or instalment customers, a dedicated virtual account removes amount matching entirely, since any credit is attributed to that customer's balance.

Sources and further reading

Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.

• Corporate Affairs Commission (CAC)
• Nigeria Data Protection Commission (NDPC)
• MDN Web Docs — web platform reference
• Node.js documentation
• Baymard Institute e-commerce UX research