PayTabs Payment Gateway for ERPNext

This is a build-to-order product, not an instant download. Typical delivery is 2-4 weeks from confirmed scope. We start with a short scoping call to lock down your acquiring setup, currencies, checkout style and target ERPNext version, then build, test on staging, run UAT and deploy. Complex flows (custom Portal checkout, multiple companies, unusual reconciliation rules) can extend the timeline, and we tell you that upfront.

Yes to all of them, provided your PayTabs merchant profile is enabled for them. The app exposes mada, Visa, Mastercard and Amex card rails plus Apple Pay and STC Pay wallets. Which methods a shopper sees depends on the currency, region and what your acquirer has switched on in your PayTabs account — we configure the app to match your enabled methods during setup.

Hosted is fastest to certify and keeps your PCI scope minimal because card entry happens on PayTabs' page. Seamless embeds card capture inside your ERPNext checkout via a client script for a fully branded, on-site experience but carries slightly more compliance responsibility. We build whichever you choose, and can support both in the same deployment for different flows.

The app is built on ERPNext's native Payment Request framework. When PayTabs returns a successful transaction, a whitelisted server callback verifies the signature, looks up the originating Payment Request, and creates a `Payment Entry` reconciled against the correct Sales Invoice. Handling is idempotent, so a duplicate PayTabs postback never creates two Payment Entries.

It is delivered as a standalone Frappe app with its own DocTypes and hooks — we do not patch ERPNext core, so standard `bench update` upgrades stay clean. We build and certify against your target v15 or v16. After go-live you get a support window for defect fixes and configuration adjustments; version bumps to a new major ERPNext release or new PayTabs API features are scoped as a follow-on engagement.

Gateway credentials are stored as encrypted `Password` fields and refund/partial-refund actions are gated behind a dedicated `Payments Manager` role profile. Every transaction and refund is written to a queryable `PayTabs Transaction Log` DocType, so you have a permissioned audit trail rather than open access.

Yes. We expose whitelisted methods over the Frappe REST API so a headless storefront, marketplace or mobile app can initiate a PayTabs checkout and receive status through ERPNext, keeping ERPNext as the single source of truth for orders, payments and reconciliation.