Paystack vs Flutterwave for Nigerian E-commerce: How to Choose

Most comparisons of these two try to declare a winner. That is the wrong exercise, because both process the same local rails, both integrate with the common store platforms, and both publish their own pricing that changes over time. A store that switches gateways rarely sees a step change in conversion.

What does change outcomes is fit: whether the checkout suits how your buyers pay, whether settlement timing suits your cash flow, whether the integration suits your platform, and how each handles the problems that cost you money later, such as failed payments, disputes and reconciliation. This guide gives you a way to evaluate both against your own store rather than a ranking to copy.

What both gateways do

Both Paystack and Flutterwave provide the same core service to a Nigerian online store:

• A hosted checkout or inline payment modal that collects payment without card details touching your server.
• Multiple payment methods in one flow, including cards, bank transfer and USSD.
• Webhooks that tell your store when a payment succeeds or fails, so orders update automatically.
• A merchant dashboard for transactions, refunds, settlements and customer records.
• Official plugins and SDKs for common platforms and programming languages.
• Payment links and simple storefront pages for sellers without a full website.
• Recurring billing support for subscriptions, with saved payment authorisations.
• Settlement to a Nigerian business bank account.

If your requirement is "take card and transfer payments on my Nigerian store and put the money in my account", either will do the job. The comparison only becomes meaningful at the next level of detail.

Where they differ in practice

Both providers update their products frequently, so treat this as a map of where to look rather than a fixed scorecard. Verify each point on the providers' own documentation and pricing pages before deciding.

The differences that actually affect a Nigerian store are usually mundane: whether the plugin for your platform is actively maintained, how quickly settlements land, how clearly the dashboard reconciles to your orders, and how responsive support is when a customer's money is in limbo.

Fees: how to compare them properly

Do not compare headline percentages. Compare the total cost of processing your actual mix of transactions.

Both providers publish fee structures that typically involve a percentage of the transaction, sometimes a flat naira component on local transactions, often a cap on local card fees, and a higher rate for international cards. Rates change, so read each provider's current pricing page rather than relying on figures quoted in any article, including this one.

Work it out like this:

1. Take last month's orders. Split them by payment method (card, transfer, USSD) and by whether the card was local or international.
2. Apply each provider's current published rates to that mix, including any caps and flat components.
3. Add the costs that are easy to forget: settlement or payout fees, chargeback or dispute fees, currency conversion margins if you collect in another currency, and any fee on refunds.
4. Compare the totals as a percentage of revenue, then decide whether the difference is material against the operational differences.

For most Nigerian SMEs the gap between providers on a realistic transaction mix is small compared with the revenue impact of an extra payment method, a faster settlement cycle or fewer failed payments. Price is a tie-breaker, not the decision.

Payment methods your Nigerian customers will use

Coverage matters more than rate. A checkout that only offers cards will lose orders in Nigeria, regardless of which provider powers it.

• Cards. Verve, Mastercard and Visa issued locally, plus international cards from diaspora buyers. Local cards often have limits on international transactions, which is why an international-only checkout fails for Nigerian buyers.
• Bank transfer. Widely preferred. Gateway-generated transfer options confirm automatically, which is the whole point: it removes screenshot verification from your process.
• USSD. Useful for customers who prefer their bank's shortcode or who have connectivity constraints.
• Direct bank debit or account-based payments, where offered and where your customers' banks are supported.
• Mobile money and wallets, relevant for some segments and for cross-border sales.

When you compare providers, test the actual checkout on a phone, with a real local card and a real transfer, and see which methods appear, how clearly they are labelled, and how the flow behaves on a weak connection. That test tells you more than any feature table.

Settlement, cash flow and reconciliation

Settlement timing determines how quickly your sales become usable cash. Nigerian gateways typically settle local transactions on a next-business-day or similar cycle, with international transactions taking longer, and both providers publish their own schedules that can vary by account type and risk profile. If you restock weekly or pay suppliers on delivery, ask each provider directly what your settlement cycle would be and whether it changes during high-volume periods.

Reconciliation is the part most store owners underestimate. Settlements arrive as batches, not as individual orders, so your finance process needs to match a batch to the orders it contains. Practical requirements:

• Settlement reports that can be exported and matched to order references.
• Order records in your store that store the gateway transaction reference.
• Clear handling of refunds, partial refunds and reversed transactions in the same report.
• A monthly routine rather than a year-end scramble.

