Quick facts
- Price
- $249.00 USD
- ERPNext versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
Tap & PayTabs Payment Gateway for MENA
Collect online payments across the GCC via Tap and PayTabs, fully wired into ERPNext invoices, quotations, and the web shop. ECOSIRE scopes, builds, installs, and supports the integration for your instance.
$249.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
Registers Tap and PayTabs as native ERPNext Payment Gateway Accounts, selectable anywhere ERPNext offers a gateway
Gateway-settings DocTypes storing API keys, merchant/entity IDs and currency map in encrypted Password fields — no secrets in plain text
Server-side integration with the Tap Charges API and PayTabs hosted/managed payment page (not a naive front-end redirect)
Payment links generated on Sales Invoice, Sales Order and Quotation via the Frappe Payment Request flow
Multi-currency GCC settlement (AED, SAR, KWD and other GCC currencies your acquirer enables) with correct invoice-currency charging
Whitelisted webhook receiver methods that verify HMAC/signature before trusting any callback
Automatic submitted Payment Entry creation against the source invoice via hooks.py doc events, updating outstanding and status
Scheduler Event reconciliation sweep that polls the gateway for pending/webhook-missed charges so no invoice is silently unpaid
ERPNext/Frappe web shop and portal checkout routed through the same gateway controller
Client script surfacing pay-now actions and payment status on invoice and customer portal
Dedicated audit-log DocType recording every gateway request, response and webhook for dispute handling
Role profile and ERPNext permission rules governing who can configure gateways and view transaction logs
Idempotent charge handling and duplicate-webhook protection to prevent double Payment Entries
Built and tested for Frappe/ERPNext v15 and v16, delivered as a bench-installable app
About this Product
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.
Why Choose Tap & PayTabs Payment Gateway for MENA
Registers Tap and PayTabs as native ERPNext Payment Gateway Accounts, selectable anywhere ERPNext offers a gateway
Gateway-settings DocTypes storing API keys, merchant/entity IDs and currency map in encrypted Password fields — no secrets in plain text
Server-side integration with the Tap Charges API and PayTabs hosted/managed payment page (not a naive front-end redirect)
Payment links generated on Sales Invoice, Sales Order and Quotation via the Frappe Payment Request flow
Multi-currency GCC settlement (AED, SAR, KWD and other GCC currencies your acquirer enables) with correct invoice-currency charging
Whitelisted webhook receiver methods that verify HMAC/signature before trusting any callback
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 2 to 4 weeks from confirmed scope, followed by a post-go-live support window. You own the code.
What you get
- Installable source code for your version of the Frappe app (bench get-app / install-app ready)
- Installation and gateway configuration on your ERPNext instance, wired to your Tap/PayTabs account
- Technical documentation — DocTypes, hooks.py doc events, whitelisted methods, webhook contract and scheduler jobs
- End-user guide plus a live training session for finance and sales users
- Post-go-live support window for defect fixes and configuration help
- UAT on a staging bench with sandbox credentials, sign-off, and a documented rollback plan
- Git repository handover with full commit history and README
- Reconciliation and webhook runbook for operations (retries, failed-charge handling, dispute lookups)
Who this is for
GCC E-Commerce Merchant
Runs an ERPNext web shop in the UAE, Saudi Arabia or Kuwait and needs locally accepted rails (KNET, mada, Apple Pay, cards) via Tap or PayTabs so checkout converts instead of failing on unsupported cards.
Finance / Accounts Manager
Wants online invoice payments to auto-reconcile into submitted Payment Entries against the right invoice, with an audit trail and a scheduler sweep for missed webhooks — ending manual bank-statement matching.
Multi-Entity GCC Group
Operates across several GCC currencies (AED, SAR, KWD) and needs each company/entity to charge in the invoice currency through its own Tap/PayTabs merchant account, all inside one ERPNext instance.
ERP / IT Lead
Owns the ERPNext deployment and needs a properly engineered, version-supported (v15/v16) app with the source, git repo, permission model and docs — not an opaque black-box plugin they cannot maintain.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Tap & PayTabs Payment Gateway for MENA app ZIP from your account dashboard.
Add the app to your bench
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Install on your site
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install Tap & PayTabs Payment Gateway for MENA and apply its schema.
Activate your license
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
How Tap & PayTabs Payment Gateway for MENA Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| GCC gateway support (Tap/PayTabs) | Both integrated natively, scoped to your account | Possible but you build and maintain it | Often single-gateway or generic, GCC gaps | |
| Multi-currency GCC (AED/SAR/KWD) | Invoice-currency charging, mapped per entity | Depends on your build effort | Varies, often single-currency assumptions | |
| Invoice/quotation payment links | Payment Request flow on invoice, order, quotation | Must design the Payment Request wiring yourself | Sometimes invoice-only | |
| Webhook reconciliation | Signed webhook + scheduler sweep, auto Payment Entry | You own retries and edge cases | Often front-end confirm, weak reconciliation | |
| Web shop checkout | Routed through the same gateway controller | Separate integration effort | May not cover the portal/web shop | |
| Source code & git handover | Full source and git repo you own | You own it because you built it | Usually closed-source, license-locked | |
| Support & version updates | Post-go-live window + optional retainer, v15/v16 | Entirely your team's burden | Vendor-dependent, may lag ERPNext releases | |
| Time to production | 2–4 weeks from confirmed scope, UAT on staging | Unpredictable, depends on in-house capacity | Fast install but rework to fit GCC rails |
Frequently Asked Questions about Tap & PayTabs Payment Gateway for MENA
Is this an existing app I can download from the Frappe Marketplace?
No. This is a build-to-order integration. ECOSIRE scopes, builds, installs, and supports it for your specific ERPNext instance, gateway accounts, and GCC currencies. You receive the full source and git repository at handover — there is no instant self-service download.
How long does delivery take?
Typically 2 to 4 weeks from confirmed scope. The timeline depends on how many gateways (Tap, PayTabs, or both), which GCC currencies, and which documents and web-shop paths must trigger payment. We agree the scope on a short call before any build starts, then prove it on a staging bench before go-live.
Which payment methods and gateways are supported?
Tap and PayTabs, which between them cover the common GCC rails — KNET, mada, Apple Pay, and card schemes — depending on what your acquirer/PSP account enables. We register each as a native ERPNext payment gateway; the exact method mix is confirmed against your merchant account during scoping.
Which ERPNext versions does it work on?
The app is built and tested for Frappe/ERPNext v15 and v16. If you run an older version, tell us during scoping and we will confirm feasibility or advise on an upgrade path before committing to the build.
What about support and updates after go-live?
Every engagement includes a post-go-live support window for defect fixes and configuration help. Because you own the source and git repo, your team can maintain it, and ECOSIRE offers ongoing support or a maintenance retainer for version upgrades, gateway API changes, and enhancements beyond the initial window.
How does payment reconciliation actually work?
When the gateway confirms a charge, a signed webhook hits a whitelisted server method that verifies the signature, finds the originating Payment Request, and creates a submitted Payment Entry against the invoice — updating outstanding and status automatically. A scheduler event also sweeps for pending or webhook-missed transactions and reconciles them by polling the gateway, so a dropped callback never leaves an invoice silently unpaid.
Do you handle our API keys and PCI concerns securely?
Yes. Payments use the gateways' hosted payment pages, so raw card data never touches your ERPNext server. API keys and merchant IDs are stored in encrypted Password fields, webhooks are signature/HMAC verified, and access is governed by a dedicated role profile and ERPNext permission rules.
Related Modules
Request a quote
Tap & PayTabs Payment Gateway for MENA
Collect online payments across the GCC via Tap and PayTabs, fully wired into ERPNext invoices, quotations, and the web shop. ECOSIRE scopes, builds, installs, and supports the integration for your instance.
- Registers Tap and PayTabs as native ERPNext Payment Gateway Accounts, selectable anywhere ERPNext offers a gateway
- Gateway-settings DocTypes storing API keys, merchant/entity IDs and currency map in encrypted Password fields — no secrets in plain text
- Server-side integration with the Tap Charges API and PayTabs hosted/managed payment page (not a naive front-end redirect)
- Payment links generated on Sales Invoice, Sales Order and Quotation via the Frappe Payment Request flow