Taking payments online in Nigeria is far easier than it was a few years ago, mostly thanks to two companies: Paystack and Flutterwave. Between them they have made it possible for a small business to accept cards, bank transfers, and USSD from a website without a merchant bank account or a mountain of paperwork. But "easier" is not the same as "obvious," and the details, the fees, the settlement timing, the compliance, are where businesses either set themselves up well or quietly lose money.
This guide covers what you actually need to collect payments on your site, how the two main options compare, what it costs, and the mistakes worth avoiding.
What you actually need
Accepting online payments comes down to three pieces working together.
- A website that can send a customer to pay. This can be as simple as a payment button or a checkout page. It does not have to be a full e-commerce store, though it can be.
- A payment gateway account. This is Paystack or Flutterwave (or another provider). They handle the hard, regulated part: securely taking the customer's card or transfer, moving the money, and paying it into your bank account.
- A secure connection (HTTPS). Your site needs a valid SSL certificate so the little padlock shows in the browser. No customer should ever type card details on a site without it, and the gateways expect it. Any decent modern host includes this free.
The gateway does the heavy lifting. You are really choosing a provider and wiring it into your site properly.
How the gateways work, briefly
When a customer pays, they are handed off to the gateway's secure checkout, either a popup on your site or a hosted page. They pay by card, bank transfer, USSD, or other methods, the gateway confirms the payment, and it tells your site whether it succeeded. The money then settles into your business bank account on the gateway's schedule, minus their fee.
Crucially, the sensitive card data flows through the gateway, not your server. That is what keeps you out of the heaviest compliance burden, and it is why you should never try to build your own card form. Let the gateway handle cards.
Paystack vs Flutterwave
Both are excellent, both are widely trusted, and for most Nigerian small businesses either one works well. They differ more in emphasis than in quality.
- Paystack is known for a clean, simple developer experience and a checkout customers recognize and trust. If your focus is collecting payments from Nigerian customers on a Nigerian website, it is a safe, popular default, and its dashboard and support are strong.
- Flutterwave casts a wider net, with stronger support for collecting across multiple African countries and currencies, plus a broader set of payment methods and payout options. If you sell beyond Nigeria or want more built-in tools like payment links and invoices out of the box, it is worth a close look.
The honest summary: if you are a Nigerian business selling mainly to Nigerians, start with whichever has the smoother onboarding for you. If you are selling across borders or in multiple currencies, weight the decision toward Flutterwave. You can also start with one and switch later, since the integration is not enormous.
The payment methods that matter here
One reason these gateways matter so much in Nigeria is that they support how Nigerians actually pay, which is not only cards.
- Cards (Verve, Mastercard, Visa) remain common, but card success rates can wobble, so you do not want them to be the only option.
- Bank transfer is huge. Many customers prefer to transfer, and the gateways generate a one-time account number for the exact amount, which is smooth and trusted.
- USSD lets customers pay from feature phones or without data by dialing a code, which still matters for a real slice of the market.
- Others like QR and mobile money show up depending on the provider.
Turn on the methods your customers actually use. Offering transfer and USSD alongside cards, rather than cards alone, meaningfully lifts how many payments go through.
What it costs
Fees change, so treat these as the shape of the pricing rather than exact numbers, and confirm the current rates on the provider's site before you commit.
Broadly, both charge a small percentage of each local transaction, commonly in the region of 1.5%, with a cap so large payments are not punished, and often a small flat addition on transactions above a threshold. International cards cost more, typically several percent, because those transactions carry more cost and risk. There is usually no monthly fee and no setup fee, so you only pay when you get paid.
Two things to plan for beyond the headline rate:
- Settlement timing. Money does not land instantly. It typically settles to your bank account the next business day for local transactions, sometimes longer for international ones. Factor that into your cash flow, especially early on.
- Who absorbs the fee. You can either take the fee out of your margin or pass it to the customer at checkout. For services, most businesses absorb it. For thin-margin products, decide deliberately rather than by accident.
Getting set up
The path is refreshingly light compared with traditional merchant accounts.
- Register a business, ideally. You can often start with a personal account for testing, but to receive settlements properly and unlock full features you will want a registered business (a CAC registration) and a corporate bank account. It also builds customer trust.
- Create and verify your gateway account. Expect to provide your business details, bank account for settlement, and identity verification (BVN and ID are standard). Verification is what lifts limits and enables live payments.
- Connect it to your website. This is the technical step. It ranges from dropping in a payment link or a simple button for a basic case, to a proper integration where your site creates the payment, confirms it on your server, and updates an order or booking. A hosted payment link needs no developer; a real checkout on your own site usually does.
- Test in test mode, then go live. Both gateways give you test keys and test cards so you can run the whole flow end to end without real money. Do this thoroughly before switching to live keys.
The step businesses skip is verifying the payment on their own server, not just trusting the popup that says "success." Without that server-side check, a technically-minded customer can fake a success and get your product for free. A proper integration always confirms the payment with the gateway before it hands over anything.
Mistakes that cost money
A few errors show up again and again, and each one is avoidable.
- Offering cards only. You lose the large group who prefer transfer or USSD. Turn on multiple methods.
- Trusting the browser instead of verifying server-side. As above, this is how businesses get defrauded. Confirm every payment with the gateway before fulfilling.
- Hardcoding your secret key into the website's front end. Your public key belongs in the browser; your secret key must stay on the server, never shipped to the visitor. Leaking it is a serious security hole.
- Not handling the failed payment. Cards fail often here. If your checkout dead-ends on failure instead of offering another method or a retry, that is a lost sale that was ready to buy.
- Ignoring receipts and records. Make sure successful payments trigger a clear confirmation to the customer and a clean record for you. Reconciling later is painful if you did not capture it cleanly.
The short version
To take payments online in Nigeria you need a secure website, a Paystack or Flutterwave account, and a proper integration between them. Both gateways are strong: pick Paystack for a simple Nigeria-focused start, lean toward Flutterwave if you sell across borders or currencies. Turn on transfer and USSD alongside cards, expect fees around 1.5% locally with next-day settlement, and register a business so settlements and trust are solid. Above all, verify every payment on your server before you deliver anything, and keep your secret key off the front end. Get those right and you can collect money as smoothly as any big Nigerian brand.