Merchants across the GCC lose sales when checkout only supports cards that local buyers do not use. ERPNext ships with a handful of generic payment gateways (Razorpay, Stripe, PayPal, Braintree), but none of them clear KNET in Kuwait, mada in Saudi Arabia, Apple Pay through a regional acquirer, or the Tap and PayTabs rails that most Gulf banks and PSPs actually settle through. Out of the box there is no Payment Gateway Account for Tap or PayTabs, no way to attach a hosted payment link to a Sales Invoice sent to a customer, and no reconciliation loop that marks an invoice paid the moment the processor confirms — so finance teams end up chasing bank statements and reconciling by hand.

ECOSIRE builds a proper Frappe app (its own module, installable with bench get-app and bench install-app) that registers Tap and PayTabs as first-class ERPNext payment gateways. We add gateway-settings DocTypes that hold your API keys, merchant/entity IDs, and currency mapping (encrypted Password fields, never plain text), plus a Payment Request flow so any Sales Invoice, Sales Order, or Quotation can generate a hosted checkout link or a Charge/Invoice on the gateway. The integration server-side calls the Tap Charges API and the PayTabs Managed/Hosted Payment Page, and supports multi-currency GCC settlement (AED, SAR, KWD, and the other GCC currencies your acquirer enables) so an invoice raised in KWD is charged in KWD without rounding surprises.

Technically it is real Frappe engineering, not a redirect wrapper. Confirmation runs through whitelisted server methods that receive the gateway webhook, verify the signature/HMAC, look up the originating Payment Request, and — via hooks.py doc events and a controller method — create and submit the Payment Entry against the correct invoice, updating outstanding amount and status atomically. A Scheduler Event sweeps for pending or webhook-missed transactions and reconciles them by polling the gateway, so a dropped webhook never leaves an invoice silently unpaid. We expose the web-shop path too: the ERPNext/Frappe web shop and portal checkout route through the same gateway controller, and a small client script surfaces pay-now actions on the invoice and portal. Access is governed by ERPNext permissions and a dedicated role profile, and every API call and webhook is written to a log DocType for audit and dispute handling. The app targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing is shipped blind. We start with a short scoping call to confirm which gateway(s), which GCC currencies, which acquirer/PSP account, and which documents (invoice, order, quotation, web shop) must trigger payment. We build against your requirements, prove it on a staging bench with UAT and sandbox credentials from Tap/PayTabs, then install on your instance and hand over the source and git repository. Typical delivery is one working week from confirmed scope, followed by a post-go-live support window. You own the code.