One MyFatoorah connector for all GCC methods — KNET, mada, Benefit, cards, Apple Pay. Built-to-order for Odoo 17/18/19 by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.

One MyFatoorah connector for all GCC methods — KNET, mada, Benefit, cards, Apple Pay. Built-to-order for Odoo 17/18/19 by ECOSIRE.
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Stop stitching together a separate Odoo provider for every Gulf payment rail. This is a build-to-order MyFatoorah payment provider for Odoo 17, 18 and 19 that ECOSIRE designs, develops, installs and supports for you — it is not an instant apps.odoo.com download. Because MyFatoorah is itself an aggregator, a single integration surfaces the full regional method list your customers expect: KNET (Kuwait), mada and cards in Saudi Arabia, Benefit (Bahrain), Apple Pay, Visa/Mastercard/AMEX, and other MyFatoorah-supported wallets — all through one connector, one settlement relationship, and one reconciliation flow inside Odoo.
Single MyFatoorah connector aggregating the full GCC method list — KNET, mada, Benefit, Apple Pay, Visa/Mastercard/AMEX and MyFatoorah wallets — with no per-method provider to maintain
Registered as a native Odoo payment provider (`payment.provider` / `payment.transaction`) so it appears on the standard website checkout and the invoice portal 'Pay Now' page
Embedded checkout using MyFatoorah InitiatePayment/ExecutePayment for card and wallet flows plus a hosted-page fallback
SendPayment invoice-link flow: email or SMS a MyFatoorah pay link straight from an Odoo customer invoice
Server-to-server webhook reconciliation with signature verification — the callback, not the browser redirect, confirms the transaction and posts payment
Full multi-currency support for Gulf trade (KWD, SAR, BHD, AED, USD and more) reconciled to the correct payment journal
Technically, the module ships as a proper Odoo payment provider. It extends the payment.provider and payment.transaction models (models.Model, typed fields, @api.depends computes for status), registers on both the website eCommerce checkout and the invoice "Pay Now" portal, and drives MyFatoorah's InitiatePayment / ExecutePayment / SendPayment (invoice-link) endpoints over JSON. Payment status is confirmed authoritatively server-to-server via a hardened webhook (the module verifies MyFatoorah's signature and treats the callback — not the browser redirect — as the source of truth), so a customer who closes the tab still gets a correctly reconciled order. Sandbox and live credentials are switchable per environment; keys live in the provider record, never hard-coded.
You get the real Odoo payment lifecycle: draft → pending → authorized → done, with automatic confirmation of the linked sale order or invoice, saved-token support where MyFatoorah permits it, and full refund and partial-refund handling that posts back to the originating account.move and journal. Multi-currency is first-class for Gulf trade (KWD, SAR, BHD, AED, USD and more), with currency passed to MyFatoorah per transaction and reconciled against the correct payment journal. Access is locked down with ir.model.access.csv and record rules so only Accounting/Payment roles touch provider credentials and transaction logs.
Every engagement is scoped to YOUR chart of accounts, journals, tax setup, storefront and edition (Community or Enterprise). Over a typical 2–4 week build we implement, test end-to-end in the MyFatoorah sandbox, migrate to live, and hand over documentation and a training session — then stand behind it with a support and bug-fix window. If you also run headless/mobile, the same transactions are reachable through Odoo's XML-RPC / JSON-RPC API.
Sells across Kuwait, KSA and Bahrain and wants shoppers to pay with KNET, mada or Benefit at the Odoo checkout without juggling multiple providers or losing carts to an unfamiliar payment page.
Wants one MyFatoorah settlement and one reconciliation flow inside Odoo Accounting — with refunds and partial refunds posted correctly to the right journal — instead of reconciling KNET, cards and wallets separately.
Runs sales in several GCC currencies (KWD, SAR, BHD, AED) and needs each transaction charged and reconciled in the correct currency and payment journal, with clean audit references for every order.
Achetez la licence sur ecosire.com et téléchargez le module ZIP MyFatoorah Payment Gateway for Odoo depuis le tableau de bord de votre compte.
Extrayez le ZIP dans votre dossier de modules complémentaires personnalisés Odoo sur le serveur (ou téléchargez-le via Applications > Installer à partir du fichier sur Odoo.sh / runbot).
Activez le mode développeur, ouvrez les applications, cliquez sur Mettre à jour la liste des applications, recherchez MyFatoorah Payment Gateway for Odoo et appuyez sur Installer.
Ouvrez le nouveau menu, collez votre clé de licence ECOSIRE, connectez toutes les informations d'identification externes (Shopify, Amazon, Stripe, etc.) et enregistrez.
Exécutez le test de connexion intégré, synchronisez vos 10 premiers enregistrements et planifiez le cron récurrent. Contactez le support si quelque chose échoue.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Aggregates KNET, mada, Benefit, Apple Pay & cards in ONE connector | Inclus | Prise en charge partielle | Prise en charge partielle | |
| Built, installed & configured for your journals and storefront | Inclus | Prise en charge partielle | Non inclus | |
| Signature-verified server-to-server webhook reconciliation | Inclus | Prise en charge partielle | Prise en charge partielle | |
| Refunds and partial refunds posted back to the Odoo invoice | Inclus | Prise en charge partielle | Prise en charge partielle | |
| Multi-currency Gulf support (KWD, SAR, BHD, AED) mapped to journals | Inclus | Prise en charge partielle | Prise en charge partielle | |
| Invoice pay-link flow (MyFatoorah SendPayment) from Odoo | Inclus | Prise en charge partielle | Non inclus | |
| Tested across Odoo 17, 18 & 19, Community and Enterprise | Inclus | Prise en charge partielle | Prise en charge partielle | |
| Post-delivery support, bug-fix window and training included | Inclus | Non inclus | Prise en charge partielle |
No. This is a build-to-order module. ECOSIRE designs, develops, installs and configures it specifically for your Odoo instance, MyFatoorah account, journals and storefront. You are buying an engineered, installed and supported integration — not a self-serve zip file.
Typical lead time is 2 to 4 weeks from kickoff. That covers scoping against your Odoo edition and chart of accounts, building the payment provider, full sandbox testing of checkout, webhooks and refunds, then the go-live migration to your live MyFatoorah keys. Timing depends on the complexity of your setup and how quickly credentials and test access are provided.
Every build includes a defined post-delivery support and bug-fix window with a named contact. We fix defects, help with configuration questions, and keep the connector working across your Odoo minor updates. When you upgrade major Odoo versions (17 to 18 to 19) or need new MyFatoorah methods, we scope that as a follow-on. Ongoing support/maintenance plans are available.
Because MyFatoorah is an aggregator, one connector exposes the methods your MyFatoorah account is enabled for — commonly KNET, mada, Benefit, Apple Pay, and Visa/Mastercard/AMEX cards, plus supported wallets. Multi-currency covers Gulf trade including KWD, SAR, BHD, AED and USD. The exact method and currency matrix is confirmed against your MyFatoorah account during scoping.
Yes. We build and test against Odoo 17, 18 and 19 on both Community and Enterprise. The module registers as a standard `payment.provider`, so it works with the website eCommerce checkout and the invoice/portal payment flow the same way core providers do. We target the exact version you run.
Confirmation is driven by MyFatoorah's server-to-server webhook, not the browser redirect. The module verifies the callback signature, updates the `payment.transaction`, confirms the linked order or invoice, and posts the payment to your journal — idempotently, so a retried or duplicate webhook never double-posts. Refunds and partial refunds are initiated from Odoo and reconciled back to the originating entry.

A build-to-order 2Checkout (Verifone) payment integration for ERPNext, giving global digital-goods sellers card acceptance, 45+ local payment methods, multi-currency checkout, and reconciled invoices. ECOSIRE scopes, builds, installs, and supports it on your ERPNext v15/v16 instance.

A build-to-order 2Checkout / Verifone payment gateway for Magento 2 and Adobe Commerce: localized checkout in 12 languages, iDEAL, Giropay and regional methods, multi-currency global selling, subscription billing and tax/invoicing automation — engineered, installed and supported by ECOSIRE.

A build-to-order ERPNext application for anonymous 360-degree reviews — configurable peer, manager, report and self rater groups, weighted competency scoring, and aggregated gap-analysis and heatmap reports. ECOSIRE scopes, builds, installs and supports it on your Frappe/ERPNext v15/v16 instance.
One MyFatoorah connector for all GCC methods — KNET, mada, Benefit, cards, Apple Pay. Built-to-order for Odoo 17/18/19 by ECOSIRE.