How to Accept Online Payments on a Nigerian Website: Methods, Gateways and Setup

What you need before you can accept payments online

Before any code or plugin, a Nigerian business needs four things: a gateway account that has passed compliance, a Nigerian bank account for settlement, a website served over HTTPS, and a decision about which payment methods and currencies to offer. Gateways will not activate live payments without the compliance step, so start it first. Requirements checklist:

• Business identity. Registered businesses supply CAC documents (business name or company registration), the owner's or directors' ID and BVN, and proof of address. Some gateways offer starter tiers for unregistered individuals with lower limits and fewer features; verify current rules on each provider's compliance page.
• Settlement bank account. A Nigerian naira account in the business's name for registered businesses. Foreign-currency settlement, where offered, has its own requirements.
• A website on HTTPS. Every gateway requires an SSL certificate on the domain; most hosting plans include one.
• Clear commercial pages. Gateways typically ask for visible terms, a refund or returns policy, contact details and a description of what you sell. These also matter for customer trust.
• Decide what you are collecting. One-off product payments, fees with a fixed amount, invoices with variable amounts, donations, subscriptions or deposits. The answer changes which integration route fits.
• Someone to own reconciliation. A named person who checks that gateway settlements match orders or invoices.

Which payment methods do Nigerian customers actually use?

Nigerian customers pay online with debit cards, bank transfers (increasingly through virtual accounts that confirm automatically), USSD codes, and wallets such as OPay and PalmPay. Card is convenient but many customers distrust card forms or have international spending disabled; bank transfer is trusted and near-universal; USSD works on any phone without data. A website should offer at least card and transfer.

Offer methods based on who your customers are, not on what the gateway can do. A B2B consultancy invoicing companies mostly needs transfer; a ticket site needs card and USSD for speed; a school needs transfer for large fee payments and card for small ones.

How to choose a payment gateway for your website

Choose a gateway by matching six criteria to your business: supported methods and currencies, compliance fit for your business type, fees at your typical transaction size, integration options for your website platform, settlement timing and reliability, and the quality of reconciliation tools and support. For most Nigerian SMEs, Paystack and Flutterwave are the default shortlist; Interswitch, Monnify and Remita suit specific cases.

Fees change and differ by method, so read the current pricing page of each provider before deciding. As a pattern, local card fees have been a small percentage plus a fixed component with a cap per transaction, and international cards cost more; treat any figure you read elsewhere as indicative until verified. Running two gateways gives redundancy on a high-volume site but doubles reconciliation work; most SMEs are better off with one well-configured gateway. Remita is often expected for payments to government bodies and some institutions, so public-sector suppliers should check what their counterparties require.

Five ways to add payments to a website

There are five routes to accepting payments on a website, from no-code to full API integration. The right one depends on whether amounts are fixed or variable, how many payments you expect, whether the site must update itself when a payment succeeds, and whether you have a developer.

The difference between the first two routes and the last two is what happens after payment. A payment page tells you that money arrived; an API integration with webhooks updates the order, marks the invoice paid, grants access to the course or issues the receipt without a human. If a staff member is checking a dashboard and updating records by hand, you are on the wrong route for your volume.

Step-by-step: accepting online payments on your website

The steps are: decide what you collect and which methods to offer, open and verify a gateway account, choose the integration route, integrate in test mode, verify payments server-side and handle webhooks, test on real phones, switch to live keys, and set up reconciliation. A no-code setup can be live within days once compliance clears; an API integration typically takes one to three weeks of development.

1. Define the payment scenarios. List everything a customer might pay for, whether the amount is fixed or variable, and what should happen after payment (receipt, order status, access, WhatsApp confirmation).
2. Open the gateway account and submit compliance. Use the business's email and phone, not a staff member's. Upload CAC documents, ID and bank details; review can take from a day to a couple of weeks.
3. Choose the integration route using the table above: the simplest route that still automates what happens after payment.
4. Integrate in test mode. Every major gateway provides test keys and test cards or bank simulations, so no real money moves during development.
5. Verify every payment on the server. Never trust a "success" message from the browser alone; confirm the transaction, amount and currency with the gateway's verification endpoint before fulfilling.
6. Handle webhooks. Register a webhook URL so the gateway notifies your site of successful payments, including transfers completed after the customer closed the page. Validate the signature the gateway sends.
7. Design the post-payment experience. Confirmation page, receipt, WhatsApp or SMS message, and a reference the customer can quote if there is a problem.
8. Test like a Nigerian customer. Cards from different banks, a transfer from a bank app, USSD on a feature phone, an abandoned payment, and a payment on a slow connection.
9. Go live. Swap test keys for live keys, confirm the live webhook URL, make a small real payment and refund it.
10. Set up reconciliation. Daily or weekly comparison of settlements against orders or invoices, with a named owner and an export routine for accounts.

