Egyptian merchants running ERPNext hit a wall the moment they try to collect money the way their customers actually pay. A huge share of the market still pays in cash, and the rest expect Meeza cards, mobile wallets, or valU installments — none of which ERPNext supports natively. Out of the box ERPNext gives you manual Payment Entries and a couple of generic gateways with no Egyptian coverage, so finance teams end up reconciling Fawry settlements by hand against bank statements, chasing reference codes in spreadsheets, and marking invoices paid days after the customer actually paid at a kiosk. That gap is where cash leaks, disputes start, and month-end close drags.

ECOSIRE builds a proper Frappe app — erpnext_fawry — that wires Fawry directly into your ERPNext payment flow rather than bolting on a fragile script. The app ships new DocTypes for Fawry Settings (encrypted merchant code, secure key, and environment toggle for Fawry's staging vs. production endpoints) and Fawry Payment Request, which stores the reference number, charge amount, expiry, and lifecycle status for every transaction. When a customer chooses Fawry at checkout — whether through the hosted Fawry payment page or the API-driven flow — the app calls Fawry's charge API from a whitelisted server method, generates the reference code the customer takes to any of the 200k+ collection outlets, and links it back to the originating Sales Order or Sales Invoice via a custom field.

Reconciliation is the part we take seriously. Fawry's webhook posts to a whitelisted, signature-verified endpoint that validates the HMAC signature before it trusts a single field, then a hooks.py doc-event handler creates the matching Payment Entry, allocates it against the invoice, and flips the Fawry Payment Request to Paid — all inside one database transaction so a half-processed callback can never leave your books inconsistent. A scheduler event runs on the Frappe scheduler_events hook to poll Fawry's status API for any reference that expired or never fired a webhook, closing the loop on stale kiosk payments automatically. Client Scripts surface the reference code and a live status badge right on the ERPNext form, and role-based permissions plus a dedicated Fawry Manager role profile keep the merchant credentials and refund actions locked to the right people.

Because this is build-to-order, nothing is a one-size download. We start with a scoping call to confirm exactly which rails you need — Meeza and card acceptance, valU installment plans, cash reference codes, or all of them — plus your ERPNext version (we support Frappe/ERPNext v15 and v16), your checkout surface, and any custom invoicing rules. We then build against your requirements, validate on a staging bench, and hand over the working app.

Typical delivery is one working week from confirmed scope. You get the full source code for your version, installation and configuration on your bench, technical documentation, a user guide and training session, a post-go-live support window, and the git repository so your team owns what we build. No instant download, no fabricated benchmarks — just a gateway that fits how you actually run ERPNext.