If you sell in Egypt or the wider MENA region, your customers expect to pay with local cards, Vodafone/Orange/Etisalat mobile wallets, and ValU-style installments — not just an international card form. Odoo ships a payment framework with providers like Stripe and a generic "wire transfer" option, but out of the box there is no Paymob payment.provider record, no Accept iframe integration, and no HMAC callback verification for the Egyptian gateway. Merchants end up either forcing customers onto a payment method they abandon, or bolting on a fragile manual reconciliation process where confirmed orders and captured cash drift apart. That gap is exactly where a native Odoo integration pays for itself.

ECOSIRE builds a dedicated Paymob integration as a proper Odoo addon. We add a new provider to Odoo's payment framework by extending payment.provider (a models.Model inheriting the core model) with the Paymob credential fields.Char — API key, integration IDs for card, wallet and ValU, and the HMAC secret — plus a payment.transaction subclass that drives Paymob's Accept flow. The customer checkout requests an auth token and an order/payment key, then renders either the Accept iframe (embedded card entry) or a redirect to Paymob's hosted page, depending on the method chosen. When Paymob calls back, our controller recomputes the HMAC over the ordered field set and compares it in constant time before ever setting a transaction to done — so a spoofed callback cannot mark an order paid. Successful transactions post through Odoo's standard accounting the same way a Stripe payment would, keeping your journals and account.payment records clean.

The build is engineered to feel like core Odoo, not a bolt-on. Access is governed by ir.model.access.csv and record rules so only accounting/settings users see credentials; the provider configuration lives in the standard Payment Providers settings view (XML/OWL) with EGP, SAR, and AED currency handling and Arabic/English labels. Refunds are wired to Paymob's refund API and reflected back onto the Odoo transaction and invoice, so a credit note and the gateway stay in sync. Every state change is logged for audit, webhook payloads are retained for troubleshooting, and the same transaction records are reachable over Odoo's XML-RPC/JSON-RPC API if you need to reconcile from an external finance system. We confirm Community vs Enterprise behavior up front — the payment framework exists in both, and we flag anything (like specific accounting automations) that differs on your edition.

Because this is build-to-order, you are not downloading a generic zip and hoping it fits. After a short scoping call we confirm your Paymob account setup, the exact methods you need live (cards, wallets, ValU, or a subset), your currencies, and your Odoo version and edition. We build against your requirements, test on a staging copy of your database with UAT sign-off, then install on production with a rollback plan. Typical delivery is one working week from confirmed scope, and you receive the full installable source, git repository handover, and a post-go-live support window so the integration keeps working as Paymob and Odoo evolve.