Quick facts
- Price
- $299.00 USD
- ERPNext versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
Paymob Gateway for ERPNext
A single Paymob connector for ERPNext that accepts cards, Meeza, mobile wallets, and Valu/Souhoola BNPL across Egypt, KSA, UAE, and Pakistan. ECOSIRE builds, installs, and supports it after we confirm your scope — this is a build-to-order engagement, not an off-the-shelf download.
$299.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
`Paymob Settings` single DocType holding API key, HMAC secret, and per-country/per-method integration IDs in Frappe encrypted fields
Unified Intention API integration — one checkout entry point across Egypt, KSA, UAE, and Pakistan
Cards and Meeza acceptance with 3-D Secure handling passed through to ERPNext transaction state
Mobile wallet payments (Egyptian wallets and regional equivalents) mapped to a single method selector
Valu and Souhoola BNPL flows, including installment plan selection surfaced at checkout
Apple Pay and Google Pay tokenized checkout supported through the same intention flow
HMAC-signature-verified webhook via a whitelisted Frappe method — no ledger write happens on an unverified callback
Automatic `Payment Entry` creation and allocation against the linked `Sales Invoice` / `Sales Order` on verified success
`Paymob Transaction` DocType logging every auth, capture, wallet charge, BNPL settlement, and refund for audit
Tokenized recurring charges for saved-card and subscription billing without re-storing PAN data
`hooks.py` doc events keeping ERPNext documents and Paymob intents in sync
Scheduler events (`hourly`/`daily`) that reconcile pending, timed-out, or stuck intents automatically
Dedicated role and role profile gating secret visibility, refunds, and transaction replay
Refund and partial-refund actions written back to ERPNext with matching journal impact, plus multi-currency handling per country
About this Product
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.
Why Choose Paymob Gateway for ERPNext
`Paymob Settings` single DocType holding API key, HMAC secret, and per-country/per-method integration IDs in Frappe encrypted fields
Unified Intention API integration — one checkout entry point across Egypt, KSA, UAE, and Pakistan
Cards and Meeza acceptance with 3-D Secure handling passed through to ERPNext transaction state
Mobile wallet payments (Egyptian wallets and regional equivalents) mapped to a single method selector
Valu and Souhoola BNPL flows, including installment plan selection surfaced at checkout
Apple Pay and Google Pay tokenized checkout supported through the same intention flow
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 2–4 weeks 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.
What you get
- Installable Frappe app source code built for your ERPNext version (v15 or v16)
- Installation and configuration on your bench — `Paymob Settings`, integration IDs, webhook endpoint, and role profile wired up
- Technical documentation: DocType schema, hooks/scheduler map, whitelisted methods, and webhook contract
- User guide plus a live training session for your finance and operations team
- UAT on a staging site with a documented rollback plan before production cutover
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with tagged release and commit history
- Reconciliation runbook covering pending/timed-out intents and refund procedure
Who this is for
MENAP multi-country merchant
Sells into two or more of Egypt, KSA, UAE, and Pakistan and is tired of running a separate acquirer and separate reconciliation per market. Wants one Paymob connector wired into ERPNext with country-aware integration IDs and currencies.
Finance controller on ERPNext
Owns `Sales Invoice` and `Payment Entry` accuracy. Needs every card, wallet, and BNPL settlement to post automatically against the right invoice with an auditable `Paymob Transaction` trail — no manual matching.
E-commerce or subscription operator
Runs online checkout and recurring billing and needs Apple Pay, Google Pay, BNPL, and tokenized recurring charges available at one checkout, all feeding back into ERPNext order and invoice state.
ERPNext implementation partner or in-house lead
Manages the client's bench and wants a clean, versioned Frappe app with proper hooks, roles, and REST methods they can maintain — not scattered server scripts pasted into production.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Paymob Gateway for ERPNext app ZIP from your account dashboard.
Add the app to your bench
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Install on your site
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install Paymob Gateway for ERPNext and apply its schema.
Activate your license
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
How Paymob Gateway for ERPNext Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| MENAP multi-country coverage | One connector for Egypt, KSA, UAE, Pakistan with per-country integration IDs | Whatever you scope and build yourself, country by country | Usually single-country or Egypt-only | |
| BNPL (Valu / Souhoola) | Built in, with installment selection at checkout | Possible but you build the whole BNPL flow | Rarely included | |
| ERPNext reconciliation | Auto `Payment Entry` + invoice paid + `Paymob Transaction` log | Depends entirely on your build quality | Often just marks paid, weak audit trail | |
| Webhook security | HMAC-verified whitelisted method before any ledger write | Only as strong as your implementation | Verification varies, sometimes missing | |
| Recurring / tokenized charges | Supported for saved-card and subscription billing | Significant extra effort to build safely | Seldom offered | |
| Version support & handover | Built for your v15/v16 bench, full git repo handed over | You own it, but you also built it from zero | Fixed release, upgrade timing not yours to control | |
| Delivery model | Build-to-order, 2–4 weeks from confirmed scope, then supported | Weeks to months of internal engineering time | Instant download but generic fit | |
| Ongoing support | Post-go-live support window + upgrade engagements | Falls on your own team | Vendor support quality varies |
Frequently Asked Questions about Paymob Gateway for ERPNext
+Is this an existing app I can download and install today?
No. This is a build-to-order engagement. ECOSIRE builds the Paymob connector against your confirmed scope — your countries, currencies, methods, and reconciliation rules — then installs it on your bench and supports it. You receive installable source for your ERPNext version, not a generic marketplace download.
+How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on how many countries and Paymob methods you need, whether BNPL and recurring tokenization are in scope, and how your reconciliation should post. We agree the scope on the initial call before any build starts.
+Which ERPNext versions are supported?
We target Frappe/ERPNext v15 and v16. We build against the specific version running on your bench and hand over source matched to it. If you plan to upgrade soon, tell us on the scoping call so we build with that migration in mind.
+Which countries and payment methods are covered?
The connector unifies checkout across Egypt, KSA, UAE, and Pakistan, covering cards and Meeza, mobile wallets, Valu and Souhoola BNPL, and Apple Pay and Google Pay. Which of these you actually enable — and per-country integration IDs — is configured in `Paymob Settings` based on your Paymob account.
+How are payments reconciled back into ERPNext?
A whitelisted webhook verifies Paymob's HMAC signature, then the app creates or allocates a `Payment Entry`, marks the linked `Sales Invoice` or `Sales Order` paid, and logs a `Paymob Transaction` row. Scheduler events also reconcile pending or timed-out intents so nothing is left in limbo.
+How do updates and ongoing support work?
Every build includes a post-go-live support window for defect fixes and configuration changes. Because you receive the full git repository and tagged source, your team can maintain it directly. We also offer ongoing support and version-upgrade engagements — for example when you move from ERPNext v15 to v16 or when Paymob changes its API.
+Do you handle recurring and subscription billing?
Yes. The connector supports tokenized recurring charges so saved-card and subscription billing work without re-storing raw card data. We map that onto your ERPNext billing flow during the build based on how you invoice recurring customers.
Related Modules
Request a quote
Paymob Gateway for ERPNext
A single Paymob connector for ERPNext that accepts cards, Meeza, mobile wallets, and Valu/Souhoola BNPL across Egypt, KSA, UAE, and Pakistan. ECOSIRE builds, installs, and supports it after we confirm your scope — this is a build-to-order engagement, not an off-the-shelf download.
- `Paymob Settings` single DocType holding API key, HMAC secret, and per-country/per-method integration IDs in Frappe encrypted fields
- Unified Intention API integration — one checkout entry point across Egypt, KSA, UAE, and Pakistan
- Cards and Meeza acceptance with 3-D Secure handling passed through to ERPNext transaction state
- Mobile wallet payments (Egyptian wallets and regional equivalents) mapped to a single method selector