Payment orchestration comparison
Paystack is a payment gateway built for African markets, with published rates, local channels such as bank transfer and USSD, and payouts on a schedule you can plan around. FloPay is orchestration built around the revenue you keep: a card vault that stays yours, retries on failed renewals, and chargeback prevention that works before a dispute reaches the card network. If you sell across Africa, the question is whether one gateway covers you or whether protecting recurring revenue needs more.
Capability match
Every comparison covers the same capabilities, so you can weigh the trade-offs that affect your revenue. Official company sources are linked where available.
| Capability | FloPay | Paystack | Evidence and notes |
|---|---|---|---|
| Independent Card Vault | Validated | Not supported | No official source published. Paystack documents an in-house vault that stores cardholder data on its own systems, and reusable authorization codes that work with a Paystack integration. A vault you control and can carry to another provider is not documented. |
| Subscription Recovery / Dunning | Validated | Not supported | View official source Paystack's subscription documentation states that a failed subscription charge is not retried. The subscription moves to an attention status and the card is charged again on the next scheduled payment date, which is the following billing cycle rather than a recovery sequence for the cycle that failed. |
| Chargeback Prevention | Validated | Not supported | No official source published. Paystack documents dispute management, chargeback alerts, and a disputes API for uploading evidence. Stopping a dispute before it reaches the card network is not documented. |
| Multiple Card Providers / Cascading Processing | Validated | Not supported | No official source published. Paystack routes across its own gateway and processor connections. Connecting card providers you contract yourself, or cascading a declined charge to the next one, is not documented. |
| Smart Routing / Failover Protection | Validated | Not supported | No official source published. Paystack documents dynamic routing across its own gateways and processors, and a checkout that suggests another channel after a failure. Routing rules you configure across your own providers are not documented. |
| Dynamic Payment Selection | Validated | Not supported | No official source published. Checkout shows the payment channels you switch on in your dashboard, and non-card channels depend on the country. Selection driven by the customer or the transaction is not documented. |
| Local / Alternative Payment Methods | Validated | Validated | View official source Paystack documents cards, bank accounts, bank transfers, USSD, mobile money, QR, and Apple Pay across its African markets. |
| SDK / API Documentation | Validated | Validated | View official source A full REST API reference covers transactions, subscriptions, transfers, disputes, and refunds, with authentication, rate limits, pagination, and error handling. |
| No-Code Integrations | Validated | Validated | View official source Paystack Commerce provides storefronts and payment pages you build in the dashboard, plus plugins for platforms such as Shopify, WooCommerce, and Wix. |
| Hosted Payment Pages | Validated | Validated | View official source Payment Pages are created in the Paystack dashboard, hosted by Paystack, and shared with customers as a link. |
| Clear & Transparent Pricing | Validated | Validated | View official source Paystack publishes local, international, transfer, virtual account, and terminal rates for each market it serves, alongside a fee calculator. |
| Automated Sales Tax Reporting | Not supported | Not supported | No official source published. Paystack documents transaction reporting and exports, but not sales tax calculation or filing. |
| Cart Abandonment / Recovery | Not supported | Not supported | No official source published. Paystack reports abandoned transactions in the dashboard, but a flow that brings those customers back to complete the purchase is not documented. |
| AI Payment Monitoring and/or Optimization | Not supported | Not supported | No official source published. Paystack describes automated and manual fraud systems and routing aimed at the best payment path, but not AI payment monitoring or optimization. |
| MID Onboarding | Not supported | Not supported | No official source published. Paystack onboards your business onto its own platform. Helping you obtain a merchant ID with an acquirer of your choosing is not documented. |
| Company Formation Support | Not supported | Validated | View official source Paystack helps businesses incorporate in Nigeria, obtain a tax identification number, and open a corporate bank account. |
| Multi-Currency / FX Support | Validated | Not supported | No official source published. Paystack documents accepting payments in the currencies of the markets it serves and a settlement option in US dollars. Currency conversion you control is not documented. |
| Network Tokenization | Validated | Not supported | No official source published. Paystack issues reusable authorization codes tied to a Paystack integration. Card network tokens from Visa or Mastercard are not documented. |
| Automatic Card Updater | Not supported | Not supported | No official source published. Paystack sends a webhook listing subscriptions whose cards expire that month so you can ask those customers to update them. Refreshing a stored card automatically is not documented. |
| PCI DSS Compliance Level | Validated | Validated | View official source Paystack states that it has been audited by a PCI-certified auditor and is certified to PCI Service Provider Level 1. |
| 3DS2 / Fraud Rules Engine | Not supported | Not supported | No official source published. Paystack documents 3D Secure as one of the ways a cardholder authorizes a charge. A fraud rules engine you configure is not documented. |
| Settlement / Payout Speed | Not supported | Validated | View official source Automated payouts run on a published schedule for each country and currency, and no action is needed from you to receive them. |
| Customer Self-Service Portal | Validated | Validated | View official source Paystack generates a hosted subscription management link where your customer can add a new card, switch to direct debit, or cancel. |
| Revenue Recognition & Reporting | Validated | Not supported | No official source published. Paystack documents transaction reports, reconciliation, and exports, but not revenue recognition. |
| Sandbox / Test Environment | Validated | Validated | View official source Paystack documents test cards that simulate successful charges, declines, and refund outcomes before you go live. |
What to consider
Where your card data lives decides how freely you can move. FloPay validates an independent card vault. Paystack stores cardholder data in its own vault and gives your integration reusable authorization codes, which work inside Paystack and nowhere else. Add a second processor later, or move into a market Paystack does not cover, and you are asking customers to enter their cards again. Every re-entry is another chance to lose the sale.
A renewal that fails once should not end the subscription. FloPay validates subscription recovery and dunning. Paystack's own documentation is explicit that a failed subscription charge is not retried: the subscription is flagged for attention and the card is charged again on the next scheduled payment date. That reattempt is the next billing cycle, not a recovery sequence for the cycle that failed, so unless you build the chase yourself the missed cycle is simply gone. For recurring revenue, that is the difference between churn you manage and churn you absorb.
The cheapest chargeback is the one that never reaches the card network. FloPay validates chargeback prevention. Paystack documents the response side thoroughly: dispute notifications, a disputes API for uploading receipts and evidence, and automatic acceptance on your behalf if the response window passes. What it does not document is the earlier step, settling a customer query with the issuer before it hardens into a formal dispute, so your team ends up defending disputes rather than heading them off.
This row goes to Paystack. Its business registration service matches you to the right registration type, handles the incorporation paperwork in Nigeria, obtains a tax identification number, and opens a corporate bank account. FloPay does not currently validate company formation support. If you are starting a Nigerian business from scratch, that is real value Paystack adds before you weigh the vault, recovery, and dispute differences above.
FAQ
Paystack is a payment gateway for African markets. You open a Paystack account, Paystack handles the processing behind it, and you get local channels, published rates, and scheduled payouts. FloPay is orchestration aimed at the revenue you keep, with a card vault that stays yours, retries on failed renewals, chargeback prevention, and routing across the providers you contract. If Africa is your market and one gateway is enough, Paystack is a strong fit. If you are protecting recurring revenue across providers, the rows above are where the two differ.
Not the failed charge itself. Paystack's subscription documentation states that if a subscription charge fails it is not retried. The subscription is marked for attention and Paystack charges the card again on the next scheduled payment date, so the next attempt is the following billing cycle rather than a recovery sequence for the one that failed. Paystack does send a monthly webhook listing subscriptions whose cards are about to expire, so you can reach those customers before the charge fails. FloPay validates subscription recovery and dunning.
Yes. Paystack generates a hosted subscription management link where your customer can add a new card, switch to a direct debit account, or cancel the subscription. FloPay validates a customer self-service portal as well, so compare what each one lets your customers do beyond changing the card on file.
Yes. Paystack publishes rates for local and international transactions, transfers, dedicated virtual accounts, and card terminals in each market it serves, together with a calculator that shows the fee on a given amount. FloPay validates clear and transparent pricing too, so the useful comparison is what each price buys rather than whether you can find it.
Paystack documents cards, bank accounts, bank transfers, USSD, mobile money, QR, and Apple Pay. Card payments are available on every account, and the other channels are available where the market supports them. That local coverage across Nigeria, Ghana, Kenya, South Africa, and Côte d'Ivoire is a genuine Paystack strength, and FloPay validates local and alternative payment methods as well.
Paystack's default is automated payouts, processed on a published schedule that depends on your country and the currency of the payment, with no action required from you. Manual payouts and payout on demand are documented as alternatives. FloPay does not currently validate settlement or payout speed, so that row goes to Paystack.
Yes, in Nigeria. Paystack guides you to the right registration type, handles the paperwork, obtains a tax identification number, and sets you up with a corporate bank account. FloPay does not currently validate company formation support, so this is a second row where Paystack leads.
Not as documented. Paystack issues reusable authorization codes that identify a stored card inside a Paystack integration, and it notes that a new authorization code is created each time a card is used while the card signature stays the same. Card network tokens from Visa or Mastercard, which the schemes refresh when a card is reissued, are not documented, so that row is not supported here. FloPay validates network tokenization.
Paystack documents 3D Secure as one of the ways a cardholder authorizes a charge, alongside PIN, OTP, and hardware token, and it describes a combination of automated and manual fraud systems running on its own side. A fraud rules engine you configure is not documented, so that row is not supported here. FloPay does not currently validate 3DS2 or a fraud rules engine either.
It covers two cases. Where the company website rules a capability out, the row cites the page that says so. Where we were unsure or unable to validate a capability from the company website, the row carries no source, and that does not mean the capability is unavailable. If you can point us to an official page that proves otherwise, use the discrepancy link and we will update the row.
Own your card vault, route around processor failures, and recover more subscription payments. Talk to us about what FloPay would change for your business.