Os detalhes do produto são exibidos em inglês. Traduções em breve.
Fatos rápidos
- Preço
- $299.00 USD
- Versões ERPNext
- —
- Tempo de configuração
- 30 min
- Licença
- Uma vez perpétua
- Idiomas
- 11 idiomas
Compra Única
Telr Payment Gateway for ERPNext
A build-to-order Telr payment gateway integration for ERPNext that lets UAE e-commerce businesses accept 120+ currencies and 30+ payment methods, with hosted checkout, tokenized repeat billing and 3-D Secure. ECOSIRE builds, installs and supports it against your ERPNext v15/v16 instance.
$299.00USD
Sem pagamento agora. Isto envia um pedido de orçamento à nossa equipe — responderemos por e-mail com preços e próximos passos.
Recursos Principais
Registers Telr as a native option in ERPNext's `Payment Gateway Account` and `Payment Request` flow, so it behaves like a first-class gateway rather than a bolt-on
`Telr Settings` single DocType holding Store ID, auth/API key, currency defaults and a test/live mode toggle, with secrets stored using Frappe's encrypted-field handling
`Telr Transaction` DocType logging order reference, hosted-page cart ID, auth/return codes and the raw gateway response for full reconciliation and audit
Hosted payment page integration so card data never touches your ERPNext server, keeping PCI DSS scope to the minimal SAQ-A footprint
Telr mobile SDK support for in-app checkout on companion iOS/Android storefronts
3-D Secure 2 authentication and Telr fraud screening enforced before authorization, with declines mapped to clear ERPNext statuses
Tokenized repeat and subscription billing — a stored Telr token is charged against future `Subscription` / `Payment Request` cycles without re-collecting card details
120+ transaction currencies and 30+ payment methods exposed through the checkout, driven by your ERPNext currency and price list data
`@frappe.whitelist(allow_guest=True)` return and IPN callback endpoints that verify the transaction signature before any document is written
Idempotent callback handler that creates the `Payment Entry`, marks the `Sales Invoice` paid and completes the `Payment Request` exactly once, even on duplicate IPNs
`hooks.py` `doc_events` on Payment Request to trigger hosted-page creation, plus an hourly `scheduler_events` job that reconciles pending or dropped transactions against the Telr API
Multi-language checkout labels and receipts sourced from ERPNext, aligned to your site's configured languages
Dedicated role profile and permission rules so only authorized staff can view credentials or reprocess/refund a transaction
Client script on Sales Invoice and Payment Request forms showing live Telr transaction status and a link to the matching `Telr Transaction` log
Refund/void support via the Telr API surfaced as a permission-gated form action, writing back a reversing Payment Entry
Structured error logging to Frappe's `Error Log` with alerting hooks, so failed authorizations and callback mismatches are visible to ops
Sobre este Produto
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.
Por Que Escolher Telr Payment Gateway for ERPNext
Registers Telr as a native option in ERPNext's `Payment Gateway Account` and `Payment Request` flow, so it behaves like a first-class gateway rather than a bolt-on
`Telr Settings` single DocType holding Store ID, auth/API key, currency defaults and a test/live mode toggle, with secrets stored using Frappe's encrypted-field handling
`Telr Transaction` DocType logging order reference, hosted-page cart ID, auth/return codes and the raw gateway response for full reconciliation and audit
Hosted payment page integration so card data never touches your ERPNext server, keeping PCI DSS scope to the minimal SAQ-A footprint
Telr mobile SDK support for in-app checkout on companion iOS/Android storefronts
3-D Secure 2 authentication and Telr fraud screening enforced before authorization, with declines mapped to clear ERPNext statuses
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.
O que você ganha
- Installable Frappe app source code for your build, delivered as a versioned git repository you own
- Installation and configuration on your ERPNext environment (staging then production), including `Telr Settings` and `Payment Gateway Account` setup
- Technical documentation — DocType schema, hooks, whitelisted endpoints, callback flow and scheduler jobs
- End-user guide plus a live training session for finance and store-operations staff
- UAT on a staging copy of your site with a documented sign-off checklist and a tested rollback plan
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with commit history, branch strategy and upgrade notes for future ERPNext versions
- Telr onboarding assistance — mapping your Store ID, keys and enabled payment methods into the integration
Para quem é isso
UAE ERPNext e-commerce operator
Runs an online store on ERPNext and needs Telr as the checkout so GCC customers pay with locally trusted cards and wallets, with paid orders flowing straight into Sales Invoices and Payment Entries — no manual reconciliation.
Subscription / recurring-billing business
Bills customers on a repeating cycle and needs Telr tokenization wired to ERPNext `Subscription` and `Payment Request` so saved cards are charged automatically each period without re-collecting card details.
Finance and controllership lead
Owns the ledger and wants every Telr settlement matched to a Payment Entry, a clear audit trail in `Telr Transaction`, and role-based control over who can see keys or issue refunds.
ERPNext technical owner / systems integrator
Maintains the ERPNext instance (v15/v16) and wants a clean Frappe app with source in git, standard `hooks.py` events and whitelisted methods, so the integration is maintainable and survives upgrades.
Visão geral da instalação
Baixe do ECOSIRE
Compre a licença em ecosire.com e baixe o ZIP do aplicativo Telr Payment Gateway for ERPNext no painel da sua conta.
Adicione o aplicativo à sua bancada
Extraia o ZIP na pasta de aplicativos do seu banco ou execute `bench get-app` com o caminho para o aplicativo extraído.
Instale no seu site
Execute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench Migra` para instalar Telr Payment Gateway for ERPNext e aplicar seu esquema.
Ative sua licença
Abra as configurações de licença ECOSIRE em seu site e ative sua chave de licença. Requer os aplicativos gratuitos ecosire_connect e ecosire_license_client.
Como Telr Payment Gateway for ERPNext se compara
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Telr support in ERPNext | Purpose-built Telr connector, native in the Payment Request flow | Depends entirely on your team's Frappe skill | Rarely covers Telr; built for generic gateways | |
| Delivery model | Build-to-order, 2–4 weeks from confirmed scope | Open-ended in-house project timeline | Instant install but generic fit | |
| Hosted page + PCI scope | Hosted page & mobile SDK, minimal SAQ-A scope | You must design and secure it yourself | Varies; often self-hosted card handling | |
| Tokenized recurring billing | Telr tokens wired to `Subscription`/`Payment Request` | Significant extra build effort | Usually one-off payments only | |
| Reconciliation & audit | `Telr Transaction` log + auto Payment Entry, hourly reconcile job | Whatever you find time to build | Basic status, limited audit trail | |
| Source code ownership | Full git repo handover, you own it | You own it, but you build and maintain it | Closed source, vendor-locked | |
| Support & upgrades | Post-go-live window + optional ongoing support | Self-supported | Vendor SLA, may not fit ERPNext specifics | |
| v15/v16 fit | Built and tested against your exact version | Depends on your testing rigor | May lag ERPNext releases |
Perguntas frequentes sobre Telr Payment Gateway for ERPNext
+Is this a ready-made app I can download and install today?
No. This is a build-to-order integration. ECOSIRE builds the Telr connector against your specific ERPNext version, Telr product set and hosting, then installs and supports it. It is not an existing Frappe Cloud Marketplace download, so there is no instant-download button — it starts with a scoping call.
+How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. The timeline depends on which Telr features you use (hosted page, mobile SDK, tokenized recurring billing, refunds) and your environment. After the scoping call we give you a firm estimate and milestones before any build work starts.
+Which ERPNext versions are supported?
We build and test against ERPNext / Frappe v15 and v16. We confirm your exact version during scoping and target it explicitly, and the git handover includes upgrade notes so the app can be maintained across future versions.
+How does the money actually get into ERPNext after a customer pays?
Telr posts a return and IPN callback to a signature-verified whitelisted endpoint. An idempotent handler then creates the matching `Payment Entry`, marks the `Sales Invoice` paid and completes the `Payment Request`. An hourly scheduler job reconciles any pending or dropped transactions against the Telr API so nothing is left in limbo.
+Is card data safe and PCI-compliant?
Yes. Checkout uses Telr's hosted payment page (and mobile SDK), so card data never touches your ERPNext server — that keeps your PCI DSS scope to the minimal SAQ-A footprint. 3-D Secure 2 and Telr's fraud screening run before authorization, and credentials are stored using Frappe's encrypted-field handling.
+Do you support recurring and subscription billing?
Yes. We use Telr tokenization so a saved card token can be charged against future ERPNext `Subscription` and `Payment Request` cycles without re-collecting card details, with each charge written back as a Payment Entry.
+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 full source in a git repository you own, you or any Frappe developer can maintain it long-term. ECOSIRE also offers ongoing support and upgrade engagements beyond the initial window.
Módulos Relacionados
Solicitar orçamento
Telr Payment Gateway for ERPNext
A build-to-order Telr payment gateway integration for ERPNext that lets UAE e-commerce businesses accept 120+ currencies and 30+ payment methods, with hosted checkout, tokenized repeat billing and 3-D Secure. ECOSIRE builds, installs and supports it against your ERPNext v15/v16 instance.
- Registers Telr as a native option in ERPNext's `Payment Gateway Account` and `Payment Request` flow, so it behaves like a first-class gateway rather than a bolt-on
- `Telr Settings` single DocType holding Store ID, auth/API key, currency defaults and a test/live mode toggle, with secrets stored using Frappe's encrypted-field handling
- `Telr Transaction` DocType logging order reference, hosted-page cart ID, auth/return codes and the raw gateway response for full reconciliation and audit
- Hosted payment page integration so card data never touches your ERPNext server, keeping PCI DSS scope to the minimal SAQ-A footprint