Skip to main content
Flutterwave Payment Gateway for Odoo — Pan-African cards, mobile money, USSD & bank transfer via Flutterwave, built into Odoo — 1/1Illustrative preview

Pan-African cards, mobile money, USSD & bank transfer via Flutterwave,

built into Odoo checkout with webhook reconciliation and refunds.

What is Flutterwave Payment Gateway for Odoo?

Pan-African cards, mobile money, USSD & bank transfer via Flutterwave, built into Odoo checkout with webhook reconciliation and refunds. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.

Key Features

Flutterwave registered as a native Odoo payment provider (extends payment.provider/payment.transaction) — selectable in Website eCommerce, the customer portal, and Subscriptions
Card payments (Visa, Mastercard, Verve) with 3-D Secure handled through Flutterwave's hosted/inline checkout
Mobile money across Africa — M-Pesa, MTN MoMo, Airtel Money, and others — surfaced as checkout options based on the customer's country
USSD and instant bank-transfer payment methods for customers without cards
Multi-country / multi-currency support (NGN, KES, GHS, UGX, TZS, ZAR, RWF, USD and more) mapped to your Odoo companies and pricelists
Signed webhook controller that verifies the Flutterwave verif-hash and transitions each payment.transaction to done / cancelled / error automatically
Idempotent callback handling — a retried or duplicated webhook never double-confirms an order or grants a license twice
Server-side transaction re-verification (verify-by-reference call) before marking paid, so a spoofed redirect can't fake a successful payment
Refunds issued directly from the Odoo transaction form via the Flutterwave API, with the refund state reflected on the sales order and invoice
Tokenized recurring payments wired to Odoo Subscriptions — cards are tokenized on first charge and auto-billed on renewal
Test vs live mode toggle on the provider record using Flutterwave sandbox keys, mirroring Odoo's standard provider state (disabled/test/enabled)
API secret keys stored securely on the provider record and never exposed to the browser or QWeb templates
ir.model.access.csv + record rules controlling who can view transactions and who can trigger refunds
Automatic reconciliation: successful payments post the payment and reconcile against the customer invoice using Odoo's accounting flow
Optional split-payment / sub-account support for marketplaces and multi-vendor setups on Flutterwave
Clear payment status and reference shown in the customer portal and on order confirmation, with failed-payment retry

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

  1. 1

    You order

    Start with a one-time build price. We scope it with you at kickoff.

  2. 2

    We build & install

    ECOSIRE builds, configures and installs it on your Odoo.

  3. 3

    Go live + support

    You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.

Technical Specifications

Odoo Compatibility
Odoo 17, Odoo 18, Odoo 19
Editions
Enterprise & Community
License
Licence confirmation required
Python Requirement
Python 3.10+
Database
PostgreSQL 12+

About this Product

Sell across Africa without forcing customers into a payment method they don't have. This build-to-order module wires Flutterwave directly into Odoo's native payment framework so your eCommerce checkout, customer portal invoice payments, and Subscriptions can accept Visa/Mastercard, mobile money (M-Pesa, MTN MoMo, Airtel), USSD, and bank transfer across dozens of African markets and currencies — all reconciled automatically inside Odoo.

ECOSIRE builds this as a proper Odoo payment provider: it extends the payment.provider and payment.transaction models, registers Flutterwave as a selectable acquirer in Website eCommerce and the portal, renders the redirect/inline checkout via QWeb + OWL, and closes the loop with a secured webhook controller that verifies the Flutterwave signature and moves each payment.transaction to done, cancelled, or error. Recurring charges are supported through Flutterwave tokenization tied to Odoo Subscriptions, and refunds are issued straight from the transaction form via the Flutterwave API — no separate dashboard hopping.

This is not an apps.odoo.com instant download. It is a net-new module that we scope to your country coverage, currencies, and checkout flow, then build, install, test in your Odoo, and support. Delivery is typically one working week depending on how many markets/currencies and which Flutterwave features (subscriptions, split payments) you enable. Works on Odoo 17, 18, and 19 (Community or Enterprise); the payment framework it builds on ships in both editions, so you are never forced into an Enterprise upsell to take money.

Security follows Odoo conventions throughout: API secret keys are stored on the provider record (never rendered client-side), ir.model.access.csv and record rules gate who can view transactions and issue refunds, webhook payloads are hash-verified before any state change, and every callback is idempotent so a retried webhook never double-confirms an order. You get clean, upgrade-safe code — no core patching — plus documentation, an admin walkthrough, and a support window to catch any real-world edge cases in the first weeks of going live.

What you get

  • The complete, upgrade-safe Odoo module (models, controllers, views, security, data) — no core patching — delivered as source in a Git repo you own
  • Fully configured Flutterwave provider record in your Odoo, wired to your live and sandbox API keys and webhook URL
  • Country, currency, and payment-method mapping tailored to the African markets you actually sell in
  • Webhook endpoint set up and verified end-to-end against your Flutterwave dashboard (test transaction confirmed reconciling in Odoo)
  • Refund and recurring-billing (tokenized Subscriptions) flows configured and demonstrated on your instance
  • Admin + finance documentation: how to configure, go live, reconcile, refund, and read transaction states
  • A live handover / training session for your team covering checkout, portal payments, and refunds
  • Post-launch support window for bug fixes and edge cases, plus compatibility guidance for your Odoo 17/18/19 version

