GCC merchants running ERPNext quickly hit a wall at checkout: buyers expect KNET in Kuwait, mada in Saudi Arabia, and Benefit in Bahrain, but ERPNext core ships payment integrations aimed at global card gateways, not the local aggregators and debit rails that dominate the region. Teams end up reconciling MyFatoorah settlements by hand, exporting CSVs, and re-keying references against Sales Invoices — which is slow, error-prone, and breaks the moment volume grows. ERPNext's built-in Payment Gateway framework simply does not speak MyFatoorah's InitiatePayment/ExecutePayment API or its webhook contract out of the box.

We build a proper Frappe app (its own module, DocTypes, and hooks.py) that integrates MyFatoorah as a first-class payment method inside ERPNext. A MyFatoorah Settings single DocType holds your API token, base URL (test vs live), and enabled payment-method IDs, with the secret stored via Frappe's get_password so it never sits in plaintext. When an invoice or web-shop order needs payment, whitelisted server methods call MyFatoorah's unified checkout to create a hosted payment session and return the redirect URL; the customer pays via KNET, mada, Benefit, or card, and MyFatoorah drives the result back to a whitelisted webhook endpoint on your site.

Technically, the confirmation path is idempotent and signature-verified. The webhook (a @frappe.whitelist(allow_guest=True) method) validates the MyFatoorah signature, looks up the originating transaction in a MyFatoorah Transaction DocType, and — only on a genuinely paid status — creates and submits a Payment Entry against the correct Sales Invoice, writing back the payment ID, method, and settled amount for clean reconciliation. Refunds issued from ERPNext call MyFatoorah's refund API and record the outcome, and multi-currency orders are mapped to the right MyFatoorah currency and account. A scheduler event (scheduler_events in hooks.py) reconciles any transactions whose webhook was missed by polling GetPaymentStatus, so a dropped callback never leaves an invoice silently unpaid. Roles and permissions are scoped through a dedicated role profile so only finance staff can view tokens or trigger refunds, and everything is exposed through the standard Frappe REST API for your other systems.

Because this is build-to-order, we start from your actual scope — which entities pay (Sales Invoice, POS, web-shop, or a custom flow), which GCC methods and currencies you need, and your MyFatoorah account tier. ECOSIRE writes the code, tests it against your MyFatoorah test credentials on a staging bench, runs UAT with you, and then installs it on your production ERPNext v15 or v16 site with a rollback plan. You receive the full source as an installable app and the Git repository, so you are never locked to us. Typical delivery is one working week from confirmed scope.