Fawry Payment Gateway for Odoo (Egypt)

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.