Who this is for

African merchant selling cross-border

You sell into multiple African countries and lose baskets because a single card gateway ignores how most of your customers actually pay. You need mobile money, USSD, and bank transfer alongside cards, in local currencies, all landing in one Odoo backend.

Odoo eCommerce store owner in Nigeria/Kenya/Ghana

Your storefront runs on Odoo Website and you want Flutterwave — a gateway your customers trust locally — as a first-class checkout option that auto-confirms orders and reconciles invoices without manual matching.

Finance / operations manager

You are tired of reconciling Flutterwave's dashboard against Odoo by hand. You want every payment, refund, and recurring charge to post and reconcile automatically, with clear transaction states and role-based access to issue refunds.

Subscription or SaaS business in Africa

You bill recurring plans and need cards tokenized once and charged automatically on renewal through Odoo Subscriptions, with failed-payment handling — not one-off manual invoices every month.

How Flutterwave Payment Gateway for Odoo Compares

CriterionECOSIRECustom BuildCompetitorOdoo Native
Pan-African methods (cards, mobile money, USSD, bank transfer)IncludedPartial supportPartial supportNot included
Native Odoo payment provider (auto order confirm + invoice reconciliation)IncludedPartial supportIncludedPartial support
Signed, idempotent webhook with server-side re-verificationIncludedPartial supportPartial supportNot included
Refunds issued from inside OdooIncludedPartial supportPartial supportNot included
Tokenized recurring billing via Odoo SubscriptionsIncludedPartial supportNot includedNot included
Scoped to your countries, currencies & checkout flowIncludedIncludedNot includedNot included
Works on Odoo 17/18/19, Community & EnterpriseIncludedPartial supportPartial supportPartial support
Build, install, test & ongoing support includedIncludedNot includedNot includedNot included

Frequently Asked Questions about Flutterwave Payment Gateway

Is this an instant download from the Odoo App Store?

No. This is a build-to-order module. ECOSIRE scopes it to your countries, currencies, and checkout flow, then builds, installs, and tests it in your Odoo. You receive the source code and a configured, working provider — not a self-service download.

How long does delivery take?

Typically one working week. A single-country, card-plus-mobile-money setup lands toward the shorter end; more markets, currencies, split payments, or recurring Subscriptions billing push toward the longer end. We confirm a firm timeline after a short scoping call and keep you updated through build and testing.

How do support and updates work after launch?

Every build includes a post-launch support window for bug fixes and edge cases discovered in real use. Because the module is upgrade-safe (no core patching), it moves cleanly between your point releases; when you upgrade Odoo across major versions (17→18→19), we offer a compatibility pass. Ongoing support and enhancement retainers are available.

Which Odoo versions and editions are supported?

Odoo 17, 18, and 19, on both Community and Enterprise. The module builds on Odoo's native payment framework, which ships in Community as well as Enterprise — so you are not forced into an Enterprise license just to accept payments.

Do I need my own Flutterwave account?

Yes. You keep your own Flutterwave merchant account and API keys — funds settle to you directly, and we never hold your credentials or your money. During setup we wire your live and sandbox keys onto the Odoo provider record and configure the webhook against your dashboard.

How are payments reconciled and kept secure?

A signed webhook controller verifies Flutterwave's verif-hash and re-verifies each transaction server-side before marking it paid, then posts and reconciles the payment against the Odoo invoice. Callbacks are idempotent, secret keys live only on the provider record (never client-side), and ir.model.access.csv plus record rules control who can view transactions or issue refunds.

Can it handle refunds and recurring billing?

Yes. Refunds are issued from the Odoo transaction form via the Flutterwave API, with the refund state reflected on the order and invoice. Recurring billing uses Flutterwave card tokenization tied to Odoo Subscriptions — the card is tokenized on first charge and auto-billed on renewal, with failed-payment handling.

Request a quote

Flutterwave Payment Gateway

Pan-African cards, mobile money, USSD & bank transfer via Flutterwave, built into Odoo checkout with webhook reconciliation and refunds.

  • Flutterwave registered as a native Odoo payment provider (extends payment.provider/payment.transaction) — selectable in Website eCommerce, the customer portal, and Subscriptions
  • Card payments (Visa, Mastercard, Verve) with 3-D Secure handled through Flutterwave's hosted/inline checkout
  • Mobile money across Africa — M-Pesa, MTN MoMo, Airtel Money, and others — surfaced as checkout options based on the customer's country
  • USSD and instant bank-transfer payment methods for customers without cards

Request a Quotation

Tell us about your Flutterwave Payment Gateway requirements and we'll send pricing, licensing options and a tailored proposal — usually within one business day.

No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.