Paystack vs Flutterwave vs Monnify vs Interswitch Nigeria 2026
Paystack vs Flutterwave vs Monnify vs Interswitch: Which Payment Gateway Should Nigerian Businesses Use?
The short answer: there is no single payment gateway that is automatically the best for every Nigerian business. The right choice depends on your average transaction value, payment channels, international customers, settlement requirements, recurring-payment needs, reconciliation workflow, developer requirements and the total cost of operating your payment system.
This comparison goes beyond the usual “which gateway is cheapest?” question. It calculates how published fee structures behave at different transaction sizes, examines settlement and cash-flow implications, compares payment channels, looks at virtual accounts and recurring collections, and builds a decision framework that a Nigerian business can actually use.
How Daily Reality NG Researched This Comparison
This article was rebuilt using a primary-source-first method. The purpose was not to collect the first page of Google results and rearrange the information. Instead, the research process separated regulatory verification, current pricing, payment-channel capabilities, settlement information, operational features and competitor coverage before the comparison was written.
Verification date: September 5, 2026.
Provider sources checked: Paystack's current pricing and support documentation; Flutterwave's current Nigeria pricing, payment-method and settlement documentation; Monnify's current pricing, payment-acceptance and product documentation; and Interswitch's current Payment Gateway and developer-facing product information.
Regulatory sources checked: Central Bank of Nigeria information concerning payment service providers and payment-system charges, together with Nigeria Data Protection Commission information concerning the Nigeria Data Protection Act 2023 and data-processing responsibilities.
Competitor coverage: current 2026 comparison articles were reviewed only to identify gaps in existing coverage. This article deliberately avoids reproducing their rankings, wording, table structures or conclusions. The main editorial difference here is that the decision is built around transaction economics, cash flow, channel mix and operational fit rather than one permanent “best gateway” label.
Important limitation: public pricing can change, and enterprise merchants may receive negotiated commercial terms. Interswitch's current public IPG presentation describes its capabilities and integration options but does not expose a simple standardized public transaction-price table comparable with the published consumer-facing rate cards of the other three providers. Therefore, this article does not invent an Interswitch percentage from an old third-party source.
This method matters because a payment-gateway comparison can become misleading when an old fee is treated as current, when a provider's transaction fee is confused with a bank or switching charge, or when a settlement feature is presented as if it were universal for every merchant.
Why This Page Exists
Most gateway comparisons answer the question, “Which one is best?” That sounds useful, but it hides the most important variable: best for what kind of business?
A Nigerian fashion store selling ₦2,000 items does not have the same payment economics as a B2B company collecting ₦500,000 invoices. A SaaS company collecting subscriptions every month has a different integration problem from a marketplace splitting one customer payment between several sellers. A business selling mainly to Nigerians has a different priority from a Nigerian software company whose customers are spread across several African and international markets.
That is why this guide treats the four gateways as business infrastructure rather than simply four brands.
The central question is not:
The better question is:
That change in question produces a very different conclusion.
Paystack vs Flutterwave vs Monnify vs Interswitch: Executive Verdict
If you want the fastest useful answer, start here: Paystack is a strong fit where a business values a straightforward developer ecosystem and predictable local transaction pricing; Flutterwave is particularly compelling where payment-method breadth and multi-market reach matter; Monnify stands out where virtual-account collections, reconciliation and same-day local settlement are central to the operation; and Interswitch deserves serious consideration when an enterprise needs broad Nigerian payment infrastructure, established rails and features such as split payments and refund APIs.
Those are fit statements, not permanent rankings.
The four-way decision in one sentence each
- Paystack: strong all-round option for businesses that want a mature developer-oriented checkout, local payment methods and transparent published pricing.
- Flutterwave: strong choice when a merchant needs broad payment-method coverage and a business model that reaches beyond Nigeria.
- Monnify: especially interesting for businesses that depend heavily on bank transfers, virtual accounts, reconciliation and faster local settlement.
- Interswitch: worth serious enterprise evaluation where established Nigerian payment infrastructure, multiple local rails, split payments and refund tooling are important.
But none of those statements should replace your own transaction model. A merchant processing ₦2,000 orders can reach a different answer from one processing ₦500,000 invoices. That is the theme running through this entire comparison.
| Business priority | Provider to investigate first | Why |
|---|---|---|
| Simple local ecommerce checkout | Paystack / Monnify | Both publish capped local pricing structures and support common Nigerian payment methods. |
| Multi-country payments | Flutterwave | Broad regional payment and currency coverage is a central part of its proposition. |
| Transfer-heavy collections | Monnify | Virtual-account and reconciliation capabilities are particularly relevant to transfer-led businesses. |
| Developer-first integration | Paystack / Flutterwave | Both provide extensive APIs and developer documentation. |
| Marketplace or split-payment workflow | Interswitch / provider-specific evaluation | Interswitch publicly highlights split payments; other providers should be tested against the exact marketplace architecture. |
| Same-day cash-flow priority | Monnify | Monnify publicly advertises same-day local settlement by 10PM plus Express Settlement options. |
| Enterprise relationship and local infrastructure | Interswitch | Requires commercial and technical evaluation rather than relying on a consumer-facing fee ranking. |
The Six-Question Gateway Test Every Nigerian Business Should Complete First
Before comparing logos, answer these six questions. They are more useful than asking another business owner which gateway they use.
What is your average transaction value?
Write down the typical amount customers pay. If your average order is ₦2,000, fixed fees and waivers matter. If your average payment is ₦200,000, transaction caps become much more important.
Where are your customers?
Are 95% of your customers in Nigeria? Do you receive payments from Ghana, Kenya, the United Kingdom, the United States or elsewhere? International pricing can completely change the economics.
How do customers actually want to pay?
Do they prefer cards, bank transfer, USSD, account payments, QR or wallet methods? A gateway with a theoretically lower card fee can still be the wrong choice if your customers mostly use another channel.
When do you need the money?
Can your business wait for the normal settlement cycle? Or do you buy stock immediately after sales, pay drivers daily, settle suppliers quickly or operate on tight working capital?
How much automation do you need?
Do you need virtual accounts, automatic reconciliation, recurring billing, invoices, split payments, webhooks, refund APIs or automated transfers?
Who will operate the payment system?
A developer-heavy startup may care about API documentation, SDKs, sandbox behaviour and webhook reliability. A small business may care more about payment links, dashboards and customer support.
Regulation: What Nigerian Businesses Should Verify Before Integration
Payment infrastructure is regulated infrastructure. A merchant should therefore separate three different questions: Is the provider operating through an appropriately authorized entity? What are the provider's current commercial terms? And what compliance obligations remain with the merchant?
The Central Bank of Nigeria's published Payment Service Providers information lists Paystack Payment Limited, Flutterwave Technology Solutions Limited, Interswitch Limited and Teamapt Limited within the switching and processing licence category. This is important because brand names and legal entities are not always identical. A business should record the legal entity appearing in its onboarding and contractual documents rather than relying only on the consumer-facing brand.
That distinction is especially relevant when discussing Monnify. Monnify identifies itself as a product of TeamApt Ltd and states that TeamApt is licensed by the Central Bank of Nigeria. Therefore, it is more precise to discuss Monnify's relationship to TeamApt rather than casually claiming that “Monnify” itself is a standalone CBN license category.
There is another important distinction: a regulator's merchant-service-charge framework should not automatically be treated as the same thing as a payment gateway's published commercial price. Banks, processors, switches, acquirers and payment platforms can sit at different layers of the payment chain. Your business needs to know what your gateway actually deducts from your settlement.
What to keep in your compliance file
- Your registered business information.
- The settlement account details approved during onboarding.
- Your gateway agreement and current pricing schedule.
- Your refund and dispute procedure.
- Your privacy notice and data-processing documentation.
- Records of payment references and reconciliation.
- Evidence of how customer payment information is handled.
- Any sector-specific authorization required for what you sell.
Do not assume that a gateway's compliance status transfers all regulatory responsibility to your company. Your business still has obligations concerning consumer information, lawful data processing, refunds, records, tax and sector-specific rules.
Paystack vs Flutterwave vs Monnify vs Interswitch: 2026 Published Pricing
The first mistake in many comparisons is putting four percentages beside each other and declaring the smallest number the winner. The second mistake is treating all payment channels as if they have identical economics. The third is ignoring caps, waivers, international charges and payout costs.
The table below therefore distinguishes published pricing from commercial conclusions.
| Provider | Published Nigerian local collection pricing | Cap / special condition | Other published information |
|---|---|---|---|
| Paystack | 1.5% + ₦100 | ₦100 waived below ₦2,500; local fee capped at ₦2,000 | International 3.9% + ₦100; transfers ₦10/₦25/₦50 by amount; DVA 1% capped at ₦300. |
| Flutterwave | 2% for Nigerian local transactions | Published as 1.4% transaction fee + 0.6% platform fee | International pricing is higher; broad payment-method and regional coverage. |
| Monnify | 1.5% for local cards and USSD; bank-transfer pricing published at 1.5% capped at ₦2,000 / ₦500 flat depending on the applicable option | Local cards/USSD capped at ₦2,000; rates shown VAT-exclusive | International cards 4%; cash collection 4%; payouts ₦10/₦20/₦40 by amount. |
| Interswitch | Current public IPG page does not provide a comparable simple standardized rate card | Commercial pricing should be confirmed directly | Publicly highlights cards, USSD, transfer, split payments, hosted fields and refund API. |
Why Paystack's ₦100 component matters
At small transaction sizes, ₦100 is not a minor detail. It is a large percentage of a ₦2,000 payment. That is why Paystack's waiver below ₦2,500 materially changes the calculation.
Why Flutterwave's current 2% matters
Older Nigerian articles may still quote a different Flutterwave local rate. That is exactly why a current comparison should use the provider's current Nigeria pricing page rather than copying an older comparison article.
Why Monnify's cap matters
A 1.5% fee sounds ordinary until the transaction becomes large. At ₦200,000, 1.5% is ₦3,000, but a ₦2,000 cap changes the actual fee. At ₦500,000, the mathematical 1.5% is ₦7,500, yet the published cap can reduce the applicable fee to ₦2,000 for the covered local method.
Why Interswitch must not be given an invented rate
It is tempting for a comparison article to fill every cell in a table. That temptation creates bad journalism when a current official rate is unavailable. Interswitch's current IPG page emphasizes functionality rather than a public standardized transaction-fee table. The responsible comparison therefore says “confirm quote” rather than repeating an old figure from another year.
The Transaction-Size Test: Where Gateway Pricing Actually Changes
This is the most useful part of the comparison for many merchants.
Instead of asking which percentage is lower, calculate the actual fee for the payment size your customers make.
Fee = percentage charge × transaction amount + applicable fixed charge, subject to any waiver or cap.
Illustrative example: ₦2,000 customer payment
| Provider | Illustrative published-rate calculation | Illustrative fee | What it teaches |
|---|---|---|---|
| Paystack | 1.5% × ₦2,000 = ₦30; ₦100 fixed component waived because payment is below ₦2,500 | ₦30 | The waiver matters enormously to small-ticket sellers. |
| Flutterwave | 2% × ₦2,000 | ₦40 | No fixed ₦100 component is added in this published local-rate calculation. |
| Monnify | 1.5% × ₦2,000 | ₦30 | The published local card/USSD rate produces the same percentage result at this size. |
| Interswitch | Current public standardized rate not established from its IPG page | Quote required | Do not invent a price to complete a table. |
For a merchant selling low-value products, the difference between ₦30 and ₦40 can look small on one sale. Across thousands of orders, it becomes a measurable operating cost. But even then, the cheapest fee should not automatically win if another gateway produces substantially better payment completion or operational efficiency.
Illustrative example: ₦10,000 customer payment
| Provider | Calculation using published standard local rate | Illustrative fee |
|---|---|---|
| Paystack | 1.5% × ₦10,000 + ₦100 | ₦250 |
| Flutterwave | 2% × ₦10,000 | ₦200 |
| Monnify | 1.5% × ₦10,000 | ₦150 |
| Interswitch | Commercial quote required | Not calculated |
Notice what happens here. Paystack's percentage is lower than Flutterwave's published local percentage, but its fixed ₦100 component makes the illustrative fee higher at this transaction size. Monnify's published 1.5% rate produces the lowest of these three illustrative collection fees.
That does not mean Monnify automatically wins. It means the transaction-size calculation has revealed something a headline percentage can hide.
Illustrative example: ₦200,000 payment
| Provider | Illustrative calculation | Illustrative result |
|---|---|---|
| Paystack | 1.5% × ₦200,000 + ₦100 = ₦3,100, then apply ₦2,000 cap | ₦2,000 |
| Flutterwave | 2% × ₦200,000 | ₦4,000 |
| Monnify | 1.5% × ₦200,000 = ₦3,000, then apply ₦2,000 cap for the covered local method | ₦2,000 |
| Interswitch | Commercial quote required | Not calculated |
The economics have changed again. The fixed ₦100 that mattered at ₦10,000 becomes irrelevant once a provider's percentage fee reaches the cap.
Illustrative example: ₦500,000 payment
At ₦500,000, Paystack's uncapped mathematical result would be ₦7,600, but the published local cap means the fee is limited to ₦2,000. Monnify's 1.5% mathematical result is ₦7,500, but its published ₦2,000 cap applies to the relevant local payment methods. Flutterwave's 2% calculation is ₦10,000 if the published local percentage applies without another negotiated or product-specific adjustment.
What the Numbers Look Like at Business Scale
A gateway fee becomes strategically important when multiplied by thousands of transactions.
Consider a purely illustrative business processing 1,000 local payments of ₦10,000 each. Gross processed value is ₦10,000,000.
| Provider | Illustrative per-payment fee | 1,000-payment illustration | Important qualification |
|---|---|---|---|
| Paystack | ₦250 | ₦250,000 | Based on published standard local pricing before other applicable costs or negotiated volume pricing. |
| Flutterwave | ₦200 | ₦200,000 | Based on the current published 2% local rate. |
| Monnify | ₦150 | ₦150,000 | Based on the published 1.5% local method rate and assumes the same method and commercial terms throughout. |
| Interswitch | Quote required | Cannot responsibly calculate | Current public IPG material does not provide the standardized rate required for a defensible calculation. |
The apparent gap between ₦150,000 and ₦250,000 is ₦100,000 on ₦10 million of illustrative processing. That is large enough to investigate.
But the correct business decision is not “choose the ₦150,000 option immediately.” You should then ask whether the cheaper collection cost is accompanied by the channels your customers need, the settlement schedule you require, the reconciliation tools your finance team needs, the recurring-payment functionality your product needs and the support processes your operation can handle.
The effective-rate calculation
For management reporting, use this formula:
“Total payment-related operating cost” should include more than the visible gateway percentage where applicable. Depending on the business, it may include collection fees, payout fees, refund costs, chargeback losses, reconciliation labour, payment-failure recovery work, urgent settlement charges, currency-conversion costs and other contractually applicable charges.
This is one of the strongest reasons not to choose a gateway from a single pricing line.
Payment Channels: The Customer Does Not Care About Your Fee Table
Your customer does not wake up thinking, “I hope this merchant has the gateway with the best merchant-side percentage.” The customer wants the payment method that works for them.
That makes payment-channel coverage an economic variable.
| Capability | Paystack | Flutterwave | Monnify | Interswitch |
|---|---|---|---|---|
| Cards | Yes | Yes | Yes | Yes |
| Bank transfer | Yes | Yes | Yes | Yes |
| USSD | Yes | Yes | Yes | Yes |
| Virtual-account model | Yes | Yes | Strongly featured | Transfer infrastructure available |
| QR / additional local rails | Supported channels vary | Yes, including NQR | Product-dependent | Yes |
| Recurring payments | Card recurring and Direct Debit support | Recurring payment capability | Direct Debit | Confirm exact recurring architecture |
| Payment links / hosted checkout | Yes | Yes | Yes | Yes / hosted options |
| Split payments | Platform capabilities available | Platform features available | Supported product workflows | Public IPG page explicitly highlights split payments |
Paystack's channel position
Paystack supports cards, bank account payments, transfers and USSD in Nigeria, alongside other supported channels. It also provides dedicated virtual accounts and recurring-payment tools. This makes it suitable for businesses that want a conventional checkout while also building more automated payment flows.
Flutterwave's channel position
Flutterwave's current developer documentation lists Nigerian options including card, USSD, bank transfer, account, internet banking, NQR, eNaira and OPay. That breadth can matter when customer behaviour is fragmented across different payment methods.
Monnify's channel position
Monnify places heavy emphasis on transfer-based collections, virtual accounts, cards, USSD, invoices, payment links and offline cash pay-ins through Moniepoint agents. For a transfer-heavy business, the payment architecture can be more important than the card rate.
Interswitch's channel position
Interswitch publicly highlights card payments, USSD, Pay With Transfer, split payments, hosted fields and a refund API. It also has a long-established position in Nigerian payment infrastructure. The important point for a prospective merchant is to test the exact channels and integration flow required by the business rather than treating brand familiarity as proof of suitability.
Settlement: The Hidden Value of Getting Your Money at the Right Time
Settlement timing is not a technical footnote. It is working capital.
Imagine two businesses that both process ₦5 million during a sales campaign. If one can access its funds materially earlier, that business may be able to restock inventory, pay suppliers, fulfil orders or fund advertising sooner.
| Provider | Published settlement information | Business implication |
|---|---|---|
| Paystack | Standard Nigerian settlement is T+1; eligible Nigerian businesses can use Payout on Demand, with a 1% charge on the withdrawal amount and availability limited to eligible processed funds. | Predictable next-day flow, with a paid early-access option for eligible businesses. |
| Flutterwave | Local Nigerian settlements are completed in 1 business day; international settlements take longer. | Suitable for businesses planning around a normal business-day settlement cycle. |
| Monnify | Publicly advertises same-day local settlement by 10PM, including weekends and public holidays, plus up to three Express Settlements per day. | Potentially valuable for merchants whose working capital turns quickly. |
| Interswitch | Confirm the applicable settlement arrangement and commercial terms for your merchant account. | Enterprise merchants should obtain settlement terms as part of the commercial evaluation. |
When same-day settlement matters most
- Fast-moving ecommerce inventory.
- Food and delivery businesses.
- Businesses paying suppliers from daily sales.
- Event businesses with short cash cycles.
- Businesses with tight advertising-to-sales loops.
- Companies where delayed settlement creates borrowing or liquidity pressure.
When settlement speed matters less
A SaaS company with predictable recurring revenue and sufficient cash reserves may care more about recurring billing, API quality and international payments than about receiving money several hours earlier.
That is why “fastest settlement” cannot be the universal winner either.
Virtual Accounts and Reconciliation: Where Payment Infrastructure Becomes Business Infrastructure
For many Nigerian businesses, the hardest payment problem is not accepting the money. It is identifying whose money arrived, for what invoice, and what should happen next.
This is where virtual accounts and automatic reconciliation become important.
Consider an online school collecting fees from 1,000 students. If every student transfers into the same bank account and the finance team manually checks screenshots, the payment gateway problem has become an accounting problem.
A virtual-account workflow can associate a customer, invoice or account reference with a payment destination and allow software to reconcile incoming funds automatically.
| Business | Why virtual accounts matter | Operational question to ask |
|---|---|---|
| School | Identify individual student payments | Can the system automatically match payment to student/invoice? |
| SaaS company | Automate account funding and reconciliation | Can webhooks update the customer's subscription status reliably? |
| Marketplace | Track money against buyers and sellers | Can the payment data map cleanly into the platform ledger? |
| Distributor | Match transfers to orders | Can the finance team reconcile without manual screenshots? |
| Service business | Associate payment with invoice | Can staff confirm payment automatically before service delivery? |
Monnify is particularly notable here because its current product positioning heavily emphasizes virtual accounts, automatic reconciliation, invoices and transfer collections. Paystack and Flutterwave also offer virtual-account/payment-transfer capabilities, so the correct choice depends on how deeply the merchant needs those capabilities integrated into its internal system.
The screenshot problem
A dangerous operational habit in Nigerian ecommerce is accepting a customer's screenshot as final proof of payment.
A screenshot is evidence of what someone says happened on their device. It is not the same thing as your backend receiving a verified payment event.
Your system should ideally verify the transaction through the gateway's server-side response, webhook or official API before releasing goods or changing an order to “paid.”
Subscriptions and Recurring Payments
If your business collects money repeatedly, the gateway decision changes.
A normal ecommerce store may process a customer once. A SaaS product may process the same customer every month. A membership business may charge weekly, monthly or annually. An insurance or service company may need mandate-based collection.
| Business model | Key requirement | What to verify before choosing |
|---|---|---|
| SaaS | Recurring card or account collection | Retry logic, webhook events, failed-payment handling and cancellation flow. |
| Membership | Predictable recurring billing | Mandate lifecycle and customer notification workflow. |
| Installment sales | Scheduled collections | Whether direct debit or recurring card functionality fits the contract. |
| Marketplace | Collection plus distribution | Split payments, ledger design and settlement controls. |
Paystack documents recurring card charges and Direct Debit for Nigerian businesses. Flutterwave also supports recurring-payment use cases. Monnify publicly highlights Direct Debit for subscriptions and installments. Interswitch should be evaluated against the exact recurring architecture your business needs.
Do not choose based only on whether a provider's marketing page contains the words “recurring.” Ask how failed recurring payments are reported, how mandates are cancelled, how webhooks behave and how your accounting system will know whether the payment succeeded.
Developer Experience: The Gateway Is Part of Your Software
For a technical team, the gateway is not just a payment button. It becomes part of the application's state machine.
A successful payment must change an order from “pending” to “paid.” A failed payment must remain recoverable. A delayed webhook must not create duplicate fulfilment. A refund must be reflected in the internal ledger. A dispute must be traceable. A duplicate webhook must not create a second shipment.
This means developer experience has direct financial consequences.
The five developer tests
- Can you create a payment without confusion?
- Can you verify payment server-side?
- Can you process webhooks safely?
- Can you refund and reconcile programmatically?
- Can you diagnose a failed transaction without guessing?
Webhook idempotency is not optional
Suppose a gateway sends the same successful-payment notification twice because your server did not acknowledge the first request quickly enough. If your application simply creates an order every time it receives the event, one customer payment can produce two fulfilment events.
The correct architecture stores a unique payment event or transaction reference and checks whether that event has already been processed.
Paystack developer position
Paystack provides APIs for payments and transfers and extensive developer documentation. Its dispute documentation also exposes API-oriented workflows, which is useful when payment operations need to be integrated into a larger application.
Flutterwave developer position
Flutterwave provides API and checkout tooling, with a broad list of payment methods and regional capabilities. For developers serving multiple markets, the wider payment-method model can be an advantage, but it also means the integration should be tested carefully for each market and method.
Monnify developer position
Monnify provides API and SDK integration alongside hosted and no-code options. Its combination of virtual accounts, transfer collections and reconciliation makes it especially relevant for systems where the payment event must become part of an accounting workflow.
Interswitch developer position
Interswitch provides APIs, web and mobile SDKs and payment-gateway integration tools. Its current IPG product also highlights hosted fields and refund APIs, which can be important for enterprise systems that want greater control over checkout and post-payment operations.
Disputes, Refunds and Operational Risk
The payment fee is only the price of accepting a payment. The operational cost appears when something goes wrong.
Every serious merchant should know:
- How failed transactions are reported.
- How refunds are initiated.
- How long refunds can take.
- How chargebacks are notified.
- How much time the merchant has to respond.
- Whether dispute evidence can be submitted through a dashboard or API.
- How transaction references can be reconciled with the internal order system.
Paystack's documented Nigerian dispute deadline
Paystack's current support documentation states that Nigerian businesses have 16 hours to respond to chargebacks, after which the chargeback can be automatically accepted. That makes dispute monitoring an operational responsibility rather than something the finance team can check once a week.
A business using Paystack should therefore have a monitored dispute email/dashboard process and preserve relevant transaction evidence.
Why every gateway needs a dispute owner
Do not assign disputes to “the company.” Assign them to a person or team.
For a small business, this may be the founder. For a larger company, it may be finance operations or customer experience. The important thing is that someone knows which inbox to monitor and which documents to collect.
| Operational event | Owner | Evidence to preserve |
|---|---|---|
| Failed payment | Engineering / support | Gateway reference, error response, customer order ID. |
| Refund | Finance / support | Original transaction, refund reference, customer communication. |
| Chargeback | Finance / disputes | Invoice, receipt, delivery proof, communication and transaction details. |
| Reconciliation mismatch | Finance / engineering | Internal ledger entry, gateway reference and settlement statement. |
Data Protection, Onboarding and Merchant Compliance
A payment gateway handles sensitive commercial and personal information. Your business should therefore evaluate the privacy and security responsibilities around the integration.
The Nigeria Data Protection Act 2023 establishes the framework for processing personal data in Nigeria, and the Nigeria Data Protection Commission oversees data-protection compliance. The NDPC identifies rights of data subjects and responsibilities for organizations that determine how personal data is processed.
For a merchant, this means the gateway integration should be considered alongside the business's own privacy notice, data minimization, access control, retention and breach-response procedures.
Do not collect payment-card data unnecessarily
If the payment provider can host sensitive payment fields or provide a secure checkout component, using that architecture can reduce the amount of sensitive payment information your own application directly handles.
Your engineering team should nevertheless review the applicable PCI responsibilities and the gateway's technical documentation rather than assuming that outsourcing checkout removes every compliance obligation.
Merchant onboarding matters too
Different businesses can face different onboarding requirements. Registered businesses, individuals, regulated sectors and higher-risk categories may not have identical requirements.
Monnify's published knowledge-base information, for example, identifies prohibited business categories. This demonstrates a broader point: the question is not only “Can the gateway technically accept my payment?” but also “Will this provider onboard and continue servicing my business category under its current risk policy?”
Which Gateway Fits Which Nigerian Business?
1. Small ecommerce store selling mostly to Nigerians
Start by comparing Paystack, Monnify and Flutterwave using your actual average order value. If most transactions are small, calculate the effect of fixed charges and waivers. If transfer payments dominate, give more weight to virtual accounts and reconciliation.
Likely shortlist: Paystack or Monnify, with Flutterwave as a strong alternative when its wider channel or international capabilities are useful.
2. SaaS startup
Your most important features are recurring billing, webhook reliability, payment verification, subscription-state management, international customer support and developer tooling.
Likely shortlist: Paystack and Flutterwave, with Monnify worth testing where Direct Debit and account-based collection are central.
3. Transfer-heavy business
If customers frequently pay by bank transfer, the ability to create and reconcile virtual accounts can matter more than a small difference in card pricing.
Likely shortlist: Monnify, Paystack and Flutterwave.
4. High-ticket business
Run the transaction-cap test. At ₦100,000, ₦200,000, ₦500,000 and ₦1 million, calculate the effective percentage after caps.
Likely shortlist: providers with commercially attractive caps or negotiated rates. Do not decide until Interswitch or any enterprise provider under consideration has supplied a real commercial quote.
5. Nigerian business selling internationally
Look beyond local rates. Compare international transaction pricing, supported currencies, settlement currencies, regional payment methods and cross-border operational requirements.
Likely first investigation: Flutterwave and Paystack, followed by a direct assessment of the other provider's international capabilities for your markets.
6. Marketplace
A marketplace has a more complicated money flow. You may need to collect one payment, allocate portions to multiple sellers, reconcile commissions and process refunds.
Priority: test split-payment functionality, settlement logic, refund behaviour and ledger integration before looking at the headline transaction rate.
7. Physical business that also sells online
Consider whether your payment infrastructure needs to connect online checkout with transfers, terminals or other physical collection methods.
Priority: evaluate the whole payment ecosystem rather than treating the online gateway as a standalone product.
8. Enterprise
Enterprise selection should involve procurement, finance, engineering, security and legal teams. Public website pricing is not enough.
Priority: commercial quote, SLA, settlement schedule, support escalation, security documentation, reconciliation, dispute process and integration architecture.
The Daily Reality NG Payment-Gateway Decision Tree
Use this decision tree before signing up.
Are most customers Nigerian?
If yes, focus heavily on NGN pricing, transfers, USSD, cards, settlement and reconciliation. If no, move international pricing and regional coverage much higher on the list.
Is your average transaction below ₦2,500?
If yes, calculate the effect of fixed fees and waivers. Paystack's ₦100 waiver below ₦2,500 is especially relevant here.
Is your average transaction above ₦100,000?
If yes, calculate caps and request commercial quotes. A capped fee can produce a dramatically lower effective percentage at high transaction values.
Do customers mostly use bank transfer?
If yes, prioritize virtual accounts, reconciliation, payment references, expiry behaviour and settlement reporting.
Do you need international customers?
If yes, compare international fees and actual supported markets rather than using Nigerian local pricing to make the decision.
Do you need same-day local cash flow?
If yes, investigate Monnify's published same-day settlement proposition and compare its value with any alternative early-settlement option.
Are you building a marketplace?
If yes, make split payments, refunds, settlement and ledger integration first-class requirements.
Are you an enterprise buyer?
If yes, obtain written commercial terms from each shortlisted provider before choosing.
Payment Gateway Risk Matrix for Nigerian Businesses
| Risk | What can go wrong | Control |
|---|---|---|
| Price risk | Old fee information remains in your business model. | Recheck official pricing before launch and periodically after launch. |
| Settlement risk | Cash arrives later than expected. | Build working-capital assumptions around actual settlement terms. |
| Webhook risk | Duplicate or missing events cause wrong order status. | Use idempotency, server-side verification and transaction references. |
| Reconciliation risk | Finance cannot match incoming money to invoices. | Use unique references and automated reconciliation. |
| Dispute risk | Chargeback deadlines are missed. | Assign an owner and monitor dispute notifications. |
| Compliance risk | Merchant category or documentation creates onboarding problems. | Confirm eligibility before development and launch. |
| Concentration risk | One provider outage stops all collections. | Consider an approved backup architecture where economically justified. |
A backup gateway is not automatically necessary for every small business. It becomes more attractive when payment downtime has a high financial cost and the business can support the engineering and reconciliation complexity of a second provider.
How to Calculate the Total Cost of Your Gateway
Use this worksheet before making the final decision.
| Variable | Your number | Why it matters |
|---|---|---|
| Monthly transaction count | ________ | Determines scale of fee impact. |
| Average transaction | ₦________ | Determines fixed-fee and cap effects. |
| Monthly gross processing | ₦________ | Useful for effective-rate calculations and volume negotiation. |
| International percentage | ________% | Can materially change total gateway cost. |
| Transfer percentage | ________% | Shows whether virtual-account economics matter. |
| Required settlement time | ________ | Converts settlement into a cash-flow requirement. |
| Monthly payment-operation labour | ₦________ | Captures reconciliation and payment support cost. |
| Estimated refunds/chargebacks | ₦________ | Shows the cost of payment operations beyond collection fees. |
The gateway scorecard
Give each shortlisted provider a score from 1 to 5 for:
- Local transaction economics.
- International transaction economics.
- Payment-channel fit.
- Settlement fit.
- Reconciliation.
- Developer experience.
- Recurring billing.
- Refund/dispute workflow.
- Merchant support.
- Compliance/onboarding fit.
Then weight the scores according to your business. A SaaS company might give developer experience and recurring billing double weight. A wholesaler might give settlement and transfer reconciliation double weight. An international merchant might give currency and cross-border support double weight.
This prevents a provider from winning simply because it scored well in categories that your business barely uses.
Your 24-Hour, 7-Day and 30-Day Payment-Gateway Implementation Plan
Your 24-hour action
Write down your last 30 days of transaction data: number of payments, average payment, highest payment, lowest payment, local percentage, international percentage and dominant payment channel.
Then calculate what Paystack, Flutterwave and Monnify's current published local rates would have cost on those actual transaction sizes. Obtain an Interswitch commercial quote rather than guessing.
Your 7-day action
- Open or verify merchant accounts with the shortlisted providers.
- Complete business verification.
- Test every major customer payment channel.
- Test successful and failed payments.
- Test webhooks.
- Test refunds.
- Test reconciliation.
- Confirm settlement timing.
- Record support response pathways.
- Update your finance team's reconciliation procedure.
Your 30-day action
After launch, do not assume the gateway decision was correct because payments are arriving.
Measure:
- Payment success rate.
- Payment failure rate.
- Transfer completion rate.
- Average time from customer payment to settlement.
- Refund turnaround.
- Chargeback count.
- Reconciliation exceptions.
- Support incidents.
- Actual effective payment cost.
- Revenue lost during payment failures.
Then compare those numbers with the assumptions you made before launch.
10 Mistakes Nigerian Businesses Should Avoid
1. Choosing the smallest headline percentage
Calculate the actual fee at your transaction sizes.
2. Copying a 2025 fee table into a 2026 decision
Payment pricing changes. Use the current provider documentation.
3. Ignoring transaction caps
Caps can completely change the economics of high-value payments.
4. Ignoring fixed charges
A ₦100 component is meaningful on small payments.
5. Forgetting international customers
Local Nigerian pricing cannot tell you what your international processing will cost.
6. Treating screenshots as payment verification
Verify payments through the gateway's server-side mechanisms.
7. Building without webhook protection
Use unique transaction references and idempotent processing.
8. Ignoring settlement timing
Settlement is working capital.
9. Failing to test refunds and disputes
Everything looks easy when every payment succeeds. Your real operational test begins when something goes wrong.
10. Treating a gateway as permanent
Your business can change. Average order value, international exposure, transaction volume and customer preferences can all change. Reassess the gateway when your economics change.
Final Feature-and-Fit Comparison
| Decision factor | Paystack | Flutterwave | Monnify | Interswitch |
|---|---|---|---|---|
| Published local pricing clarity | Strong | Strong | Strong | Commercial confirmation needed |
| Local fee cap | ₦2,000 | Not shown as a comparable cap on current public Nigeria pricing | ₦2,000 for listed local methods | Confirm quote |
| Small-ticket economics | Strong because ₦100 component is waived below ₦2,500 | Simple 2% calculation | 1.5% local published rate | Confirm quote |
| International reach | Strong | Very strong regional proposition | International payment support | Evaluate exact market requirements |
| Transfer / virtual-account use | Strong | Strong | Very strong focus | Strong transfer infrastructure |
| Same-day local settlement proposition | Not standard; Payout on Demand for eligible businesses costs 1% | Normal local settlement within 1 business day | Publicly advertised T+0 by 10PM plus Express Settlement | Confirm commercial arrangement |
| Developer tooling | Strong | Strong | Strong | Strong enterprise/API proposition |
| Split payments | Evaluate exact platform need | Evaluate exact platform need | Evaluate exact product | Explicitly highlighted on IPG page |
| Refund API | Available through platform/API workflows | Available through platform workflows | Available through platform workflows | Explicitly highlighted |
| Best fit depends on | Developer experience, local checkout, predictable pricing | Payment-method breadth and international reach | Transfer infrastructure, reconciliation and cash flow | Enterprise infrastructure and commercial fit |
Final Verdict: Which Payment Gateway Should Nigerian Businesses Use?
The strongest answer is not a brand name. It is a selection process.
Choose Paystack when your priority is a strong general-purpose Nigerian checkout with transparent published pricing, developer-oriented tooling, common local payment methods and a clear local fee cap. It is especially attractive when the business values a mature integration experience and needs to understand its payment economics without negotiating every basic number.
Choose Flutterwave when payment-method breadth and international or African-market reach are central to your business. Its Nigerian payment-method list is broad, and its wider regional footprint can reduce the need to design the business around a Nigeria-only payment architecture.
Choose Monnify when transfer-led collections, virtual accounts, reconciliation and local cash-flow timing are central. Its published same-day settlement proposition can be particularly meaningful to businesses whose inventory or operating cycle depends on quickly recycling customer payments.
Choose Interswitch when enterprise-grade Nigerian payment infrastructure, multiple local payment rails, split-payment functionality, hosted fields and refund tooling fit your architecture. Do not choose it from an old internet fee table. Get the current commercial quote and evaluate the entire relationship.
The most important conclusion
The best payment gateway is the one that produces the lowest sustainable total cost for your actual business while giving your customers reliable payment options and your team the operational controls needed to reconcile, settle, refund and resolve disputes.
For that reason, Daily Reality NG would not recommend signing up for any of these four providers simply because a comparison article labels it “best overall.” Instead, take your own last 30 days of payment data and run the transaction-size test.
If your average payment is ₦2,000, the answer can differ from a merchant whose average payment is ₦500,000. If 80% of your customers transfer money, your priorities should differ from a card-heavy ecommerce store. If your business needs funds the same day, settlement can matter more than a small fee difference. If you sell internationally, local Nigerian rates are not enough.
That is the real comparison.
What Makes This Comparison Different
This page was deliberately structured around several questions that simple gateway lists often leave unanswered.
| Original decision tool | What it solves |
|---|---|
| Six-question gateway test | Prevents businesses from choosing before understanding their own payment profile. |
| Transaction-size calculations | Shows why fixed charges, percentages and caps behave differently at different order values. |
| Annual-volume illustration | Converts small per-payment differences into a business-scale figure. |
| Cash-flow framework | Shows why settlement timing is a financial variable rather than a technical footnote. |
| Channel-fit analysis | Connects payment methods to actual Nigerian customer behaviour. |
| Risk matrix | Shows where operational failures can cost more than transaction fees. |
| Gateway scorecard | Lets different business models weight the decision differently. |
| 24-hour / 7-day / 30-day plan | Turns comparison research into an implementation process. |
The result is intentionally not a static ranking. A static ranking becomes outdated as pricing, product capabilities and business requirements change. A decision framework remains useful because the merchant can put new figures into the same model.
Frequently Asked Questions
Is Paystack cheaper than Flutterwave in Nigeria?
Not at every transaction size. Paystack currently publishes 1.5% + ₦100 for local transactions, with the ₦100 waived below ₦2,500 and the fee capped at ₦2,000. Flutterwave currently publishes 2% for Nigerian local transactions. Because Paystack has a fixed component and a cap, the actual difference depends on the transaction amount.
Is Monnify cheaper than Paystack?
It can be on certain transaction sizes and covered payment methods under the published standard rates. Monnify currently publishes 1.5% for local cards and USSD, capped at ₦2,000, while Paystack publishes 1.5% + ₦100 with a ₦2,000 cap and a waiver of the ₦100 component below ₦2,500. Your own transaction distribution should determine the comparison.
Which payment gateway is best for Nigerian ecommerce?
There is no universal winner. Paystack, Flutterwave and Monnify can all be strong options. Compare your average order value, dominant payment method, settlement needs, refund workflow and reconciliation requirements before deciding.
Which gateway is best for bank-transfer payments?
Monnify deserves particular attention because its product proposition strongly emphasizes virtual accounts, bank transfers and automatic reconciliation. Paystack and Flutterwave also support transfer-based collection and virtual-account workflows, so the final decision should come from a live test against your accounting process.
Which payment gateway settles fastest in Nigeria?
Settlement depends on the provider, product, merchant eligibility and payment type. Monnify currently publicly advertises same-day local settlement by 10PM and Express Settlement options. Paystack has a standard T+1 schedule for Nigerian businesses plus an eligible Payout on Demand option that carries a 1% fee. Flutterwave states that local Nigerian settlements are completed in one business day. Always confirm the terms applicable to your own account.
Does Paystack have a transaction cap?
Paystack currently publishes a ₦2,000 maximum fee per local transaction. That is a fee cap, not a ₦2,000 limit on the value of the customer's payment.
Does Monnify have a transaction-fee cap?
Monnify currently publishes a ₦2,000 cap for local card and USSD collection and a ₦2,000 cap for its published bank-transfer rate option. Its pricing page also identifies other payment categories with different pricing, so merchants should check the exact payment method.
Does Flutterwave have a ₦2,000 local transaction cap?
The current public Nigerian pricing information reviewed for this article lists a 2% local transaction fee and does not present the same ₦2,000 local cap used in the Paystack and Monnify comparison above. Do not assume a cap unless it appears in the applicable commercial terms.
Is Interswitch more expensive?
That cannot responsibly be determined from the current public IPG page alone. Interswitch's current public product material emphasizes features rather than a standardized transaction-price table comparable with the public rate cards of the other providers. Enterprise merchants should request a current quote.
Can I use more than one payment gateway?
Technically, many businesses can architect for multiple providers, but the additional complexity affects engineering, reconciliation, customer support and reporting. A second gateway makes the most sense when the financial value of resilience, channel coverage or commercial leverage justifies the additional operational complexity.
Should a Nigerian startup choose a gateway based on developer experience?
Yes, if payments are a meaningful part of the product. A difficult integration can create payment-state bugs, reconciliation errors and support costs. Developer documentation, APIs, SDKs, webhook reliability and refund workflows should therefore be treated as commercial considerations, not just technical preferences.
Should I change gateways just to save 0.2%?
Not automatically. Calculate the annual saving and compare it with migration development, testing, reconciliation changes, customer communication, downtime risk and operational training. A small percentage saving can be worthwhile at high volume, but it can also be uneconomical when the migration cost is large.
How often should a business review its payment gateway?
At minimum, review the economics when your transaction volume, average order value, customer geography, payment-channel mix or business model changes materially. It is also sensible to recheck official pricing and product documentation periodically because commercial terms can change.
Your Payment Gateway Checklist
Before you press “go live,” make sure you can answer yes to these questions:
- ☐ I know my average transaction value.
- ☐ I calculated fees at my real transaction sizes.
- ☐ I checked fee caps and fixed charges.
- ☐ I checked international pricing if applicable.
- ☐ I tested the payment methods my customers actually use.
- ☐ I understand the settlement schedule.
- ☐ I understand refunds and disputes.
- ☐ My system verifies payments server-side.
- ☐ My webhook handling is idempotent.
- ☐ My finance team can reconcile transactions.
- ☐ My business category is eligible.
- ☐ I have confirmed current commercial terms.
If several boxes remain unchecked, the gateway decision is not finished.
About the Author
Samson Ese is the founder of Daily Reality NG, a Nigerian digital publication focused on practical information, technology, finance, business, lifestyle and everyday issues affecting Nigerians.
Daily Reality NG publishes independently structured guides designed to help readers understand not only what a product or service does, but how the decision affects real-world Nigerian users.
Editorial and Pricing Disclaimer
This article is an independent comparison and is not an endorsement, guarantee or financial recommendation for any payment provider. Pricing, product availability, settlement arrangements, supported channels, eligibility requirements and commercial terms can change. Enterprise or high-volume merchants may receive negotiated terms that differ from public pricing.
Illustrative calculations in this article are mathematical examples based on the published standard rates identified during the September 5, 2026 research review. They are not a transaction statement or quotation from any provider. Merchants should confirm the exact terms that apply to their account before making a commercial decision.
Regulatory references are included for context and should not be interpreted as legal advice. Businesses operating in regulated or specialized sectors should obtain appropriate professional advice and confirm their sector-specific requirements.
Comments
Post a Comment