Saudi shoppers reach for their wallets, not their cards. STC Pay dominates local peer-to-peer and retail flows, Apple Pay carries most iPhone checkouts, and mada tokenized wallets convert far better than raw PAN entry — yet ERPNext core ships with no native concept of any of them. Out of the box the ERPNext Payment Gateway framework and the Web Payments flow give you a generic redirect to whatever gateway you configured; there is no STC Pay button, no Apple Pay merchant validation handshake, no Google Pay sheet, and no one-tap express path. Merchants end up bolting on hosted payment pages that break the ERPNext order lifecycle, lose the payment reference, and force customers off-site at the exact moment conversion is most fragile.

This kit is a proper Frappe app (a real module with its own hooks.py, DocTypes, and versioned migrations) that ECOSIRE builds for your instance to close that gap. We add a Wallet Payment Settings single DocType to hold your STC Pay merchant credentials, Apple Pay merchant identifier and domain-association file, Google Pay merchant info, and mada/gateway routing — with secrets stored as Frappe password fields, never in plaintext. Wallet buttons render on the Web Payments checkout and (optionally) the ERPNext POS via client scripts, and a set of @frappe.whitelist() server methods handle the parts that must run server-side: the Apple Pay merchant-session validation call to Apple's gateway, STC Pay charge/OTP initiation, and signed tokenization against your acquiring gateway (Moyasar, HyperPay/PayFort, Tap, or your existing Saudi provider). Every wallet transaction is captured as a Wallet Transaction DocType linked back to the Sales Order or Sales Invoice so the payment reference, gateway response, and reconciliation status live inside ERPNext where your finance team already works.

Under the hood the app leans on the framework rather than fighting it. hooks.py doc events fire on Payment Entry and Sales Invoice on_submit to reconcile wallet captures and post the corresponding accounting; a scheduler event polls for pending/async STC Pay confirmations and expires stale checkout sessions; and the whitelisted endpoints are exposed cleanly through the Frappe REST API so a headless storefront or mobile app can drive the same one-tap flow. Access is governed by a dedicated role and role profile so only authorized users read the credential DocType or reconcile transactions, and all button-render and validation logic degrades gracefully — an unsupported device or browser simply never sees the Apple Pay button, so nothing breaks for non-Apple traffic.

Because this is build-to-order, you are not downloading a frozen marketplace app and hoping it fits. After a short scoping call we confirm your ERPNext version (v15 or v16), your current Saudi acquiring gateway, which surfaces need wallet buttons (web checkout, POS, headless), and your reconciliation and VAT-invoice expectations. ECOSIRE then builds the app against that scope, provisions Apple Pay domain verification and STC Pay merchant onboarding with you, and validates the full flow on a staging bench before touching production. Typical delivery is one working week from confirmed scope. You receive the installable source, a documented git repository, UAT sign-off with a rollback plan, and a post-go-live support window — this is a real engineering engagement, not a plugin purchase.