Saudi and MENA e-commerce sellers running ERPNext keep hitting the same wall at the checkout: ERPNext core ships integrations for Stripe, PayPal, Razorpay and a handful of others, but there is no native Moyasar connector — and none of the core gateways clear mada, Apple Pay, STC Pay or SADAD, which is exactly what local buyers expect to see. Teams end up reconciling payments by hand, exporting spreadsheets from the Moyasar dashboard, and manually marking Sales Invoices as paid, which breaks straight-through order-to-cash and invites keying errors on every transaction.

ECOSIRE builds a proper Frappe app — a versioned, bench-installable package with its own module — that registers Moyasar as a first-class ERPNext Payment Gateway. We add a Moyasar Settings DocType (single) to hold your publishable and secret API keys, currency, and enabled payment methods, encrypted using Frappe's password fieldtype so secrets never sit in plaintext. From there the app wires into the standard Payment Request / Integration Request flow so a hosted Moyasar payment form or a direct API charge can be raised against any Sales Invoice, Sales Order, or web-shop order without leaving ERPNext.

Technically the connector is grounded in Frappe primitives, not a black box. Payment callbacks land on whitelisted methods (@frappe.whitelist(allow_guest=True)) exposed through the Frappe REST API; hooks.py doc_events on Payment Request and Sales Invoice keep document state in sync; and every gateway call is persisted as an Integration Request for a full audit trail. Webhook signatures from Moyasar are verified before any status change is trusted, so spoofed callbacks can't mark an invoice paid. mada, Visa, Mastercard, Amex, Apple Pay and STC Pay run through the hosted form or the API, SADAD handles bill-payment references, and tokenized cards enable recurring charges driven by a scheduler event (scheduler_events) for subscription-style billing. Refunds initiated from ERPNext call Moyasar's refund API and write the result back to the source document. Role-based permissions and a dedicated role profile keep gateway configuration and refund actions off limits for ordinary users.

Because this is build-to-order, nothing ships as an anonymous instant download. You request a quotation, we run a short scoping call to confirm your ERPNext version (v15 or v16), the exact payment methods and currencies you need, your checkout surface (web shop, Payment Request emails, or a custom portal), and any reconciliation or recurring-billing requirements. We then build against a staging clone of your site, run UAT with you, and hand over installable source code plus a git repository. Typical delivery is 2–4 weeks from confirmed scope, and every engagement includes a post-go-live support window and a documented rollback plan.