This is build-to-order, not an instant AppSource install. After kickoff we scope your Easypaisa aggregator's API, build the AL extension, test it in your BC sandbox, then install it on production. Typical delivery is a few weeks, mainly gated by your sandbox access and Easypaisa merchant approvals — we confirm a firm timeline with you up front.

An active Business Central environment (Online/SaaS or on-prem) where we can be granted an extension-install role, and an active Easypaisa merchant or aggregator agreement with API credentials (or one in progress). We handle all the AL development, callback wiring, Job Queue setup, and permission sets.

Because it ships as a standard per-tenant extension, it is built to survive BC's monthly and major updates. Our engagement includes post-launch support and upgrade-compatibility maintenance — if a future BC release or an Easypaisa API change affects the connector, we update it. Support terms are agreed at the start; there is no surprise per-transaction fee from ECOSIRE.

Merchant ID, store ID, and API keys are stored using Business Central's Isolated Storage API, not in plain table fields, and access is gated behind a dedicated permission set. Payment and invoice data stays inside your own BC tenant — ECOSIRE does not route your transactions through any third-party system of ours.

It settles automatically. When Easypaisa confirms a payment, the callback handler (backed by a Job Queue reconciliation worker for late notifications) matches the transaction to the open invoice and posts a Cash Receipt Journal application, so the customer ledger clears with no manual matching. You still get a full per-transaction audit trail on the connector ledger page.

It is built PKR-native because Easypaisa settles in Pakistani Rupees, so there is no forced currency conversion. If your BC company also trades in other currencies, the connector simply handles the Easypaisa (PKR) collections; your existing multi-currency invoices in other currencies are unaffected.