Fees, settlement, refunds and reconciliation

Gateways deduct their fee from each transaction and settle the balance to your bank account on a schedule, typically the next business day for local payments, with faster options on some providers. Refunds are initiated from the gateway dashboard or API and take days to reach the customer's bank. Reconciliation, matching settlements to sales, is the step most Nigerian businesses skip and later regret.

• Fees. Model the fee at your typical transaction size: a cap on local card fees favours large payments such as school fees or rent, while a fixed component matters for small ones. Decide whether to absorb fees or pass them on, and be transparent if you do.
• Settlement. Know the default timing, weekend and public-holiday behaviour, and whether you can settle to more than one account. For foreign-card payments, confirm how conversion works and what your bank does with foreign inflows.
• Refunds and disputes. Publish a refund policy that matches what you can actually do. Card chargebacks go through the gateway's dispute process; keep proof of delivery or service.
• Reconciliation. Export gateway transactions with references, match them to orders or invoices, and investigate the gaps: partial, duplicate and off-gateway payments. Automate this beyond a few dozen payments a week.

Security and compliance: what your website must do

Using a licensed gateway's hosted form or inline checkout means card data never touches your server, which removes most of the PCI DSS burden from your business. Your remaining obligations are to serve the site over HTTPS, keep secret keys off the browser and out of public code, verify transactions server-side, validate webhook signatures, and protect customer data under the Nigeria Data Protection Act 2023. Security checklist:

• Never collect card numbers on your own forms; let the gateway's checkout handle them.
• Keep secret keys in server-side configuration, not in JavaScript, templates or public repositories.
• Verify amount, currency and status with the gateway before fulfilling.
• Check webhook signatures and reject requests that fail.
• Rate-limit payment initiation and watch for repeated failed attempts.
• Log transaction references against orders, and restrict who can issue refunds.
• Publish a privacy notice covering payment and contact data; retain only what you need; verify current NDPA obligations with the NDPC.
• Keep plugins, frameworks and the server patched; abandoned plugins are a common entry point.

Nigerian realities that shape your payment setup

Compared with the generic advice in overseas guides, a Nigerian payment setup has to accommodate transfer-first customers, bank app and network outages, fake transfer alerts, exchange-rate exposure on foreign payments, and a compliance process built around CAC registration and BVN. Design for these rather than discovering them at launch.

• Transfer is a primary method, not a fallback. Use virtual-account transfers through the gateway so that transfers confirm automatically and fake "I have paid" screenshots stop being a problem.
• Outages happen. Bank apps, switches and networks fail at month-end and on salary days. Offer more than one method and show clear guidance when a payment is pending.
• Mobile and data. Most payments happen on phones over mobile data. Keep the checkout light and avoid redirect chains that break on flaky connections.
• Foreign payments. If diaspora customers or foreign clients pay you, confirm which gateway supports international cards for your business type and how settlement works; Stripe is not a straightforward option for a Nigerian company.
• Trust. A recognisable gateway checkout, visible contact details and instant receipts reassure customers who have been defrauded before.
• Regulation. Payment providers operate under Central Bank of Nigeria licensing, and your compliance file determines limits and features. Keep CAC and bank documents current and verify requirements with the provider.

Example (hypothetical): a private school in Abuja collects fees online

Example (hypothetical): a private secondary school in Abuja with 600 students collects termly fees by bank transfer to the school account. The bursar spends two weeks each term matching transfers to students, because parents use their own names, pay in instalments and rarely quote the student's ID. The school adds fee payment to its existing WordPress website. Because amounts vary by class and instalment plan, it uses an API integration through a small custom plugin rather than a fixed payment page: a parent enters the student ID, the site shows the balance from the school's records, and the parent pays by card or virtual-account transfer through the gateway. Webhooks update the balance and email a receipt automatically; a WhatsApp confirmation follows for parents who opted in. Fee caps on local card payments keep the cost per large payment low, and the school decides to absorb fees rather than pass them on. The setup takes about three weeks, most of it connecting the fee records. Afterwards the bursar reconciles by exporting gateway settlements and matching by student ID, which the integration records on every transaction. The measures that matter are unmatched payments per term (target: near zero) and days to close reconciliation. This is a hypothetical scenario to illustrate route selection, not a client case study.

