How to accept online payments on your website in Nigeria

Quick answer: how do online payments work for a Nigerian website?

Your website does not take the money itself. A payment gateway sits in the middle. The customer chooses to pay, is shown a secure payment screen belonging to the gateway, and picks a method such as card, bank transfer, USSD or a bank app. The gateway confirms the payment, tells your website, and later settles the money to your bank account, minus its fees.

This arrangement keeps card numbers away from your server and spreads the security burden to a company built to carry it. Your job is to set it up correctly, confirm payments reliably and match them to orders.

Popular gateways in Nigeria include Paystack and Flutterwave, and there are others. The steps below apply to any of them. Check the gateway's own website for the current requirements, supported methods, fees and settlement times, because these change.

What do you need before you apply?

Prepare these first so the application goes through without back-and-forth.

• A working website or app where the checkout will live, with real product or service pages, a visible contact page and clear prices.
• A business bank account. Settlements go to a Nigerian bank account whose name should match your registered business or, for an individual, your name.
• Business details. Business name, address, phone, email, a description of what you sell and your website address.
• Identity verification. Gateways follow know-your-customer rules. Expect to provide the owner or director's identification and a bank verification number, and for registered companies, registration documents. Sole traders may be allowed with fewer documents, but limits may apply.
• Policies. A refund and returns policy, delivery information, and terms. Reviewers often check them, and customers trust sites that show them.
• A legitimate product or service. Gateways restrict some categories. Read their list of prohibited and restricted businesses before applying.

Registering your business is not always compulsory for a starter account, but it widens what you can do and builds trust. Ask the gateway what applies to your situation.

How do you choose between gateways?

Compare on things you can verify, using each gateway's official pages and support.

• Payment methods. Cards, bank transfer, USSD, bank app, and whether your customers use them. If you need international customers, check foreign cards and currencies.
• Fees. How they are charged: a percentage, a fixed part, a cap, and who can bear them (you or the customer). Look at examples for your typical order size rather than relying on headline rates.
• Settlement. How long after payment the money reaches your bank, which days it runs, and whether you can pick a schedule.
• Integration options. Plugins for your platform, a hosted payment page, a popup, or an API for custom systems.
• Dashboard and reports. Easy to search, filter and export transactions.
• Refund and dispute handling. How refunds are made and how chargebacks are handled.
• Support quality and reliability. Documentation, response times and past uptime.
• Extras. Payment links, invoices, subscriptions, split payments, payouts to vendors.

You can offer more than one gateway, but start with one and make it solid.

How do you set it up step by step?

1. Create an account on the gateway's website using a business email you control, with two-step verification enabled.
2. Submit the business and verification details. Use information that matches your documents exactly. Mismatched names are a common cause of delay.
3. Add your settlement bank account and confirm it.
4. Find your API keys. There are test keys and live keys, each with a public (publishable) key and a secret key. The secret key must never be placed in browser code, shared on chat or committed to a public repository.
5. Choose how to integrate. Use the plugin for your platform if one exists, or use the gateway's hosted checkout or popup. A custom site integrates through the gateway's API.
6. Connect your checkout in test mode using the test keys.
7. Set up the webhook. In the gateway dashboard, enter the web address on your site that will receive payment notifications. Your site must verify that each notification is genuine before marking an order paid.
8. Run your test payments (see the next section).
9. Complete the activation or go-live request once the gateway approves your business.
10. Swap in the live keys, make one small real payment and confirm it appears in your dashboard, your order system and your bank settlement.

What does the payment flow look like?

Understanding the flow helps you fix problems and avoid the most common security mistake.

1. The customer fills their cart and reaches checkout.
2. Your site creates the order with status pending, and records the amount and a unique reference.
3. Your site starts the payment with the gateway, sending the amount from your server, never trusting an amount sent by the browser.
4. The customer pays on the gateway's secure page or popup.
5. The gateway sends the customer back to your site, and also sends a webhook to your server.
6. Your server verifies the payment, either by checking the webhook signature or by asking the gateway for the transaction status, and confirms the amount and currency match the order.
7. Only then does the order become paid, stock is reduced, and the customer receives a receipt by email or message.
8. Later, the gateway settles the money to your bank.

If the customer closes the page after paying but before returning to your site, the webhook is what keeps your records right. Process each payment only once, so a repeated notification does not duplicate an order.

How should you test before going live?

Test mode lets you simulate payments without real money. Gateways publish test card numbers and scenarios in their documentation; use those exactly as given and never use real card details in test mode.