Ask each provider to show you a settlement report before you commit. If your accountant cannot use it easily, that cost recurs every month.

Integration with your store platform

Hosted platforms. Both providers offer official integrations for the common store platforms. Check that the plugin for your specific platform is current, actively maintained and supports the methods you want, including transfer and USSD. A neglected plugin is a risk regardless of how good the underlying API is.

WooCommerce. Both have official plugins. Verify support for your WooCommerce and PHP versions, webhook handling, refunds from the WordPress admin and subscription support if you need it.

Custom builds. Both offer REST APIs and SDKs. What matters for a custom store: clear webhook signatures and retry behaviour, a usable test environment, idempotency handling so a retried request does not double-charge, and documentation that covers failure cases rather than only the happy path.

Mobile apps. Check SDK availability for your framework and how each handles a payment that completes while the app is backgrounded, which is common on Nigerian networks.

Whichever you choose, implement three things properly: verify webhook signatures, never mark an order paid from the client side alone, and store the gateway reference on the order.

Failed payments, disputes and chargebacks

Failed payments are a bigger revenue issue than fee differences. Cards fail for insufficient funds, transaction limits, failed authentication, issuer timeouts and network problems. Your checkout should show a plain-language reason and immediately offer an alternative method, ideally bank transfer. Measure your payment success rate by method, then work on the worst performer.

Disputes and chargebacks arise when a customer says goods were not received or not as described. Both gateways provide a dispute workflow with an evidence window. Your defence is operational: delivery confirmation with date and recipient, the delivery address captured at checkout, communication history, and a clear returns policy published on your site. Stores that keep dispatch records win disputes; stores that rely on memory do not.

Fraud controls. Use each provider's built-in risk checks, and add your own rules for pay-on-delivery orders: flag first-time customers with high-value baskets, confirm phone numbers before dispatch, and record refusals so you can tighten rules by area.

Compliance, onboarding and data protection

Onboarding. Both providers require business verification before settling at full limits: typically CAC registration documents, bank account details, directors' identification and BVN information, and sometimes a live website showing products, contact details and a refund policy. Requirements change, so confirm current documentation with each provider and with the Corporate Affairs Commission.

Card data. Use hosted checkout, an inline modal or an approved SDK so card details never reach your server. This keeps your PCI DSS obligations light. Do not build custom forms that capture card numbers unless you have a compelling reason and specialist advice.

Data protection. Customer names, phone numbers, addresses and transaction records are personal data under the Nigeria Data Protection Act 2023. Publish a privacy notice covering payment processing, limit staff access to transaction data, set retention periods and check what your gateway's terms say about data processing. Verify current obligations with the Nigeria Data Protection Commission or a qualified adviser.

Regulatory context. Payment service providers in Nigeria operate under Central Bank of Nigeria licensing and oversight. As a merchant, your practical obligations are business verification, accurate representation of goods, and compliance with your provider's terms.

An evaluation checklist for your store

Run both providers through this before deciding.

• Both accounts opened in test mode and a live low-value transaction completed on each
• Checkout tested on a mid-range Android phone over mobile data
• Card, bank transfer and USSD all confirmed working and clearly labelled
• Current published fees applied to last month's actual transaction mix
• Settlement timing confirmed in writing for your account type
• Sample settlement report reviewed by whoever does your books
• Official plugin for your platform checked for recent maintenance
• Webhook behaviour and retry policy reviewed by your developer
• Refund and partial refund flow tested end to end
• Dispute process and evidence requirements read and understood
• Support channels tested with a real question before you commit
• Onboarding document requirements confirmed against what you hold
• International card acceptance tested if you sell to diaspora customers
• Data processing terms reviewed against your privacy notice

If both pass, choose on settlement timing and support responsiveness. Those are the two things you will care about at 9pm when a customer's payment is stuck.

Example (hypothetical): a fashion brand selling locally and abroad

Example (hypothetical): a Lagos fashion brand takes about 250 orders a month. Roughly 60% pay by bank transfer, 35% by local card and 5% by international card from diaspora customers. Average order value is ₦45,000, and they restock fabric weekly, so settlement speed matters.

How they evaluated:

