LPM LocalPayMapLocal payment directory
← Back

Payment channel profile

Flutterwave: what merchants should know

Flutterwave is a payment service provider (PSP) and payment gateway, not a bank, not a wallet and not a card network. It is a payments infrastructure company that lets businesses accept and send payments across Africa and internationally through one integration. For the merchant, Flutterwave is an aggregator and gateway: it connects you to cards, bank accounts, bank transfers, USSD, QR, Apple Pay, mobile money and M-Pesa, and then settles to your bank account. It provides a dashboard, APIs, payment links, store and invoicing tools. It is an acquirer-like front end that bundles many local rails. Flutterwave operates in Nigeria, Ghana, Kenya, South Africa, Uganda, Tanzania, the UK, the US and parts of Europe. It does not itself hold consumer wallets. Flutterwave matters across Africa and for Africa-connected cross-border commerce, where it is one of the largest gateways for accepting local

NigeriaPrimary marketMain service market
Payment aggregatorPayment typeCustomer payment method
Medium, verify entity and documentsEntity requirementOnboarding conditions
T+1SettlementPayout timing

What it is

Flutterwave is a payment service provider (PSP) and payment gateway, not a bank, not a wallet and not a card network. It is a payments infrastructure company that lets businesses accept and send payments across Africa and internationally through one integration. For the merchant, Flutterwave is an aggregator and gateway: it connects you to cards, bank accounts, bank transfers, USSD, QR, Apple Pay, mobile money and M-Pesa, and then settles to your bank account. It provides a dashboard, APIs, payment links, store and invoicing tools. It is an acquirer-like front end that bundles many local rails. Flutterwave operates in Nigeria, Ghana, Kenya, South Africa, Uganda, Tanzania, the UK, the US and parts of Europe. It does not itself hold consumer wallets.

How customers pay

Flutterwave matters across Africa and for Africa-connected cross-border commerce, where it is one of the largest gateways for accepting local cards, bank transfers, mobile money and M-Pesa behind one API. It is used by marketplaces, travel, entertainment and global brands entering Africa. For a cross-border merchant, Flutterwave is a practical single integration to reach many African local methods plus international cards. Its payout product also helps platforms send money to sellers and contractors across countries.

How merchants connect

  • Sign up and use hosted checkout, payment links or the Flutterwave Store.
  • Integrate the Flutterwave API and SDKs for web and mobile.
  • Use Flutterwave Invoices, Events and Mobile POS for different sales models.
  • Onboard as a registered business with a bank account in a supported region.

Best-fit business models

Flutterwave fits African-facing and Africa-connected businesses of every size, from a store link to a full API integration with payouts. It is strong when you want many local methods and cross-border payouts through one provider. You need a registered business and a local or compatible bank account. The Flutterwave Store and payment links are useful for merchants without a website. Its developer tools, sandbox and clear documentation make it approachable for small teams without a payments engineer. Its payout product also helps platforms send funds to sellers and contractors across several countries from one balance. Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms. Confirm against the provider's official pricing page or a written quote before you go live.

Cross-border and local-entity limits

Flutterwave is a gateway/PSP that can accept international cards and Apple Pay, but local methods are domestic and settled in local currency, and payouts depend on your registered region and licensing. Supported methods differ by country, so a method available in Nigeria may not exist in another market. Plan for FX, local entity requirements, licences (such as central-bank payment institution licences) and per-country limits before relying on it for settlement. Verify the method list for each country you sell in, because it changes.

Alternatives and complements

  • Paystack
  • Paymob
  • Kopo Kopo
  • cards
  • bank transfer
  • mobile money

Provider questions to ask

  • What are your fees per method and region, including mobile money and cross-border cards, in writing?
  • How fast is settlement, and which countries can I receive payouts in?
  • Which local methods are actually live in my target countries?
  • Do you support refunds, disputes, chargebacks and recurring billing?

Questions merchants ask

Is Flutterwave enough as a standalone checkout option?

Usually no. Use Flutterwave where it matches local buyer habits, then add complementary methods for cards, wallets, bank transfers, cash vouchers, or BNPL depending on the market and ticket size.

Can a foreign merchant connect to Flutterwave directly?

Sometimes, but many merchants use a PSP, acquirer, aggregator, or local partner. Confirm entity, bank-account, currency, tax, industry, refund, and settlement requirements before implementation.

What should I verify before signing for Flutterwave?

Ask whether the method is live for your entity and industry, which checkout flows are supported, how refunds and failed payments work, what fees apply, and which currency you receive.

Public sources