Paystack vs Flutterwave: How to Integrate Payments in Your App or Website

Payments are where most Nigerian apps quietly lose money: failed transactions, abandoned checkouts and customers who never try again. Choosing between Paystack and Flutterwave matters less than integrating whichever you choose properly. Here is what we have learned building checkouts for retailers, airlines, cinemas and marketplaces.

Paystack or Flutterwave?

• Fees: both charge around 1.5% for local cards with a cap, more for international cards. Confirm current rates on their pricing pages; they change.
• Payment methods: both support cards, bank transfer, USSD and mobile money. Flutterwave covers more African countries and currencies; Paystack is strongest in Nigeria, Ghana, Kenya and South Africa.
• Developer experience: Paystack's API and documentation are widely considered the cleaner of the two; Flutterwave's breadth of features is larger.
• Settlement and support: ask other merchants in your sector. Settlement times and dispute handling vary by account type and volume.

Many of the businesses we work with run both, with the second gateway as an automatic fallback. When one provider has an outage or a bank is declining cards, the checkout retries on the other instead of showing an error. That single design decision recovers a surprising share of orders.

Integration decisions that matter

• Use the hosted checkout or SDK for card entry. Never let card numbers touch your servers; it keeps you out of PCI scope.
• Verify every payment on your backend with the provider's API before you fulfil an order. Client-side success callbacks can be faked.
• Handle webhooks idempotently: providers retry, and a duplicate webhook must not create a second order or a second wallet credit.
• Reconcile daily. Match your orders against the provider's settlement reports automatically and alert on differences.
• Design for the fail case: show the customer what happened, keep their cart, offer bank transfer or the fallback gateway, and let them retry without re-entering everything.
• Test with real bank cards from several Nigerian banks, not just the sandbox. Some banks decline online transactions by default.

Subscriptions, wallets and refunds

Recurring billing works on both platforms through tokenised cards; plan for card expiry and failed renewals with a grace period and reminders. Wallets and stored value need a ledger you own, with every credit and debit recorded and auditable, and a licensing check with your lawyers if you hold customer funds. Refunds should be a button in your admin, not a manual process on the provider's dashboard.

What it costs to build

One gateway with cards and transfers is part of our Basic app and website packages. Multiple providers, subscriptions, wallets and reconciliation dashboards are in Premium and Business. Whatever you build, budget engineering time for the failure paths; that is where the money is.