Los detalles del producto se muestran en inglés. Próximamente traducciones.
Datos rápidos
- Precio
- $249.00 USD
- Versiones de ERPNext
- —
- tiempo de configuración
- 30 minutos
- Licencia
- Perpetuo único
- Idiomas
- 11 idiomas
Compra única
ERPNext PayTabs Connector
A build-to-order Frappe app that wires PayTabs hosted checkout, payment links, and webhook confirmation directly into ERPNext, automatically posting reconciled Payment Entries against your Sales Invoices. ECOSIRE builds, installs, and supports it on Frappe/ERPNext v15/v16.
$249.00USD
Sin pago ahora. Esto envía una solicitud de presupuesto a nuestro equipo; te responderemos por correo con precios y próximos pasos.
Características clave
Packaged as a proper Frappe app with its own module, DocTypes, and `hooks.py` — installs on your bench with `bench get-app` / `bench install-app`, no core patching
`PayTabs Settings` single DocType stores Profile ID, server key, and region endpoint encrypted via Frappe's Password fieldtype, with per-currency profile mapping
Integrates with ERPNext's native Payment Gateway and Payment Request flow so existing invoice and portal payment paths keep working
Hosted Payment Page redirect generation via the PayTabs API — card data stays on PayTabs' PCI-DSS page, never on your ERPNext server
Shareable payment link generation for email/WhatsApp collection, each link bound to a specific Sales Invoice or Payment Request
Webhook endpoint exposed as a guest-allowed whitelisted method with HMAC signature verification against your server key
Idempotency keying on the PayTabs transaction reference so retried IPN callbacks never create duplicate Payment Entries
Automatic creation and submission of reconciled `Payment Entry` records linked to the source invoice, inside a single atomic transaction
Scheduler event (cron `scheduler_events`) that polls the PayTabs query API to reconcile transactions whose webhook was missed or delayed
Multi-currency support with mapping to ERPNext currencies and local MENA methods (mada, STC Pay, Apple Pay, KNET where enabled on your PayTabs profile)
In-ERPNext refund action that calls the PayTabs refund API and posts the corresponding credit/return entry
Tokenized recurring payments reusing the stored PayTabs token for subscription rebilling without re-collecting card details
`PayTabs Transaction Log` DocType capturing full request/response payloads for audit, reconciliation, and dispute evidence
Role-scoped permissions and a dedicated role profile so only authorized finance users can view keys, trigger refunds, or read raw gateway logs
Client scripts and server scripts for status badges and validation on Sales Invoice / Payment Request, plus Frappe REST API access for headless/e-commerce checkout
Sobre este producto
MENA merchants running ERPNext hit a wall the moment they try to collect card payments the way their customers actually pay. ERPNext core ships a Payment Gateway framework with a handful of built-in integrations, but PayTabs — the dominant gateway across Saudi Arabia, the UAE, Egypt, Jordan, Oman, and beyond — is not one of them. Teams end up reconciling gateway settlements against ERPNext by hand, exporting CSVs from the PayTabs merchant dashboard, and guessing which Sales Invoice a payment belongs to. Multi-currency card acceptance, local methods like mada, STC Pay, and Apple Pay, refunds, and recurring billing all live outside the ERP, so finance never has a single source of truth.
Por qué elegir ERPNext PayTabs Connector
Packaged as a proper Frappe app with its own module, DocTypes, and `hooks.py` — installs on your bench with `bench get-app` / `bench install-app`, no core patching
`PayTabs Settings` single DocType stores Profile ID, server key, and region endpoint encrypted via Frappe's Password fieldtype, with per-currency profile mapping
Integrates with ERPNext's native Payment Gateway and Payment Request flow so existing invoice and portal payment paths keep working
Hosted Payment Page redirect generation via the PayTabs API — card data stays on PayTabs' PCI-DSS page, never on your ERPNext server
Shareable payment link generation for email/WhatsApp collection, each link bound to a specific Sales Invoice or Payment Request
Webhook endpoint exposed as a guest-allowed whitelisted method with HMAC signature verification against your server key
ECOSIRE builds a dedicated PayTabs connector as a proper Frappe app — its own module, DocTypes, and hooks.py wiring — that plugs into ERPNext's native Payment Gateway and Payment Request flow rather than bolting on a parallel system. A PayTabs Settings single DocType holds your Profile ID, server key, region endpoint, and currency mapping (encrypted via Frappe's password fieldtype). When a Sales Invoice or Payment Request needs collection, the app calls the PayTabs Hosted Payment Page API and returns a redirect URL, or generates a shareable payment link your team can send over email or WhatsApp. Customers pay on PayTabs' PCI-compliant page; card data never touches your ERPNext server.
Confirmation is webhook-first, not redirect-dependent. A whitelisted endpoint (@frappe.whitelist(allow_guest=True)) receives the PayTabs Instant Payment Notification, validates the HMAC signature against your server key, checks idempotency so a retried callback never double-posts, and on success creates and submits a reconciled Payment Entry linked back to the originating invoice — all inside a single database transaction. hooks.py doc events keep statuses in sync, a scheduler event reconciles any transactions that missed their webhook by polling the PayTabs query API, and every request/response is written to a PayTabs Transaction Log DocType for audit and dispute handling. Refunds are issued from within ERPNext and post the matching credit entry; tokenized recurring payments reuse the saved PayTabs token for subscription-style rebilling without re-collecting card details.
Because this is build-to-order, you are not downloading a generic marketplace app and hoping it fits. ECOSIRE scopes your exact PayTabs region, currencies, local methods, invoice/subscription workflow, and role permissions on a short call, then builds, tests on a staging bench, and installs the connector on your Frappe/ERPNext v15 or v16 site. Typical delivery is 2 to 4 weeks from confirmed scope. You receive the full source, documentation, a training session, a post-go-live support window, and the git repository so your team owns the code outright.
lo que obtienes
- Installable source code for your version of the connector, built for your Frappe/ERPNext v15 or v16 site
- Installation and configuration on your environment — bench app install, PayTabs Settings wiring, webhook URL registration, and region/currency setup
- Technical documentation: architecture, DocType schema, hooks and scheduler events, whitelisted endpoints, and webhook signature/idempotency logic
- User guide plus a live training session for your finance and operations team
- UAT on a staging bench before go-live, with a documented rollback plan
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover so your team fully owns and can extend the code
- Configuration record of PayTabs profiles, currency mapping, and enabled local methods for your account
¿Para quién es esto?
MENA e-commerce & retail merchant on ERPNext
Sells across GCC and North African markets and needs to accept regional cards and local methods (mada, KNET, STC Pay, Apple Pay) with every successful charge landing as a reconciled Payment Entry against the right Sales Invoice.
Finance / accounts manager
Owns month-end close and is tired of manually matching PayTabs dashboard settlements to ERPNext. Wants webhook-confirmed, idempotent posting, an audit log, and in-ERP refunds so the books reconcile without spreadsheets.
Subscription or services business
Bills recurring plans or retainers and needs tokenized rebilling through PayTabs so customer card details are stored once at the gateway and charged on schedule without re-collection.
ERPNext implementation partner / internal IT lead
Needs a clean Frappe app they can read, own, and maintain — proper DocTypes, hooks, and REST endpoints on v15/v16 — not an opaque marketplace plugin, so they can extend it as requirements evolve.
Descripción general de la instalación
Descargar desde ECOSIRE
Compre la licencia en ecosire.com y descargue la aplicación ZIP de ERPNext PayTabs Connector desde el panel de su cuenta.
Añade la aplicación a tu banco
Extraiga el ZIP en la carpeta de aplicaciones de su banco o ejecute `bench get-app` con la ruta a la aplicación extraída.
Instalar en su sitio
Ejecute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench migrar` para instalar ERPNext PayTabs Connector y aplicar su esquema.
Activa tu licencia
Abra la configuración de licencia de ECOSIRE en su sitio y active su clave de licencia. Requiere las aplicaciones gratuitas ecosire_connect y ecosire_license_client.
Cómo se compara ERPNext PayTabs Connector
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| Availability | Built to order for your PayTabs account, delivered in 2-4 weeks | Depends on hiring and internal roadmap | Instant install but generic fit | |
| PayTabs coverage | Hosted page, links, refunds, tokenized recurring, local methods | Whatever you scope and can afford to build | Often card-only, limited local methods | |
| Reconciliation | Webhook-confirmed, idempotent auto Payment Entry + scheduler backfill | Must be designed and hardened yourself | Basic callback, often no idempotency or backfill | |
| ERPNext integration | Native Payment Gateway/Request flow, DocTypes, hooks, REST | Varies by developer discipline | Sometimes bypasses native flow | |
| Code ownership | Full source + git repo handover | You own it, if it's documented | Closed listing, no source | |
| Version support | Built for v15/v16, upgrade path discussed | Whatever you target | May lag core releases | |
| Support | Post-go-live window + training + optional ongoing | Your team owns all support | Vendor tickets, variable SLA | |
| Total effort for you | Scoping call, UAT, go-live — we build the rest | Spec, build, test, maintain end to end | Install and hope it fits your workflow |
Preguntas frecuentes sobre ERPNext PayTabs Connector
+How long does delivery take?
This is a build-to-order product, not an instant download. Once we confirm scope on the initial call — your PayTabs region, currencies, local methods, invoice/subscription workflow, and permissions — typical delivery is 2 to 4 weeks. We build and test on a staging bench, run UAT with you, then install on your production Frappe/ERPNext site.
+Is this an existing app on the Frappe Cloud Marketplace?
No. ECOSIRE builds this connector to order as a proper Frappe app for your specific PayTabs account and ERPNext workflow. You get the source code and the git repository at handover, so you own it outright rather than renting a black-box listing.
+Which Frappe and ERPNext versions are supported?
We build for Frappe/ERPNext v15 and v16. If you're on an earlier version we'll discuss an upgrade path or a backport during scoping. The app installs on your bench via bench get-app / bench install-app with no core patching.
+How are payments confirmed and reconciled?
Confirmation is webhook-first. A signed PayTabs Instant Payment Notification hits a whitelisted endpoint, we verify the HMAC against your server key, apply idempotency so retries never double-post, and on success create and submit a Payment Entry linked to the invoice in one atomic transaction. A scheduler job also polls the PayTabs query API to catch any missed webhooks.
+Does card data touch our ERPNext server?
No. Customers pay on the PayTabs Hosted Payment Page, which is PCI-DSS compliant. Your ERPNext site only receives tokens and transaction references, which keeps your compliance surface small. Recurring billing reuses the PayTabs-stored token rather than storing card numbers.
+Do you support refunds and recurring payments?
Yes. Refunds are issued from within ERPNext via the PayTabs refund API and post the matching return entry. Tokenized recurring payments let you rebill subscriptions or retainers on schedule using the saved PayTabs token, without re-collecting card details.
+What support and updates come after go-live?
Every build includes a post-go-live support window for defect fixes and configuration adjustments, plus a training session and full documentation. Because you receive the git repository, your team can maintain and extend the connector independently, and we can quote ongoing support or feature work separately if you want us to keep evolving it.
Solicitar presupuesto
ERPNext PayTabs Connector
A build-to-order Frappe app that wires PayTabs hosted checkout, payment links, and webhook confirmation directly into ERPNext, automatically posting reconciled Payment Entries against your Sales Invoices. ECOSIRE builds, installs, and supports it on Frappe/ERPNext v15/v16.
- Packaged as a proper Frappe app with its own module, DocTypes, and `hooks.py` — installs on your bench with `bench get-app` / `bench install-app`, no core patching
- `PayTabs Settings` single DocType stores Profile ID, server key, and region endpoint encrypted via Frappe's Password fieldtype, with per-currency profile mapping
- Integrates with ERPNext's native Payment Gateway and Payment Request flow so existing invoice and portal payment paths keep working
- Hosted Payment Page redirect generation via the PayTabs API — card data stays on PayTabs' PCI-DSS page, never on your ERPNext server