Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $249.00 USD
- ERPNext versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
एक बार की खरीदारी
Tap Payments Gateway for ERPNext
A build-to-order Tap Payments integration for ERPNext that adds KNET, mada, Apple Pay and card checkout, webhook-driven reconciliation, and refunds. ECOSIRE builds, installs, and supports it after you request a quotation.
$249.00USD
अभी कोई भुगतान नहीं। यह हमारी टीम को एक कोटेशन अनुरोध भेजता है — हम कीमत और अगले चरणों के साथ ईमेल द्वारा संपर्क करेंगे।
प्रमुख सुविधाएँ
Registers Tap as a native ERPNext Payment Gateway via a Payment Gateway Account, so Payment Requests route to it like any built-in gateway
Tap-hosted redirect checkout and inline card form, selectable per Payment Request or web checkout
KNET, mada, Benefit, Apple Pay and international card scheme support with per-method enable/disable in settings
Multi-currency GCC processing (KWD, SAR, AED, BHD, QAR, OMR) with currency passed straight to the Tap Charge API
Gateway controller implemented against Tap's Charges and Refunds REST endpoints with typed request/response handling
Encrypted credential storage in a Tap Settings Single DocType — secret keys never live in code or version control
Whitelisted charge-creation and redirect-callback methods (@frappe.whitelist(), allow_guest for the webhook)
HMAC hashstring signature verification on every inbound webhook to reject forged or replayed callbacks
Idempotent webhook processing keyed on Tap charge_id so retried webhooks never double-post a Payment Entry
hooks.py doc events keep Sales Invoice, Payment Request and Payment Entry states consistent on submit/update
Custom fields for Tap charge_id, card scheme, last-four and payment status written back for a full audit trail
Refunds and partial captures triggered from a Payment Entry button, with the Tap refund reference recorded on-document
Hourly scheduler_events job reconciles charges stuck in an intermediate/authorized state
Failed-capture and dispute Notifications routed to a finance Role Profile via Frappe's notification system
Client Scripts for the checkout UX and a customer-portal-friendly payment page for online orders
इस उत्पाद के बारे में
GCC businesses running ERPNext quickly hit a wall at the checkout: ERPNext ships Stripe, PayPal, Razorpay and a handful of other gateways out of the box, but there is no native connector for Tap Payments — the processor most Gulf merchants actually rely on for KNET, mada, Benefit and locally-issued cards. That means KWD, SAR, AED and BHD payments either get collected outside ERPNext and reconciled by hand, or customers are pushed to a gateway that declines regional debit rails. The result is broken automation between your storefront, your Sales Invoice, and your General Ledger.
Tap Payments Gateway for ERPNext क्यों चुनें
Registers Tap as a native ERPNext Payment Gateway via a Payment Gateway Account, so Payment Requests route to it like any built-in gateway
Tap-hosted redirect checkout and inline card form, selectable per Payment Request or web checkout
KNET, mada, Benefit, Apple Pay and international card scheme support with per-method enable/disable in settings
Multi-currency GCC processing (KWD, SAR, AED, BHD, QAR, OMR) with currency passed straight to the Tap Charge API
Gateway controller implemented against Tap's Charges and Refunds REST endpoints with typed request/response handling
Encrypted credential storage in a Tap Settings Single DocType — secret keys never live in code or version control
ECOSIRE builds a proper Frappe app that registers Tap as a first-class payment gateway inside ERPNext. It plugs into the standard Payment Gateway Account and Payment Request flow, so a Sales Invoice, Web Order, or portal payment can hand off to Tap-hosted checkout or an inline card form without you leaving ERPNext. We implement the gateway controller against Tap's Charges and Refunds APIs, store credentials in an encrypted Frappe Single DocType (never in code), and expose whitelisted methods (@frappe.whitelist()) for creating charges and receiving redirects. Payment status, Tap charge_id, card scheme, and last-four are written back to custom fields on the Payment Request and linked Payment Entry so finance has a full audit trail.
Reconciliation is webhook-driven rather than polling-based. We register a Tap webhook endpoint as a whitelisted allow_guest method, verify the hashstring HMAC signature on every callback, and update payment state idempotently — a duplicate or replayed webhook can never double-post a Payment Entry. hooks.py doc events (on_submit, on_update) keep the Sales Invoice, Payment Request and Payment Entry in sync, a scheduler_events hourly job sweeps any charges left in an intermediate state, and failed captures raise a Frappe Notification to your finance role profile. Refunds and partial captures are handled from a custom button on the Payment Entry that calls Tap's refund endpoint and records the reference back on the document.
Because this is build-to-order, nothing is a black box. After you request a quotation we run a short scoping call to confirm which Tap products you use (KNET, mada, Apple Pay, cards, saved-card tokens), your currencies, and where payments originate (ERPNext portal, a headless storefront, or POS). We build against your Frappe/ERPNext v15 or v16 version, test on a staging bench with Tap test keys, run UAT with you, then install on production with a rollback plan and hand over the git repository. Typical delivery is 2–4 weeks from confirmed scope, and you own the source.
What you get
- Installable source code for your version — a versioned Frappe app targeting your ERPNext v15 or v16 bench
- Installation and configuration on your environment, including Tap Settings, Payment Gateway Account, and webhook registration
- Technical documentation: architecture, DocType and custom-field reference, API/webhook contract, and hooks map
- End-user guide plus a live training session for your finance and operations team
- UAT on a staging bench using Tap test keys, followed by a go-live cutover with a documented rollback plan
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with full commit history so you own and can extend the code
- Deployment checklist covering production keys, webhook URL, and Tap dashboard configuration
Who this is for
GCC e-commerce operator
Runs an online store on ERPNext (native web shop or headless) selling into Kuwait, KSA, UAE or Bahrain and needs KNET and mada acceptance so local debit customers can actually check out and have the payment auto-matched to the Sales Invoice.
Finance and accounts controller
Owns reconciliation in ERPNext and wants every Tap charge to post a Payment Entry automatically, with charge_id, card scheme and refunds visible on-document instead of exported from the Tap dashboard and keyed in by hand.
Services or subscription business
Sends payment links from ERPNext Payment Requests for invoices, retainers or bookings and needs Tap-hosted checkout, Apple Pay, and reliable webhook status so paid invoices close themselves.
ERPNext partner or in-house admin
Manages the bench and needs a clean, version-pinned Frappe app with encrypted credentials, whitelisted methods and documented hooks that they can maintain and upgrade across v15/v16, rather than a fragile one-off script.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Tap Payments Gateway for ERPNext 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 Payments Gateway for ERPNext 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 Payments Gateway for ERPNext Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Tap / KNET / mada support | Purpose-built Tap gateway with KNET, mada, Apple Pay and cards | Possible but you scope and build it yourself | Rare; most marketplace apps target Stripe/Razorpay | |
| ERPNext integration depth | Native Payment Gateway Account + Payment Request + Payment Entry | Depends entirely on your developer's approach | Often a bolt-on that skips standard payment docs | |
| Reconciliation | Signed, idempotent webhooks + hourly sweep job | Whatever you build; easy to get double-posts wrong | Frequently polling or manual status checks | |
| Refunds & partial capture | On-document button, reference recorded in ERPNext | Extra scope you must specify and build | Often not covered | |
| Version fit (v15/v16) | Built and tested against your exact bench version | You own compatibility across upgrades | May lag ERPNext releases | |
| Source & ownership | Full git repo handover — you own it | You own it but pay full build cost | Usually closed or licensed per site | |
| Security of credentials | Encrypted Single DocType, whitelisted methods, HMAC verify | Only as good as your implementation | Varies; not always audited | |
| Delivery & support | 2–4 weeks, UAT, rollback plan, support window | Timeline and support depend on your team | Download now, limited GCC support |
Frequently Asked Questions about Tap Payments Gateway for ERPNext
How long does delivery take?
This is a build-to-order integration, not an instant download. After a scoping call to confirm your Tap products, currencies and payment sources, typical delivery is 2–4 weeks from confirmed scope — including staging build, UAT and production cutover. Tighter timelines can sometimes be arranged during scoping.
Is this a ready-made app on the Frappe Marketplace?
No. ECOSIRE builds it for your environment and hands over the source. We tailor the gateway to your Tap account setup, your ERPNext version (v15 or v16), and your checkout flow, then install and support it — you are not downloading a generic pre-built app.
Which payment methods and currencies are supported?
KNET, mada, Benefit, Apple Pay and international card schemes, with per-method toggles. Multi-currency GCC processing covers KWD, SAR, AED, BHD, QAR and OMR — the exact set is confirmed during scoping based on what your Tap account is enabled for.
How does reconciliation work?
It is webhook-driven. Tap calls a signed webhook endpoint on every charge event; we verify the HMAC hashstring, then update the Payment Request and post a Payment Entry idempotently so retries never double-post. An hourly scheduler job sweeps any charge left in an intermediate state.
What about support and updates after go-live?
Every build includes a post-go-live support window for defect fixes and configuration changes. Because you receive the git repository, your team can maintain it; ECOSIRE also offers ongoing support and version-upgrade retainers, including moving the app across ERPNext v15/v16 upgrades.
Do refunds and partial captures work inside ERPNext?
Yes. A button on the Payment Entry calls Tap's refund endpoint for full or partial amounts and records the refund reference back on the document, so your accounts stay accurate without logging into the Tap dashboard.
Where are the Tap API keys stored?
In an encrypted Tap Settings Single DocType using Frappe's password field encryption. Secret keys are never committed to the repository or hard-coded, and access is restricted by role permissions.
कोटेशन का अनुरोध करें
Tap Payments Gateway for ERPNext
A build-to-order Tap Payments integration for ERPNext that adds KNET, mada, Apple Pay and card checkout, webhook-driven reconciliation, and refunds. ECOSIRE builds, installs, and supports it after you request a quotation.
- Registers Tap as a native ERPNext Payment Gateway via a Payment Gateway Account, so Payment Requests route to it like any built-in gateway
- Tap-hosted redirect checkout and inline card form, selectable per Payment Request or web checkout
- KNET, mada, Benefit, Apple Pay and international card scheme support with per-method enable/disable in settings
- Multi-currency GCC processing (KWD, SAR, AED, BHD, QAR, OMR) with currency passed straight to the Tap Charge API