Egyptian cards, wallets, and Fawry pay-at-outlet cash on Odoo — reference codes, webhook reconciliation, EGP, and refunds. Built to order. One-time license from $249.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Egyptian cards, wallets, and Fawry pay-at-outlet cash on Odoo — reference codes, webhook reconciliation, EGP, and refunds. Built to order.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
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.
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
Configurable reference-code expiry window (e.g. 24/48/72 hours) with the deadline shown to the customer and stored on the `payment.transaction`
QWeb-rendered Fawry payment voucher/receipt attached to the order and emailed automatically, showing the reference code, amount in EGP, and expiry
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 2–4 weeks depending on scope.
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.
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.
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.
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.
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.
Buy the license on ecosire.com and download the Fawry Payment Gateway for Odoo (Egypt) module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Fawry Payment Gateway for Odoo (Egypt), and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| 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 |
This is a build-to-order module, not an instant download. Typical delivery is 2–4 weeks 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.
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.
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.
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.
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.
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.
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.
Egyptian cards, wallets, and Fawry pay-at-outlet cash on Odoo — reference codes, webhook reconciliation, EGP, and refunds. Built to order.