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 $249.00 USD; request a quote for a scoped proposal.
示意预览Pan-African cards, mobile money, USSD & bank transfer via Flutterwave,
built into Odoo checkout with webhook reconciliation and refunds.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Odoo 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
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 2–4 weeks 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.
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.
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.
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.
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.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Pan-African methods (cards, mobile money, USSD, bank transfer) | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Native Odoo payment provider (auto order confirm + invoice reconciliation) | 包含 | 部分支持 | 包含 | 部分支持 |
| Signed, idempotent webhook with server-side re-verification | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Refunds issued from inside Odoo | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Tokenized recurring billing via Odoo Subscriptions | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Scoped to your countries, currencies & checkout flow | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Works on Odoo 17/18/19, Community & Enterprise | 包含 | 部分支持 | 部分支持 | 部分支持 |
| Build, install, test & ongoing support included | 包含 | 不包括在内 | 不包括在内 | 不包括在内 |
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.
Typically 2–4 weeks. 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.
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.
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.
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.
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.
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.
Pan-African cards, mobile money, USSD & bank transfer via Flutterwave, built into Odoo checkout with webhook reconciliation and refunds.