What it is
Flutterwave is a payment service provider, not a payment method. Your customers choose a card, a bank transfer, a mobile money wallet or another local method, and Flutterwave is the company that sits behind your checkout, routes the transaction, manages the risk checks and settles the money to you. It started in Nigeria and sells itself on breadth across African markets rather than depth in one. That framing matters for planning: you are choosing an infrastructure partner, and the things worth testing are coverage per country, authorisation performance, payout reliability and the quality of support when something breaks mid-campaign.
- Flutterwave is a payment service provider rather than a payment method customers pick.
- It aggregates cards, bank transfer, mobile money and other local methods behind one API.
- It started in Nigeria and competes on breadth across African markets.
- Test coverage per country, authorisation rates, payout reliability and support quality.
Where it is used
Flutterwave serves merchants across a wide set of African markets, with Nigeria as its home market and coverage also in Ghana, Kenya, Uganda, South Africa and others. It settles in local currency, naira in Nigeria and the corresponding currency elsewhere, and it supports a long list of transaction currencies. On the customer side, the value is the spread of local methods rather than a consumer brand. Shoppers will not ask for Flutterwave by name. They will use whichever card, bank or wallet option you present, and Flutterwave is what makes that list possible in each country.
- Flutterwave covers Nigeria plus markets including Ghana, Kenya, Uganda and South Africa.
- It settles in local currency, with naira in the Nigerian market.
- It supports a long list of transaction currencies for cross-border trade.
- Shoppers use the methods you present rather than looking for the provider brand.
Which businesses it suits
Flutterwave suits merchants that sell into several African markets and would rather run one integration than negotiate country by country. Pan-African e-commerce, travel, digital content, remittance-adjacent businesses and platforms that need both collections and payouts fit well. It suits you less if you operate in a single country and already have a good local gateway, since the breadth you are paying for is unused. It is also a weaker fit for businesses with no technical resource at all, and for categories excluded by its compliance and acceptance policy. It is a reasonable choice for platforms that need collections and payouts handled in one place.
- Flutterwave suits merchants selling into several African markets through one integration.
- Pan-African e-commerce, travel, content and platform businesses fit well.
- A single-country merchant with a good local gateway may not need the breadth.
- Restricted categories and businesses with no technical resource fit less well.
How merchants usually connect
Merchants register an account directly, complete business verification, and integrate through the API, a hosted checkout, payment links, invoices or an online store product. Onboarding needs company registration documents, identification for directors and beneficial owners, bank account details, and a review of your business model, website and expected volumes. Some markets require a local entity, so confirm structure before you build. Because the product set covers collections, transfers and payouts, be clear about which of those you need, since approval and limits can differ between them. Ask how long the review takes in your target markets before you set a launch date.
- Merchants register directly and integrate through the API, hosted checkout, links, invoices or a store.
- Onboarding covers company documents, owner identification, bank details and a business review.
- Some markets require a local entity, so settle your structure before building.
- Be clear which of collections, transfers and payouts you need, since approvals differ.
Cross-border merchant notes
The appeal of Flutterwave for cross-border sellers is that it reduces the number of local relationships you need, but it does not remove local rules. Collection happens in local currency in each market, and repatriation follows that market's foreign exchange and central bank requirements, in Nigeria those of the Central Bank of Nigeria. Coverage is also uneven in practice: a method that is live in Nigeria may be limited or unavailable in another country, and some functionality varies by corridor. Ask for a written confirmation of which methods and currencies are live in each market you plan to sell into.
- Collection happens in local currency, with repatriation following each market's central bank rules.
- Coverage is uneven in practice, so a method live in Nigeria may be limited elsewhere.
- Ask for written confirmation of live methods and currencies for each target market.
- Plan for corridor-by-corridor differences rather than assuming one uniform product.
Fees, settlement and refunds
Treat any published rate as a starting point only. Real pricing shifts with country, industry, volume, settlement currency, integration method and contract terms. Verify against the operator's official pricing page or a written quote before you commit. Costs vary by country and by method, and cross-border or currency conversion usually adds on top. Settlement runs to your account on a schedule that depends on market, currency and compliance status. Refunds are initiated from the dashboard or API, and card transactions carry chargeback exposure, unlike mobile money collections. Ask for a worked example using your real method mix before you sign.
- Treat published rates as a starting point and verify the real price on the official page or in a quote.
- Costs vary by country and method, with conversion added on cross-border transactions.
- Settlement timing depends on market, currency and your compliance status.
- Card transactions carry chargeback exposure, while mobile money collections generally do not.
Alternatives and complements
Paystack is the closest comparison and is often stronger in Nigeria specifically, so if your business is concentrated there, quote both. dLocal suits merchants who want one cross-border contract spanning Africa, Latin America and Asia rather than Africa alone. A local bank transfer option remains sensible for high-value corporate orders where percentage fees are hard to justify. Specialist mobile money aggregators can be deeper in a single country, so if wallets dominate your volume in one market, compare that route as well. Assess both on live coverage rather than on headline rates alone.
- Quote Paystack alongside Flutterwave if your business is concentrated in Nigeria.
- Consider dLocal if you want one contract spanning Africa, Latin America and Asia.
- Keep bank transfer for high-value corporate orders where percentage fees bite.
- Compare specialist mobile money aggregators if wallets dominate one market.
Questions to ask before you integrate
Ask for a written list of live methods and settlement currencies for each market you plan to enter. Ask whether a local entity is required anywhere and what the alternative is. Ask for the payout schedule, the cut-off times and any reserve or holdback terms. Ask how chargebacks are handled and who bears the liability. Ask about approval rates in your category. Ask whether transfers and payouts are approved on your account or only collections. Finally, ask who supports you during launch, and through which channel, because that matters more than the fee.
- Which methods and settlement currencies are live in each market you plan to enter?
- Where might a local entity be needed, and what alternative contracting route can the provider offer?
- What is the payout schedule, and are there reserve or holdback terms?
- Are transfers and payouts approved on your account, or only collections?
- Who supports you during launch, and through which channel?
Merchant usage and connection route
Flutterwave in the payment stack
Flutterwave is a PSP and payment infrastructure brand merchants may evaluate for African and cross-border payment acceptance, local methods, cards, collections, and business payment workflows. Use it to compare market coverage, onboarding fit, checkout capabilities, reconciliation, refund handling, support model, and whether local alternatives are needed.
Connection route
A merchant may connect directly to Flutterwave, through a platform, marketplace, plugin, or orchestration layer, or use another PSP that routes to local payment partners. Confirm the contracting entity, covered countries, payment methods, acquiring or aggregation model, settlement reporting, and escalation path.
Verification questions
- Which countries, merchant entity, currencies, customer locations, and payment methods are required?
- Is the merchant integrating directly with Flutterwave or through a platform, plugin, marketplace, or orchestration layer?
- Which card, mobile money, bank transfer, checkout, refund, dispute, payout, and reconciliation flows are in scope?
- What onboarding, documentation, product-category, risk-review, reserve, and support expectations must be verified?
- Who handles local method failures, card disputes, refunds, account reviews, and operational incidents?
Merchant caveats
- Public country coverage should be verified against the merchant's entity, category, and payment methods.
- A PSP brand may still rely on local partners for parts of the payment flow.
- Settlement, reserves, refunds, and dispute operations require direct provider confirmation.
- Provider examples are discovery examples only, not recommendations or support evidence.
Provider examples to verify
Related markets
Keep researching
- Flutterwave Payment Acceptance
- Flutterwave
- Flutterwave vs Paystack
- Paystack vs Flutterwave in Nigeria: Merchant Shortlist Review
- psp contacts
This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.
Sources
Capability verification checklist
Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.
- Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
- Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
- Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.
Official links to open
Commercial terms to confirm
| Pricing model | psp or aggregator quote |
|---|---|
| Pricing basis | official public pricing or terms |
| FX markup | International (cross-currency) payments are priced at the higher international card/method tier rather than a separate published FX markup; exact rates vary by country. |
| Payout fee | Payout/transfer fee varies by destination country (e.g. Nigeria bank transfer NGN 10-50 by amount; Kenya KES 100; SEPA EUR 35; UK GBP 35; US USD 40). |
Fields still to confirm
- Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.
Integration route to confirm
| API / checkout route | REST API; client SDKs and prebuilt UIs available (per Getting Started) |
|---|---|
| Sandbox | yes |
| Webhooks | yes |
Fields still to confirm
- SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
- PCI scope: confirm with the provider, acquirer, PSP, or official documentation before launch.
- 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.
Operational features to confirm
| Recurring billing | yes |
|---|---|
| Marketplace split | yes |
| Partial refund | yes |
Fields still to confirm
- Preauth / capture: confirm with the provider, acquirer, PSP, or official documentation before launch.
Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.
Questions merchants ask
Is Flutterwave a payment method?
No, it is a payment service provider. Customers choose cards, bank transfer, mobile money or another local method, and Flutterwave sits behind your checkout to route the transaction, run risk checks and settle the funds. You are choosing an infrastructure partner rather than adding a logo to your checkout.
Which countries does Flutterwave cover?
It covers Nigeria as its home market plus a wide set of African markets including Ghana, Kenya, Uganda and South Africa. Coverage of individual methods varies by country, so ask for written confirmation of which methods and settlement currencies are live in each market you intend to sell into.
Can a foreign company use Flutterwave?
Many foreign-registered businesses can, depending on their country, their target markets and their category. Some markets require a local entity. Ask directly which countries you can be activated for and whether a local entity is needed, because that determines your company structure before you build.
How does Flutterwave pricing work?
Published rates are a first filter, not a final price. What you pay moves with country, industry, volume, settlement currency, integration method and contract terms. Costs vary by country and by method, with conversion added on cross-border transactions, so get a written quote for your actual mix.
How long does Flutterwave settlement take?
Settlement depends on the market, the currency and your compliance status, and new accounts may face a hold period while risk reviews complete. Confirm the payout schedule, the cut-off times and any minimum payout in writing, because these matter more to cash flow than the headline fee.
Should I choose Flutterwave or Paystack?
Quote both. Paystack is often the stronger option if your business is concentrated in Nigeria, while Flutterwave competes on breadth across African markets. Compare live methods per country, approval rates in your category, payout schedules and support quality, rather than comparing headline fees alone.