Flutterwave for WooCommerce

No. This is a build-to-order plugin. ECOSIRE builds it to your store's currencies, enabled payment methods and checkout style, then installs it on your WordPress site and configures it with you. You are not buying a generic file from WooCommerce.com or WordPress.org — you are buying a working, installed and tested integration.

A standard build is typically delivered in about 5 to 10 business days from the moment we have your Flutterwave API keys (test and live), staging access, and confirmation of which payment methods and currencies you need. If you require WooCommerce Subscriptions tokenized billing or unusual multi-currency rules, we will confirm the timeline before starting. We always test on staging before touching your live store.

Every build includes a post-launch support window for fixes, and we provide compatibility updates as WooCommerce, WordPress and the Flutterwave API evolve — including HPOS changes and gateway API revisions. You keep the code on your own site; we apply updates on request, and extended maintenance is available if you want us to monitor and patch proactively.

Whatever your Flutterwave merchant account is approved for: cards, mobile money (M-Pesa, MTN MoMo, Airtel Money), bank transfer and USSD across 30+ African markets, settling in currencies such as NGN, KES, GHS, ZAR, UGX, TZS, RWF and XOF/XAF. The exact list of live methods and currencies is governed by your Flutterwave account approvals, which we surface in the WooCommerce checkout.

Yes. The gateway extends WC_Payment_Gateway so it integrates with standard WooCommerce checkout regardless of theme, it is built HPOS-ready (works with both the high-performance custom order tables and the legacy order store), and method labels use standard WordPress i18n functions so it is translation-ready for WPML and Polylang. It is also safe to run on a multisite network.

Order completion is driven by Flutterwave transaction webhooks delivered to a dedicated REST endpoint that verifies the verif-hash signature and re-confirms each charge server-side before marking the order paid, so spoofed callbacks cannot complete orders. Refunds are issued directly from the WooCommerce order screen and call the Flutterwave refund API, with partial refunds supported.