How much does it cost to accept payments online?

Indicatively, adding payments to a Nigerian website costs nothing beyond transaction fees if you use payment links or an official plugin yourself, ₦80,000–₦400,000 for a developer to add inline or plugin-based payments to an existing site, and ₦300,000–₦1,500,000+ for an API integration with webhooks, receipts and reconciliation inside a custom site or portal. Gateway fees are charged per transaction on top. Indicative 2026 ranges; actual quotes vary with scope, vendor and exchange rate.

To compare quotes, ask each developer to price the same scenario list, the integration route, server-side verification, webhook handling, receipt design, reconciliation exports and testing on real payment methods. Compare two or three written quotes on identical scope.

Mistakes to avoid

• Launching without automatic transfer confirmation. Manual "send your receipt on WhatsApp" flows invite fake alerts and eat staff time. Use gateway virtual accounts.
• Trusting the browser's success message. Fulfilment based on a client-side callback can be spoofed. Verify server-side and use webhooks.
• Exposing secret keys. Keys pasted into page templates or public code repositories are a common cause of fraud. Keep them server-side.
• Ignoring the fee structure. A method that is cheap for ₦5,000 payments may be expensive for ₦500,000 payments, or the reverse. Model fees at your real transaction sizes.
• No reconciliation owner. Money arriving is not the same as money accounted for. Assign the task and automate exports.
• Offering only card. Many Nigerian customers will abandon a card-only checkout. Transfer and USSD are essential.
• Using a personal account. Settling business payments into a personal account complicates tax, compliance and, later, selling or scaling the business.

Conclusion

Accepting online payments on a Nigerian website comes down to four decisions: which methods your customers need (card and transfer at minimum, USSD where phones and data are unreliable), which licensed gateway fits your business type and transaction sizes, which integration route automates what happens after payment, and who reconciles settlements against sales. Get the gateway compliance started first, choose the simplest route that still updates your records automatically, verify every payment on the server, and test with real Nigerian banks and phones before going live. If you want payments integrated properly into a Nigerian business website, portal or web application, with automatic confirmation, receipts and reconciliation, Linestech can help you choose the gateway and route that fit your operation and build the integration.

Frequently asked questions

Can I accept online payments without registering my business with CAC?

Some gateways offer starter or individual accounts with lower transaction limits and fewer features, which can be enough to test demand. For higher limits, settlement to a business account and features such as subscriptions or multiple settlement accounts, gateways generally require CAC registration. Check the current compliance requirements on the provider's website.

Do I need a developer to accept payments on my website?

Not for payment links, hosted payment pages or official plugins on WordPress, WooCommerce and Shopify. You need a developer when amounts are variable and calculated by your system, when payment must trigger something automatically, when you are building a portal or web app, or when reconciliation needs to be automated.

Which is better for a Nigerian website, Paystack or Flutterwave?

Both serve Nigerian SMEs well with card, transfer and USSD, plugins for common platforms and developer APIs. Paystack is often chosen for simplicity and documentation; Flutterwave for multi-currency collection and broader African coverage. Compare current fees at your transaction sizes, compliance fit for your business type and the specific features you need.

How quickly do I receive the money?

Gateways typically settle local payments to your bank account on the next business day, with weekends and public holidays shifting the schedule; some offer faster settlement options. International card payments and foreign-currency settlements can take longer and involve conversion. Confirm settlement terms on your provider's dashboard.

How do I handle a customer who says they paid but the order is not confirmed?

Ask for the gateway transaction reference, then check the dashboard. Common causes are a transfer made outside the virtual-account window, a card payment pending bank confirmation, or a webhook that failed to reach your site. A well-built integration logs every attempt with a reference, which makes these cases quick to resolve.

Can my website accept payments in dollars from customers abroad?

Possibly, depending on your gateway, business type and compliance status. Some Nigerian gateways support international cards and multi-currency collection with settlement in naira or, in some cases, foreign currency. Confirm eligibility, fees and settlement rules with the provider and your bank before promising dollar pricing on the site.

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)
• Central Bank of Nigeria (CBN)
• Paystack developer documentation
• Flutterwave developer documentation
• MDN Web Docs — web platform reference
• Flutter documentation