UAE-based businesses running ERPNext on a webshop or subscription model hit a wall at the payment layer. ERPNext ships with a Payment Gateway abstraction and integrations for the likes of Razorpay, Stripe, PayPal and Braintree — but none of them natively speak to Telr, the Dubai-headquartered acquirer that most GCC banks and marketplaces prefer. Without a Telr connector you are stuck reconciling settlements by hand, forcing customers off-site to a disconnected checkout, and getting no automatic write-back of paid status into your Sales Invoice and Payment Entry documents. That gap is exactly what this build-to-order integration closes.

We build a proper Frappe application — not a pile of loose server scripts — that registers Telr as a first-class option in ERPNext's Payment Gateway Account and Payment Request flow. The app ships a Telr Settings single DocType (Store ID, auth key, test/live toggle, currency defaults) with credentials stored via Frappe's encrypted field handling, plus a Telr Transaction DocType that logs every order, hosted-page reference, return code and gateway response for audit and reconciliation. Checkout uses Telr's hosted payment page and mobile SDK so card data never touches your server (keeping PCI scope minimal), while 3-D Secure 2 and Telr's fraud screening run before authorization. Repeat and subscription billing use Telr tokenization so a saved token can be charged against future Subscription/Payment Request cycles without re-collecting card details.

Technically, the integration is wired through hooks.py document events and whitelisted methods. A @frappe.whitelist(allow_guest=True) endpoint receives Telr's return and IPN callbacks, verifies the transaction signature, and — inside an idempotent handler — creates the matching Payment Entry, marks the Sales Invoice paid, and moves the Payment Request to Completed. doc_events on Payment Request trigger hosted-page creation; a scheduler_events hourly job polls for pending or ambiguous transactions and reconciles them against the Telr API so a dropped browser session never leaves an order in limbo. All customer-facing amounts, currency and multi-language checkout labels are driven from ERPNext data via the Frappe REST API, and access is controlled with a dedicated role profile so only authorized users can view keys or reprocess transactions. A client script surfaces live transaction status on the Sales Invoice and Payment Request forms.

Because this is build-to-order, nothing is a black-box download. After a short scoping call we confirm the exact Telr product set you use (hosted page, mobile SDK, tokenization, recurring), your ERPNext version (v15 or v16) and hosting, then build and configure the app against a staging copy of your site. Typical delivery is 2–4 weeks from confirmed scope. You get the full app source in a git repository, install and configuration on your environment, UAT sign-off on staging with a documented rollback plan, technical and user documentation, a training session, and a post-go-live support window. ECOSIRE builds it, installs it, and stands behind it.