PayTabs Payment Gateway for ERPNext

ECOSIRE builds a proper Frappe app — for example erpnext_paytabs — that registers PayTabs as a native gateway in ERPNext. It exposes a PayTabs Settings DocType holding your Profile ID, Server Key, region endpoint, and supported currencies (secrets stored via Frappe's Password fieldtype, never in plaintext), and wires into the standard Payment Request flow so any Sales Invoice, Sales Order, or web-shop checkout can redirect the customer to a PayTabs hosted payment page. The customer pays with mada, cards, Apple Pay, or a regional wallet on PayTabs' PCI-scoped page — no card data ever touches your ERPNext server.

Technically, the confirmation path is webhook-driven for reliability. A whitelisted method (@frappe.whitelist(allow_guest=True)) receives PayTabs' server-to-server callback, verifies the signature/cart_id, and on a successful tran_type creates and submits the matching Payment Entry, reconciles it against the originating invoice, and flips the Payment Request to Paid. hooks.py doc events keep everything consistent — for instance an on_submit handler on Sales Invoice can auto-issue a payment link, and a scheduler event (scheduler_events) polls PayTabs' query API to catch any callback that was dropped, so a momentary network blip never leaves a paid order stuck as unpaid. Refunds and voids are handled from within ERPNext: an authorized user triggers a refund from the Payment Entry, the app calls PayTabs' refund API, and a credit/reversal is recorded back against the ledger. Client scripts add the "Pay with PayTabs" actions to the relevant forms, and role profiles plus DocType permissions keep refund/void rights restricted to finance roles.

Because this is build-to-order, you are not downloading a one-size-fits-all plugin and hoping it matches your setup. We start with a short scoping call to confirm your PayTabs region and account type, the currencies and payment methods you actually use, which documents should trigger payment (invoices, sales orders, POS, web-shop), and your reconciliation and refund policies. We then build against your Frappe/ERPNext version (v15 or v16), deliver on a staging site for UAT, and only cut over to production once you have signed off. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full source code, git repository, and a post-go-live support window — the app is yours to keep, extend, and self-host.