示意预览Egyptian cards, wallets, and Fawry pay-at-outlet cash on Odoo
— reference codes, webhook reconciliation, EGP, and refunds. Built to order.
什么是 Fawry Payment Gateway for Odoo (Egypt)？
Egyptian cards, wallets, and Fawry pay-at-outlet cash on Odoo — reference codes, webhook reconciliation, EGP, and refunds. Built to order. 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
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
Fawry is how Egypt actually pays. Between debit cards, mobile wallets (Vodafone Cash, Etisalat, Orange), and the ubiquitous "pay at any Fawry outlet with a reference code" flow, a large share of Egyptian customers will not — or cannot — complete a card-only checkout. If your Odoo eCommerce, sales, or invoicing sends buyers to a Stripe or PayPal button they don't recognize, you lose the sale at the last step.
This is a BUILD-TO-ORDER Odoo payment provider. ECOSIRE designs, builds, installs, and supports a native Fawry integration for your Odoo 17, 18, or 19 database — Community or Enterprise. It is not an existing apps.odoo.com download you install blindly; we engineer it against your Fawry merchant account, your EGP journals, and your checkout flow, then hand you a clean, upgrade-safe module with source code. Typical delivery is one working week from confirmed scope and access.
Under the hood it is a proper Odoo payment.provider extension. We add a Fawry provider record with your merchant code and secure hash keys (stored, never hardcoded), a payment.transaction subclass that talks to Fawry's ChargeRequest / PayAtFawry API, and the redirect/inline OWL flow so customers pick card, wallet, or "pay at outlet." When a buyer chooses the cash option, the module generates a Fawry reference code with a configurable expiry window and shows it — plus a QWeb-rendered voucher — right on the confirmation page and in the order email. Payment lands asynchronously when the customer walks into any Fawry point; our webhook controller validates Fawry's signature hash, reconciles the transaction, moves the Odoo order/invoice to paid, and posts to the correct EGP journal. Refunds are supported from the Odoo transaction view where your Fawry plan allows them.
You get security done the Odoo way (ir.model.access.csv + record rules so only the right users see credentials and transactions), sandbox-first delivery so you test with real reference codes before going live, and full source so you're never locked in. Works with Odoo eCommerce, the sales/invoicing "pay now" links, and any custom flow via the standard payment API — and it survives Odoo upgrades because it extends core models instead of forking them.
你得到什么
- Installable Odoo module (17.0 / 18.0 / 19.0 as required) with a complete `__manifest__.py`, models, views, security, controllers, and QWeb templates — delivered as source you own
- Configured Fawry `payment.provider` record wired to your merchant credentials, plus mapped EGP journal(s) and enabled payment methods (card, wallet, pay-at-outlet)
- End-to-end sandbox setup and a joint test pass: real reference-code generation, a simulated outlet payment, webhook reconciliation, and a refund
- Production go-live: credentials cutover, webhook URL registered with Fawry, and a live smoke-test transaction verified together
- Admin & finance documentation — how to read transaction states, handle a stuck/expired reference code, reconcile, and issue refunds
- A live handover/training session for your team plus a config runbook and support-contact sheet
- Post-launch support window (bug fixes and reconciliation help) at the tier agreed in your quote
- Odoo-upgrade guidance so the module carries forward to your next major version
这是给谁的
Egyptian eCommerce merchant on Odoo
Runs an Odoo Website/eCommerce store in Egypt and is losing checkout conversions because customers want Fawry cash and wallets, not a foreign card gateway. Needs Fawry to appear natively at checkout with a reference code and email voucher.
Finance / accounting manager
Owns EGP reconciliation in Odoo and is tired of manually matching Fawry settlements to invoices. Wants signed webhooks to auto-post payments to the right journal, clear transaction states, and refund handling inside Odoo.
Odoo partner or in-house developer
Needs a clean, upgrade-safe Fawry provider that extends core `payment.provider`/`payment.transaction` rather than a fragile fork — with source code, sandbox parity, and an API surface (XML-RPC/JSON-RPC) they can build on.
Subscription / services business billing in EGP
Sends Odoo invoices with 'pay now' links and needs Egyptian customers to settle them via Fawry outlets or wallets, with automatic status updates and dunning that respects reference-code expiry.
Fawry Payment Gateway for Odoo (Egypt) 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Fawry cards, wallets, and pay-at-outlet cash in one flow | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Reference-code generation with configurable expiry + emailed voucher | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Signed webhook reconciliation into the correct EGP journal | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Built and tested against your Fawry account and Odoo version/edition | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Refund support from inside the Odoo transaction view | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Upgrade-safe (extends core payment.provider, not a fork) | 包含 | 部分支持 | 部分支持 | 包含 |
| Full source code ownership + team training | 包含 | 包含 | 部分支持 | 包含 |
| Dedicated post-launch support & reconciliation help | 包含 | 不包括在内 | 部分支持 | 不包括在内 |
| Sandbox-first delivery with a joint go-live smoke test | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
关于Fawry Payment Gateway的常见问题
How long until it's live, and what's the delivery process?
This is a build-to-order module, not an instant download. Typical delivery is one working week from kickoff, depending on scope (number of payment methods, custom checkout, journals). We work sandbox-first: we build against Fawry's test environment, run a joint test pass with real reference codes and webhook reconciliation, then cut over to production and verify a live transaction with you. You receive the full module source at handover.
How do you handle support and Odoo upgrades after go-live?
Every build includes a post-launch support window (fixes and reconciliation help) sized to the tier in your quote. Because the module extends Odoo's core `payment.provider` and `payment.transaction` instead of forking them, it carries forward across Odoo upgrades; we provide upgrade guidance, and can re-validate the module against your next major Odoo version under a maintenance agreement.
Does this work on Odoo Community, or only Enterprise?
Both. The payment framework we extend exists in Odoo Community and Enterprise for 17, 18, and 19. We confirm your exact version and edition at kickoff and deliver a module built for it. Some higher-level accounting automations differ between editions, and we map the reconciliation flow to whichever you run.
Which payment methods does the Fawry integration cover?
Egyptian cards (via Fawry's hosted, 3-D Secure card flow), mobile wallets such as Vodafone Cash, Etisalat Cash, and Orange Money, and the pay-at-outlet cash flow where Odoo generates a Fawry reference code the customer pays at any Fawry point, machine, or app. The exact wallet set depends on what your Fawry merchant contract enables.
How does a cash 'pay-at-outlet' payment get reconciled in Odoo?
When a customer chooses pay-at-outlet, the module creates a Fawry reference code with a configurable expiry and shows it on the confirmation page and in the order email with a QWeb voucher. The order sits pending. When the customer pays at a Fawry outlet, Fawry sends a signed callback; our webhook controller validates the SHA-256 hash, marks the `payment.transaction` done, posts the payment to your EGP journal, and confirms the order — no manual matching.
What do you need from us to build it, and is Fawry's own account included?
You provide your Fawry merchant account and API credentials (merchant code and secure hash keys) — the Fawry contract itself is between you and Fawry, we don't resell it. From there we need your Odoo version/edition, access to a staging database, and your EGP journal setup. We handle the rest: module code, provider configuration, webhook registration, testing, and training.
Is it secure, and where are the credentials stored?
Credentials live on the Odoo provider record, protected by `ir.model.access.csv` and record rules so only authorized users can see them — never hardcoded in source. Card data is handled by Fawry's hosted flow, so raw card numbers never touch your Odoo server. Every webhook is signature-verified to block tampered or replayed callbacks, and each transaction logs its Fawry references and raw payload for audit.
相关模块
Fawry Payment Gateway
Egyptian cards, wallets, and Fawry pay-at-outlet cash on Odoo — reference codes, webhook reconciliation, EGP, and refunds. Built to order.
- Native Odoo `payment.provider` + `payment.transaction` extension — Fawry appears as a first-class payment method in eCommerce checkout, sales order 'pay now' links, and customer portal invoices
- Accept Egyptian debit/credit cards through Fawry's hosted card flow (3-D Secure handled by Fawry, so no PCI card data touches your Odoo server)
- Mobile wallet payments — Vodafone Cash, Etisalat Cash, Orange Money and other Fawry-supported wallets — selectable at checkout
- Pay-at-outlet cash flow: generates a Fawry reference code the customer takes to any Fawry point, machine, or app to pay in cash