1. Method coverage. Both providers covered card, transfer and USSD. They tested each checkout on a mid-range phone and compared how clearly the transfer option was presented, since transfer is the majority of their volume.
2. Cost on their mix. They applied each provider's current published rates to last month's split, including the local fee cap and the international card rate, and found the difference immaterial relative to revenue.
3. International sales. Because diaspora orders are growing, they checked multi-currency collection and payout options in detail.
4. Settlement. They confirmed the settlement cycle for their account type in writing with both providers, because weekly restocking depends on it.
5. Platform fit. Their store runs on WooCommerce, so they checked plugin maintenance history and tested refunds from the admin.
6. Support. They sent the same technical question to both and compared the response.

They chose on settlement timing and international coverage rather than on fees, and kept a tested integration for the second provider as a fallback. That fallback is the part most stores skip and later regret during an outage.

Mistakes to avoid

• Choosing on headline percentage alone. Compare total cost on your real transaction mix, including caps, international rates and dispute fees.
• Card-only checkout. In Nigeria this alone costs more than any fee difference.
• Accepting screenshots as payment confirmation. Use webhooks; screenshots are trivially faked.
• Marking orders paid from the browser. Always confirm server-side from the gateway.
• Ignoring failed-payment rates. A few percentage points of failure outweigh fee differences.
• No reconciliation process. Settlement batches that nobody matches to orders create accounting problems that compound.
• Not testing refunds before launch. The first refund should not be a live experiment.
• Assuming plugin support is current. Check maintenance dates for your platform version.
• Skipping dispute evidence discipline. Without delivery records you lose disputes you should win.
• Having no fallback. Any provider can have an outage; a tested second integration protects revenue.

Conclusion

Paystack and Flutterwave are both credible choices for a Nigerian online store, and the useful comparison is against your own numbers rather than against each other in the abstract. Check payment-method coverage first, because offering transfer and USSD matters more than any fee difference. Then confirm settlement timing, test the checkout on a real phone, price both against last month's actual transaction mix, check plugin maintenance for your platform, and read the dispute process before you need it. Treat published fees as current-only information and verify them on each provider's own pricing page.

If you need a Nigerian checkout built properly, with transfer and USSD enabled, webhooks verified server-side and settlements that reconcile cleanly to your orders, Linestech integrates payment gateways into e-commerce websites, apps and custom systems. Tell us your platform and payment mix and we can advise on the right setup.

Frequently asked questions

Which is better for a Nigerian online store, Paystack or Flutterwave?

Neither is universally better. Both process card, bank transfer and USSD payments for Nigerian merchants and integrate with common store platforms. Choose based on your transaction mix, settlement timing, platform plugin quality, multi-currency needs and support responsiveness. Run a live test transaction on both before deciding.

Can I use both gateways on the same store?

Yes, and larger stores often do. One serves as primary and the other as fallback for outages or specific payment types. The cost is extra integration and reconciliation work across two dashboards, so it makes sense above a certain volume rather than for a new store.

Do these gateways support bank transfer and USSD, or only cards?

Both support card, bank transfer and USSD for Nigerian merchants, with automatic confirmation through webhooks. Enabling transfer is one of the highest-impact changes a Nigerian store can make, because a large share of buyers prefer it and it removes manual screenshot verification from your process.

How long does settlement take?

Both publish settlement schedules, typically a next-business-day cycle for local transactions with longer timelines for international payments, and timing can vary by account type, risk profile and banking days. Confirm your specific cycle in writing with the provider, especially if your cash flow depends on quick restocking.

What do I need to open a merchant account?

Generally CAC registration documents, a business bank account, directors' identification, BVN details and a live website showing your products, contact information and refund policy. Requirements differ by provider and change over time, so check the current list with each provider before applying.

Are these gateways safe to use for card payments?

Both use hosted checkout flows and SDKs so card data does not touch your servers, which is the safe pattern and keeps your compliance burden light. Your own responsibilities are securing your store and admin accounts, verifying webhooks server-side, and protecting customer data in line with the Nigeria Data Protection Act 2023.

What happens when a customer disputes a payment?

The gateway opens a dispute with a window for you to submit evidence such as delivery confirmation, the address captured at checkout, communication records and your published returns policy. Outcomes depend on the evidence. Stores that log dispatch details and keep customer communication in one place resolve disputes far more successfully.

Should I switch gateways if I am unhappy with my current one?

Switch for operational reasons: poor settlement timing, weak support, missing payment methods or an unmaintained plugin for your platform. Do not switch expecting a large conversion improvement from fees alone. Keep the old integration in place during transition, test the new one live with small transactions, and move gradually.

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