Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.
Kurze Fakten
- Preis
- $299.00 USD
- ERPNext-Versionen
- —
- Rüstzeit
- 30 Min
- Lizenz
- Einmalig und unbefristet
- Sprachen
- 11 Sprachen
Einmalkauf
PayTabs Payment Gateway for ERPNext
A build-to-order Frappe app that wires PayTabs into ERPNext's Payment Gateway framework, so MENA merchants can accept mada, Visa, Mastercard, Amex, Apple Pay and STC Pay across 168+ currencies with hosted or seamless checkout. ECOSIRE builds, installs and supports it for your scope.
$299.00USD
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Hauptfunktionen
Registers PayTabs as a native ERPNext Payment Gateway so Payment Requests, Sales Invoices and POS flows resolve to a real Payment Entry
`PayTabs Settings` Single DocType holding profile ID, server key and client key as encrypted `Password` fields, plus region and default-currency config
Hosted payment page mode (PCI scope minimised) and seamless iframe mode embedded in the ERPNext web/Portal checkout via a client script
mada domestic Saudi debit acceptance alongside Visa, Mastercard and American Express card rails
Apple Pay and STC Pay wallet support surfaced in the checkout options
Multi-currency acceptance across 168+ currencies with per-transaction currency mapped to the ERPNext document currency
Whitelisted server callback method that verifies the PayTabs return signature before creating any Payment Entry
Idempotent postback handling keyed on the PayTabs transaction reference so duplicate callbacks never double-post a Payment Entry
Tokenization for repeat customers — saved-card tokens stored against the Customer for one-click reorders
Refund and partial-refund action from ERPNext, gated behind a `Payments Manager` role profile and written back to the transaction log
`hooks.py` doc events wiring Payment Request submission to gateway checkout creation, with a `PayTabs Transaction Log` DocType for audit and querying
Scheduler event that reconciles pending/held transactions and flags mismatches for review
Frappe REST API + whitelisted methods so an external storefront or mobile app can initiate a PayTabs checkout through ERPNext
Built and certified against your target Frappe/ERPNext v15 or v16 bench, with sandbox and production credential profiles
Über dieses Produkt
If you sell in Saudi Arabia, the UAE or Egypt on ERPNext, the gap shows up the moment a customer reaches the pay button. ERPNext ships with generic Payment Gateway integrations (Stripe, Razorpay, PayPal, Braintree), but none of them clear mada — the domestic Saudi debit scheme that most local shoppers actually carry — and none surface Apple Pay or STC Pay natively. So you either lose the sale to cart abandonment, or you bolt on an off-platform checkout and lose the tie-back to your Sales Invoice, Payment Entry and reconciliation. This app closes that gap by making PayTabs a first-class citizen inside ERPNext.
Warum PayTabs Payment Gateway for ERPNext wählen
Registers PayTabs as a native ERPNext Payment Gateway so Payment Requests, Sales Invoices and POS flows resolve to a real Payment Entry
`PayTabs Settings` Single DocType holding profile ID, server key and client key as encrypted `Password` fields, plus region and default-currency config
Hosted payment page mode (PCI scope minimised) and seamless iframe mode embedded in the ERPNext web/Portal checkout via a client script
mada domestic Saudi debit acceptance alongside Visa, Mastercard and American Express card rails
Apple Pay and STC Pay wallet support surfaced in the checkout options
Multi-currency acceptance across 168+ currencies with per-transaction currency mapped to the ERPNext document currency
We build a proper Frappe app (its own module, installed via bench get-app and bench install-app) that registers a PayTabs provider against ERPNext's native Payment Gateway and Payment Request framework. A PayTabs Settings Single DocType holds your profile ID, server key and client key (stored as encrypted Password fields), your acquiring region, default currency and hosted-vs-seamless mode. From there the flow is standard ERPNext: a Payment Request generates a checkout, the customer pays via PayTabs, and a controller returns them to a whitelisted return handler. On the server side, hooks.py doc events and a whitelisted callback method validate the PayTabs return signature, look up the originating Payment Request, and create the Payment Entry — so every paid transaction reconciles against the correct invoice with no manual matching.
Technically, we cover both integration styles. Hosted payment page hands checkout entirely to PayTabs (fastest to certify, PCI scope minimised). The seamless iframe embeds card capture directly in your ERPNext web checkout or Portal page via a client script, for a branded, on-site experience. We handle mada, Visa, Mastercard and Amex card rails plus Apple Pay and STC Pay wallets, multi-currency acceptance across 168+ currencies, and optional tokenization so returning customers pay with a saved card token rather than re-entering details. Server-side callback verification, idempotent transaction handling (so a double PayTabs postback never creates two Payment Entries), and a scheduler event that reconciles any pending/held transactions round out the reliability story. Role-based permissions keep gateway credentials and refund actions restricted to a Payments Manager role profile, and all activity is written to a queryable log DocType.
Because this is build-to-order, nothing is a black box. After a short scoping call we confirm your acquiring setup, currencies, checkout style (hosted or seamless), and which ERPNext transactions trigger payment (Sales Invoice, POS, web checkout, or a custom Portal flow). We build against your target Frappe/ERPNext version (v15 or v16), test the full happy path plus failure and refund paths on a staging bench, run UAT with your team, and only then deploy to production with a rollback plan. You receive the source code for your version, the git repository, and a support window after go-live. Typical delivery is 2-4 weeks from confirmed scope.
Was Sie bekommen
- Installable Frappe app source code for your target ERPNext version (v15 or v16), installed via `bench get-app` / `bench install-app`
- Installation and configuration on your bench, including sandbox and production PayTabs credential profiles
- Technical documentation: DocType reference, hooks and callback flow, and credential/environment setup
- End-user guide plus a live training session for your finance and operations team
- UAT on a staging bench covering happy-path, declined-payment, refund and duplicate-callback scenarios, with a documented rollback plan
- Post-go-live support window for defect fixes and configuration adjustments
- Handover of the git repository with full commit history and branch/tag for your production version
Für wen das ist
Saudi ERPNext merchant needing mada
A KSA retailer or services business whose customers pay predominantly with mada and STC Pay. They run sales and invoicing in ERPNext and need domestic rails at checkout without pushing customers to an off-platform page that breaks reconciliation.
UAE / Egypt multi-currency seller
A cross-border merchant billing in AED, EGP, USD and more who needs PayTabs' 168-currency acceptance mapped cleanly onto ERPNext document currency, with each settled payment landing as a reconciled Payment Entry.
ERPNext implementation partner / internal ops lead
The person responsible for the bench who wants a clean, upgrade-safe Frappe app rather than patched core files — proper DocTypes, hooks and whitelisted methods, delivered as a git repo they can maintain.
Finance manager reconciling gateway settlements
Owns month-end close and needs every PayTabs card, wallet and refund transaction to reconcile against the right invoice automatically, with a permissioned, auditable log instead of manual matching.
Installationsübersicht
Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei der PayTabs Payment Gateway for ERPNext-App von Ihrem Konto-Dashboard herunter.
Fügen Sie die App zu Ihrer Bank hinzu
Extrahieren Sie die ZIP-Datei in den Apps-Ordner Ihrer Bank oder führen Sie „bench get-app“ mit dem Pfad zur extrahierten App aus.
Installieren Sie es auf Ihrer Website
Führen Sie „bench --site SITE_NAME install-app APP_NAME“ gefolgt von „bench migrate“ aus, um PayTabs Payment Gateway for ERPNext zu installieren und sein Schema anzuwenden.
Aktivieren Sie Ihre Lizenz
Öffnen Sie die ECOSIRE-Lizenzeinstellungen auf Ihrer Website und aktivieren Sie Ihren Lizenzschlüssel. Erfordert die kostenlosen Apps ecosire_connect und ecosire_license_client.
Wie PayTabs Payment Gateway for ERPNext im Vergleich abschneidet
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| mada / STC Pay support | Built in, matched to your enabled PayTabs methods | Possible but you build and maintain the rails | Often international cards only, mada patchy | |
| ERPNext reconciliation | Native Payment Request → reconciled Payment Entry | Depends on developer discipline | Varies; may need manual matching | |
| Checkout style | Hosted or seamless iframe, your choice | Whatever you scope and build | Usually one fixed mode | |
| Duplicate-callback safety | Idempotent, keyed on PayTabs reference | Must be engineered deliberately | Not guaranteed | |
| Upgrade safety | Standalone Frappe app, no core patches | Risk of core patching | Depends on the vendor's design | |
| Permissions & audit | Payments Manager role + transaction log DocType | You define it | Limited or none | |
| Support & delivery | Built, installed, UAT'd + post-go-live window | You own it end to end | Best-effort forum / vendor support | |
| ERPNext version fit | Built and certified for your v15 or v16 | Whatever you target | May lag current releases |
Häufig gestellte Fragen zu PayTabs Payment Gateway for ERPNext
+How long does delivery take?
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.
+Does it really support mada, Apple Pay and STC Pay, or just international cards?
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 payment page or seamless iframe — which should I use?
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.
+How does a payment tie back to my ERPNext invoice?
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.
+Will this survive an ERPNext upgrade, and do I get updates?
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.
+Who can process refunds and see the credentials?
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.
+Can an external storefront or mobile app trigger PayTabs through ERPNext?
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.
Verwandte Module
Angebot anfordern
PayTabs Payment Gateway for ERPNext
A build-to-order Frappe app that wires PayTabs into ERPNext's Payment Gateway framework, so MENA merchants can accept mada, Visa, Mastercard, Amex, Apple Pay and STC Pay across 168+ currencies with hosted or seamless checkout. ECOSIRE builds, installs and supports it for your scope.
- Registers PayTabs as a native ERPNext Payment Gateway so Payment Requests, Sales Invoices and POS flows resolve to a real Payment Entry
- `PayTabs Settings` Single DocType holding profile ID, server key and client key as encrypted `Password` fields, plus region and default-currency config
- Hosted payment page mode (PCI scope minimised) and seamless iframe mode embedded in the ERPNext web/Portal checkout via a client script
- mada domestic Saudi debit acceptance alongside Visa, Mastercard and American Express card rails