Test at least these cases:

• A successful payment: the order turns paid, stock reduces and an email is sent.
• A declined card or insufficient funds: the customer sees a clear message and can try again, and the order stays unpaid.
• The customer abandons the payment: the order stays pending and does not look paid.
• The browser is closed after payment: the webhook still marks the order paid.
• The same webhook arrives twice: nothing is duplicated.
• Someone changes the amount in the browser: your server rejects the mismatch.
• A refund: the order and stock update as you expect.
• Phone use on mobile data: the checkout is quick, readable and works on a small screen.

After going live, make a small real purchase yourself and trace it through the dashboard, your order, the receipt and the bank settlement. Then refund it to confirm that process too.

How do fees, settlement and currency work?

Do not assume numbers; read them on the gateway's pricing page and in your account agreement. Concepts to understand:

• Transaction fee. Usually a percentage of each payment, sometimes with a fixed part and a maximum. The fee is deducted before settlement, so the amount reaching your bank is lower than the amount the customer paid.
• Who pays the fee. You can absorb it in your prices or pass it to the customer where the gateway and the rules allow. Be transparent either way, and show the final total before the customer pays.
• Settlement delay. Money usually arrives after a settlement period, not instantly. Plan your cash flow, especially around weekends and public holidays.
• Currency. Naira is standard. If you accept other currencies, check conversion, settlement currency and any extra charges.
• Other charges. Ask about fees for refunds, payouts, chargebacks and failed transfers.
• Taxes. Your income from online sales is part of your business income for tax. Keep records and ask an accountant how it applies.

How do refunds, disputes and failed payments work?

Decide the rules before the first complaint.

• Write a refund policy covering when refunds are given, how long they take, which items are excluded and who pays for return delivery. Show it at checkout.
• Refund from the dashboard or through the API, referencing the original transaction. Full and partial refunds are usually supported, and the time for money to return to the customer depends on their bank. Tell them to expect a delay.
• Failed payments with money debited. This happens when a transfer or bank session times out. The gateway can usually trace it. Tell the customer to keep the transaction reference, check the dashboard and confirm with the gateway. Reverse or complete the order accordingly.
• Chargebacks. A customer can dispute a card payment with their bank. Keep proof: order, delivery confirmation, communication. Respond within the gateway's deadline.
• Customer service. Put a phone or WhatsApp number near the pay button. Most customers who feel safe will complete the payment.

How do you keep online payments secure?

• Use HTTPS on every page, so the connection is encrypted. Check that the padlock shows and the certificate is renewed automatically.
• Do not store card numbers. Let the gateway handle card entry through its hosted page or popup.
• Protect your secret keys. Keep them on the server in configuration, not in public code, and rotate them if they leak.
• Verify every payment on the server and check amount, currency, reference and status.
• Secure the dashboard. Strong unique password, two-step verification, limited team access and removal of former staff.
• Keep software updated, including plugins and themes. Out-of-date plugins are a common way in for attackers.
• Beware of phishing. Fake emails and messages pretending to be your gateway or a customer's bank are common. Log in only by typing the address yourself, and confirm payments in the dashboard, never from a screenshot of a transfer.
• Keep backups of your site and orders.

How do you reconcile payments with orders?

Reconciliation means checking that the money you received matches the orders you fulfilled. Do it often, ideally weekly, and always at month end.

1. Export the gateway's transaction report for the period, including reference, amount, fee and status.
2. Export your orders for the same period.
3. Match each paid order to a successful transaction by reference.
4. List anything unmatched: payments without orders, orders marked paid without payments, duplicate payments, refunds.
5. Compare the net total (payments minus fees and refunds) with the settlements received in your bank statement.
6. Investigate and fix differences, and record the fee as an expense.

Using a reference number you generate for each order makes this far easier. If your website and your accounting or stock records are connected, much of this can be automatic.

When should you get help?

You can do a basic setup yourself if your platform has a ready plugin. Get a technician when you have a custom website, need to tie payments to stock and customer records, handle subscriptions or split payments, or have been caught by problems such as duplicated orders or payments that do not confirm. A clean integration is much cheaper than discovering a loophole after customers have found it.

Frequently asked questions

Written by the ICT AccessPoint team

We repair laptops and build websites and business systems. Have a question this guide did not answer? Message us.

This guide is general advice. Every device and business is different, so if you are unsure, ask a technician before you act.