MENA merchants running ERPNext hit a wall the moment they try to collect card payments the way their customers actually pay. ERPNext core ships a Payment Gateway framework with a handful of built-in integrations, but PayTabs — the dominant gateway across Saudi Arabia, the UAE, Egypt, Jordan, Oman, and beyond — is not one of them. Teams end up reconciling gateway settlements against ERPNext by hand, exporting CSVs from the PayTabs merchant dashboard, and guessing which Sales Invoice a payment belongs to. Multi-currency card acceptance, local methods like mada, STC Pay, and Apple Pay, refunds, and recurring billing all live outside the ERP, so finance never has a single source of truth.

ECOSIRE builds a dedicated PayTabs connector as a proper Frappe app — its own module, DocTypes, and hooks.py wiring — that plugs into ERPNext's native Payment Gateway and Payment Request flow rather than bolting on a parallel system. A PayTabs Settings single DocType holds your Profile ID, server key, region endpoint, and currency mapping (encrypted via Frappe's password fieldtype). When a Sales Invoice or Payment Request needs collection, the app calls the PayTabs Hosted Payment Page API and returns a redirect URL, or generates a shareable payment link your team can send over email or WhatsApp. Customers pay on PayTabs' PCI-compliant page; card data never touches your ERPNext server.

Confirmation is webhook-first, not redirect-dependent. A whitelisted endpoint (@frappe.whitelist(allow_guest=True)) receives the PayTabs Instant Payment Notification, validates the HMAC signature against your server key, checks idempotency so a retried callback never double-posts, and on success creates and submits a reconciled Payment Entry linked back to the originating invoice — all inside a single database transaction. hooks.py doc events keep statuses in sync, a scheduler event reconciles any transactions that missed their webhook by polling the PayTabs query API, and every request/response is written to a PayTabs Transaction Log DocType for audit and dispute handling. Refunds are issued from within ERPNext and post the matching credit entry; tokenized recurring payments reuse the saved PayTabs token for subscription-style rebilling without re-collecting card details.

Because this is build-to-order, you are not downloading a generic marketplace app and hoping it fits. ECOSIRE scopes your exact PayTabs region, currencies, local methods, invoice/subscription workflow, and role permissions on a short call, then builds, tests on a staging bench, and installs the connector on your Frappe/ERPNext v15 or v16 site. Typical delivery is one working week from confirmed scope. You receive the full source, documentation, a training session, a post-go-live support window, and the git repository so your team owns the code outright.