イメージプレビューOne MyFatoorah connector for all GCC methods — KNET, mada, Benefit, cards, Apple Pay.
Built-to-order for Odoo 17/18/19 by ECOSIRE.
MyFatoorah Payment Gateway for Odooとは？
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 $999.00 USD; request a quote for a scoped proposal.
主な機能
受注生産、すべておまかせ
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
- 1
ご注文
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
- 2
構築とインストール
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
- 3
本番稼働 + サポート
約1週間（営業日ベース）で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
技術仕様
- Odoo互換性
- Odoo 17, Odoo 18, Odoo 19
- エディション
- Enterprise＆Community
- ライセンス
- ライセンスの確認が必要です
- Python要件
- Python 3.10+
- データベース
- PostgreSQL 12+
この製品について
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 one working 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.
得られるもの
- 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
これは誰のためのものですか
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.
MyFatoorah Payment Gateway for Odoo の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Odoo 標準機能 |
|---|---|---|---|---|
| Aggregates KNET, mada, Benefit, Apple Pay & cards in ONE connector | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Built, installed & configured for your journals and storefront | 付属 | 部分的なサポート | 含まれていない | 含まれていない |
| Signature-verified server-to-server webhook reconciliation | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Refunds and partial refunds posted back to the Odoo invoice | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Multi-currency Gulf support (KWD, SAR, BHD, AED) mapped to journals | 付属 | 部分的なサポート | 部分的なサポート | 部分的なサポート |
| Invoice pay-link flow (MyFatoorah SendPayment) from Odoo | 付属 | 部分的なサポート | 含まれていない | 含まれていない |
| Tested across Odoo 17, 18 & 19, Community and Enterprise | 付属 | 部分的なサポート | 部分的なサポート | 部分的なサポート |
| Post-delivery support, bug-fix window and training included | 付属 | 含まれていない | 部分的なサポート | 含まれていない |
MyFatoorah Payment Gateway に関するよくある質問
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 one working week 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.
関連モジュール
MyFatoorah Payment Gateway
One MyFatoorah connector for all GCC methods — KNET, mada, Benefit, cards, Apple Pay. Built-to-order for Odoo 17/18/19 by ECOSIRE.
- 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