MENAP merchants running ERPNext repeatedly hit the same wall: ERPNext ships with no native Paymob support, so online payment requests fall back to bank transfer, manual reconciliation, or a bolt-on gateway that only covers one country. If you sell into Egypt, Saudi Arabia, the UAE, and Pakistan you end up juggling separate acquirers, separate reconciliation spreadsheets, and no clean link back to the ERPNext Sales Invoice or Payment Entry that finance actually works from. The result is delayed collections, orphaned payments, and a checkout experience that leaks conversions.

ECOSIRE builds the Paymob Gateway as a proper Frappe app — a versioned app in your bench with its own module, not a pile of pasted server scripts. It registers a Paymob Settings single DocType for API keys, HMAC secret, integration IDs per country and per method, and enabled payment options, all stored with Frappe's encrypted-field handling so secrets never sit in plaintext. Payment intents are created against Paymob's Unified Intention API and reconciled back through a whitelisted webhook endpoint that verifies Paymob's HMAC signature before it touches any ledger. On a verified success the app creates or allocates a Payment Entry, marks the linked Sales Invoice or Sales Order paid, and writes a Paymob Transaction log row so every card auth, wallet charge, or BNPL settlement is auditable.

Technically it hangs off the parts of ERPNext you already trust. hooks.py doc events keep ERPNext documents and Paymob state in sync; scheduler events (hourly, daily) poll for pending or stuck intents and reconcile timeouts so nothing is left hanging. A whitelisted method exposed through the Frappe REST API drives checkout initiation and the return/callback flow, and a small client script surfaces a "Pay with Paymob" action on the customer-facing side. Access is governed by a dedicated role and role profile so only authorized users can view secrets, refund, or replay a transaction. The connector abstracts the method matrix — cards and Meeza, mobile wallets, Valu and Souhoola BNPL, plus Apple Pay and Google Pay — behind one unified checkout, and supports tokenized recurring charges so saved-card and subscription billing map onto ERPNext without re-entering card data. It targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, we start from your real scope: which countries and currencies, which Paymob methods and integration IDs, whether you need BNPL and recurring tokens, and how you want reconciliation to post. We build against that, hand you the installable source for your version, deploy it on your bench, and support it after go-live. Typical delivery is one working week from confirmed scope. There is no instant download — you get a connector built for your ERPNext, not a generic plugin you have to bend to fit.