Flutterwave Gateway for Magento 2

Hauptfunktionen

Native Magento 2 payment method implemented against Magento\Payment service contracts (MethodInterface / Gateway Command pattern), not a hosted iframe hack

Cards, mobile money, bank transfer, M-Pesa and USSD exposed as Flutterwave payment options at checkout

Hosted redirect checkout OR inline modal checkout, selectable per store-view in system.xml

Multi-country and multi-currency presets tuned for cross-border African merchants (NGN, KES, GHS, ZAR, USD and more)

Signature-verified Flutterwave webhook controller that reconciles against quote/order totals before invoicing — prevents spoofed paid callbacks

Server-side transaction verification on the Flutterwave verify endpoint before order state changes

Online full and partial refunds initiated from the Magento admin Sales grid, recorded as payment transactions

Dispute and chargeback notes surfaced on the order so support teams can act on them

Encrypted storage of secret API keys via Magento config encryption, with separate test/live key sets

Per-store-view and per-website configuration through system.xml, config.xml and di.xml

Admin ACL resources in acl.xml so only authorised roles can edit gateway settings

REST and GraphQL compatibility for headless / PWA Studio storefronts

Optional cron job to reconcile pending or stuck transactions automatically

Adobe Commerce and Magento Open Source 2.4.x compatible, PSR-12 clean, full source code delivered

Auf Bestellung gebaut, komplett für Sie erledigt

Keine Selbsteinrichtung — eine funktionierende App, die von ECOSIRE erstellt, installiert und betreut wird.

Sie bestellen

Starten Sie mit einem einmaligen Entwicklungspreis. Den Umfang legen wir beim Kickoff gemeinsam fest.

Wir bauen & installieren

ECOSIRE erstellt, konfiguriert und installiert sie auf Ihrem Magento 2.

Go-live + Support

Sie gehen in etwa 2–4 Wochen live, mit einem Support-Zeitraum nach dem Launch.

Über dieses Produkt

This is a build-to-order Flutterwave payment gateway for Magento 2 Open Source and Adobe Commerce — it is not an instant Adobe Commerce Marketplace download. After purchase, ECOSIRE builds, installs and supports the module for your specific store, store-view configuration and Flutterwave account.

The extension ships as a proper Magento module under app/code/Ecosire/Flutterwave, registered through registration.php and module.xml. Payment behaviour is implemented against Magento's payment service contracts: a custom MethodInterface (or Gateway\Command pattern via Magento\Payment\Gateway) wired through di.xml, with system.xml and config.xml exposing per-store-view configuration (public/secret keys, encryption-mode, country/currency rules, checkout style). Secret keys are stored encrypted via Magento's config encryption, never in plain text.

At checkout, customers can pay with cards, mobile money, bank transfer, M-Pesa and USSD through Flutterwave's hosted (redirect) flow or an inline modal. Order state is driven by Flutterwave webhooks received on a dedicated controller, verified by signature, and reconciled against quote/order totals before an invoice is created — so a manipulated client callback can't mark an order paid. Transactions are recorded as Magento payment transactions, enabling online refunds (full and partial) and dispute/chargeback notes from the admin Sales grid. Admin access is gated by ACL resources defined in acl.xml.

The build includes REST/GraphQL compatibility so headless and PWA Studio storefronts can initialise and verify payments, optional cron-based reconciliation of pending transactions, multi-currency and multi-country presets for cross-border African merchants, and full source code. ECOSIRE handles installation on your staging and production environments, smoke-testing in Flutterwave test mode, and go-live.

Was Sie bekommen

Custom Ecosire_Flutterwave module under app/code with registration.php, module.xml, di.xml, system.xml, config.xml and acl.xml

Installation and configuration on your staging and production Magento 2 / Adobe Commerce environments

Flutterwave test-mode smoke test across card, mobile money, bank transfer, M-Pesa and USSD before go-live

Webhook endpoint set up, signature secret configured, and reconciliation verified end-to-end

Full commented source code and a short admin configuration guide (keys, modes, country/currency setup)

30 days of post-launch support covering bug fixes and configuration adjustments

Für wen das ist

Cross-border African online retailer

A merchant selling into Nigeria, Kenya, Ghana and South Africa who needs one gateway covering cards, mobile money, M-Pesa and bank transfer so local buyers can pay the way they already do.

Magento store owner switching from a manual or redirect-only payment flow

An owner currently emailing payment links or using a basic redirect who wants a properly integrated, refund-capable Flutterwave method inside Magento admin without leaving the order workflow.

Agency or in-house developer team on Adobe Commerce / PWA Studio

A technical team that wants clean, service-contract-based source code and REST/GraphQL support they can extend, rather than a black-box marketplace binary.

Wie Flutterwave Gateway for Magento 2 im Vergleich abschneidet

Kriterium	ECOSIRE	Benutzerdefinierter Build	Konkurrent
Built specifically for your store, Flutterwave account and country mix	Im Lieferumfang enthalten	Im Lieferumfang enthalten	Teilweise Unterstützung
Cards, mobile money, M-Pesa, bank transfer and USSD in one gateway	Im Lieferumfang enthalten	Teilweise Unterstützung	Teilweise Unterstützung
Signature-verified webhooks with server-side reconciliation against order totals	Im Lieferumfang enthalten	Teilweise Unterstützung	Teilweise Unterstützung
Online full and partial refunds from the Magento admin	Im Lieferumfang enthalten	Teilweise Unterstützung	Im Lieferumfang enthalten
REST / GraphQL support for headless and PWA Studio	Im Lieferumfang enthalten	Teilweise Unterstützung	Teilweise Unterstützung
Installed, tested and supported for you after purchase	Im Lieferumfang enthalten	Nicht im Lieferumfang enthalten	Nicht im Lieferumfang enthalten
Full source code you can own and extend	Im Lieferumfang enthalten	Im Lieferumfang enthalten	Teilweise Unterstützung

Häufig gestellte Fragen zu Flutterwave Gateway for Magento 2

Is this an instant download from the Adobe Commerce Marketplace?

No. This is a build-to-order extension. After purchase, ECOSIRE builds and configures the Flutterwave module for your specific Magento 2 / Adobe Commerce store and Flutterwave account, then installs it for you. You receive full source code — not a Marketplace one-click install.

What is the delivery lead time?

Typical delivery is 5 to 10 business days from when we receive your Flutterwave test credentials and access to a staging environment. Stores with heavy customisation, multi-website setups or headless/PWA Studio frontends may take a little longer; we confirm a firm timeline before starting.

How does ongoing support and updates work?

Every build includes 30 days of post-launch support for bug fixes and configuration changes. After that, we offer optional maintenance to keep the module compatible with new Magento 2.4.x / Adobe Commerce releases and any changes to the Flutterwave API. Because you hold the full source, your own team can also maintain it.

Which payment methods and countries are supported?

Whatever your Flutterwave account is enabled for — typically cards, mobile money, bank transfer, M-Pesa and USSD across Nigeria, Kenya, Ghana, South Africa and other supported African markets. We configure the country and currency presets to match your cross-border setup.

Will it work with a headless or PWA Studio storefront?

Yes. The integration is built on Magento payment service contracts and exposes REST/GraphQL support, so a headless or PWA Studio frontend can initialise and verify Flutterwave payments. Tell us your frontend stack and we scope the integration accordingly.

Is it secure — can someone fake a successful payment?

No. Order completion is driven by signature-verified Flutterwave webhooks and a server-side verify call, reconciled against the Magento quote/order totals before any invoice is created. Client-side callbacks alone never mark an order paid, and secret keys are stored using Magento's config encryption.