MyFatoorah Payment Gateway for Odoo

Key Features

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

Refunds and partial refunds initiated from Odoo, posted back to the originating `account.move` and credit note

Saved payment token support where MyFatoorah allows it, for returning-customer one-click checkout

Per-environment sandbox and live credential switching stored on the provider record — never hard-coded

Automatic sale order / invoice confirmation on `done` status, with idempotent handling so duplicate webhooks never double-post

`@api.depends` computed status fields and a searchable transaction log with the MyFatoorah reference for audit and support

Security via `ir.model.access.csv` and record rules so only Payment/Accounting roles see credentials and transaction data

QWeb-ready payment references on order confirmations and invoice PDFs for clean customer-facing documents

Compatible with Odoo 17, 18 and 19 on both Community and Enterprise editions

Transactions accessible over Odoo XML-RPC / JSON-RPC for headless storefronts or mobile apps

Built to order, done for you

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

You order

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

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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.

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.

What you get

Complete, installable Odoo module (`__manifest__.py`, models, views/OWL, QWeb, `ir.model.access.csv` and record rules) targeting your Odoo 17, 18 or 19 instance

Live and sandbox configuration of your MyFatoorah credentials on the payment provider record, mapped to your payment journal and chart of accounts

End-to-end sandbox testing of checkout, invoice pay-link, webhook confirmation, refund and partial-refund before go-live

Go-live migration to production keys plus a post-launch smoke test on your real storefront

Admin and finance documentation: configuration guide, method/currency matrix, reconciliation and refund runbook

A live training session for your team (checkout, invoice links, refunds, reading the transaction log)

A defined post-delivery support and bug-fix window with a named point of contact

Source code ownership handover so your team (or ours) can extend it later

Who this is for

GCC eCommerce merchant on Odoo Website

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.

Finance manager consolidating settlement

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.

Multi-country Gulf operator

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.

How MyFatoorah Payment Gateway for Odoo Compares

Criterion	ECOSIRE	Custom Build	Competitor
Aggregates KNET, mada, Benefit, Apple Pay & cards in ONE connector	Included	Partial support	Partial support
Built, installed & configured for your journals and storefront	Included	Partial support	Not included
Signature-verified server-to-server webhook reconciliation	Included	Partial support	Partial support
Refunds and partial refunds posted back to the Odoo invoice	Included	Partial support	Partial support
Multi-currency Gulf support (KWD, SAR, BHD, AED) mapped to journals	Included	Partial support	Partial support
Invoice pay-link flow (MyFatoorah SendPayment) from Odoo	Included	Partial support	Not included
Tested across Odoo 17, 18 & 19, Community and Enterprise	Included	Partial support	Partial support
Post-delivery support, bug-fix window and training included	Included	Not included	Partial support

Frequently Asked Questions about MyFatoorah Payment Gateway for Odoo

Is this an instant download from the Odoo App Store?

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.

How long does delivery take?

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.

What support and updates do I get after delivery?

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.

Which payment methods and currencies are actually supported?

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.

Will it work with my Odoo version and edition?

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.

How are payments confirmed and reconciled reliably?

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.