Integrating Flutterwave
Auth: API key · Partner program: not required · Setup time: about 10 minutes · Last verified: 2026-05-15
Africa breadth — 30+ countries, methods spanning cards, mobile money, bank transfers, USSD, QR, M-Pesa, and Pay-by-Bank. Strong in West Africa; growing in East/Southern Africa.
Auth model
Section titled “Auth model”Bearer-token from the merchant Secret Key — FLWSECK_TEST-… for test, FLWSECK-… for live. Generate under Settings → API in the Flutterwave dashboard.
Required adapter quirks
Section titled “Required adapter quirks”- Multi-currency settlement on one account. Unlike Paystack, a single Flutterwave merchant can settle in multiple currencies (NGN + USD + GHS + KES + UGX + ZAR + …). Always read
Charge.currencyper row; don’t assume an account-level default. - Decimal money. Flutterwave returns
amountas a float in major units — the adapter multiplies by 100. JPY / KRW are not in coverage so the simple ×100 is safe. - No top-level customer list. Customers are derived from transactions.
listCustomersreturns empty; build a customer index fromCharge.customerIdor use the customer-search endpoint per-transaction. verif-hashwebhook header is the secret-hash itself, NOT an HMAC. You configure a single shared string in the dashboard; Flutterwave echoes it verbatim on every delivery. Compare timing-safely (the adapter does).
References
Section titled “References”- API reference: https://developer.flutterwave.com/reference/
- Webhooks: https://developer.flutterwave.com/docs/webhooks
- Multi-currency settlement: https://developer.flutterwave.com/docs/settlements
opensteward.dev ·Plans and free license ·Terms ·Privacy ·support@opensteward.dev
© 2026 Falco Consulting AB. Built from open-steward/opensteward@a3961d8. This site sets no cookies, runs no analytics and loads nothing from other sites, except platform logos from Brandfetch on the Platforms page.