Merchants in Saudi Arabia and the UAE lose conversions at checkout when their only options are card or bank transfer. Shoppers increasingly expect BNPL — split-in-3 and pay-later — and Tamara is one of the dominant providers in the GCC. ERPNext core has no concept of Tamara: its Payment Gateway and Payment Request framework covers a fixed set of gateways, the website checkout has no way to surface BNPL eligibility or promo messaging, and there is no mechanism to reconcile an asynchronous authorize/capture/refund lifecycle against Sales Orders and Sales Invoices. Bolting this on with ad-hoc server scripts leaves you with unsigned webhooks, no idempotency, and payment states that silently drift out of sync.

ECOSIRE builds a proper Frappe app — a versioned, installable package with its own module, DocTypes, hooks.py doc events, whitelisted API methods, and scheduler entries — that integrates Tamara cleanly into your ERPNext checkout and order flow. A Tamara Settings single DocType holds your merchant token, notification/public keys, environment (sandbox/production), and enabled payment types, encrypted as password fields. At checkout we run an eligibility and risk pre-check against Tamara's API for the cart total, currency, and country, then render localized promo widgets — Arabic and English, with correct RTL layout and instalment breakdowns — via a client script on the website checkout and product pages. When the customer chooses Tamara, we create a checkout session, persist a Tamara Transaction DocType linked to the ERPNext Sales Order/Payment Request, and redirect to the hosted flow.

The lifecycle is handled end to end. A whitelisted webhook endpoint receives Tamara notifications, verifies the signature, enforces idempotency on the event id, and drives state transitions: authorized orders move forward, captured payments post a Payment Entry against the Sales Invoice, and refunds initiated from ERPNext (via a custom action that calls Tamara's refund API) sync back and update transaction status. hooks.py doc_events on Sales Invoice submit trigger capture where your policy is capture-on-fulfilment; a scheduler event periodically reconciles any transactions left in a pending state so nothing is lost to a dropped webhook. All Tamara API calls, request/response payloads, and status changes are logged for audit and dispute handling. Role-based permissions restrict Tamara Settings and refund actions to finance roles you designate.

Everything is built against your ERPNext version (v15 or v16) and your actual checkout configuration — website store, POS, or a custom sales flow — so it fits your data model instead of forcing a generic one. The app is delivered as clean source in a git repository you own, with migrations, fixtures for custom fields and roles, and no core-file patches.

Because this is build-to-order, there is no instant download. After a short scoping call we confirm the exact flows, currencies, and capture policy, then build, test on a staging bench, and install on your instance. Typical delivery is one working week from confirmed scope, followed by a post-go-live support window. You receive the full source, documentation, and a training session — you are never locked to us.