GCC e-commerce merchants running ERPNext hit a wall the moment they try to take real local payments. ERPNext ships generic gateway hooks (Razorpay, Stripe, PayPal, Braintree) and a Payment Gateway / Payment Request flow, but none of them speak the schemes your Kuwaiti, Saudi, and Emirati customers actually use — KNET, mada, benefit, or Apple Pay through a regional acquirer. Merchants end up bolting a hosted redirect onto the website, reconciling settlements by hand, and manually marking Sales Invoices as paid, which breaks the audit trail and leaves recurring billing impossible.

We build a proper Frappe app (erpnext_tap) that integrates Tap Payments directly into ERPNext's payment lifecycle. It registers a Tap Payments Settings single DocType for credentials and scheme configuration (test/live secret keys, merchant ID, enabled brands, settlement currency), extends the standard Payment Request and Web Checkout so charges are created through Tap's Charges API or the goSell hosted checkout, and captures the customer on Tap's token/source objects. Doc events wired through hooks.py (Payment Request on_submit, Sales Invoice on_update) create the charge and post a Payment Entry against the correct account only after Tap confirms CAPTURED — so ledgers never drift from acquirer reality.

Technically, the app exposes @frappe.whitelist() methods for charge creation, status polling, and refunds, plus a public webhook endpoint that validates Tap's hashstring HMAC signature before updating the linked document — guarding against spoofed callbacks. A scheduler event (hooks.py scheduler_events) reconciles pending charges and expires stale sessions, so a dropped redirect never leaves an order stuck. For subscriptions we store the Tap customer and card tokens against the ERPNext Customer to drive tokenized recurring charges from the Subscription DocType. Client Scripts render the goSell card SDK and Apple Pay / Google Pay buttons on the checkout, and role profiles plus permission rules keep secret keys visible only to your Payments Manager.

Because this is build-to-order, nothing ships as a one-click install. After a short scoping call we confirm your acquirer setup, enabled schemes, settlement currency, and ERPNext/Frappe version (v15 or v16). We build against a staging bench, run UAT with your real Tap test keys, hand over a git repository plus install and configuration docs, then install on your production bench and stay on a support window through go-live. Typical delivery is one working week from confirmed scope.