South Asia Payment Gateway Pack

The problem: your invoices have no Pay button

Zoho Books and Zoho Invoice have an excellent online-payment story — for merchants in the countries whose gateways sit in Zoho's catalogue. If you invoice from Pakistan, Bangladesh or Sri Lanka, that catalogue is largely empty for you. The result is an invoice PDF that ends with bank account details typed into the notes field, a customer who screenshots a transfer receipt onto WhatsApp, and a finance person who manually opens the invoice, records a payment, guesses the reference and hopes the amount matches after charges.

Everything downstream breaks from there. Payment status in Zoho Books is only as fresh as the last person who checked the bank portal. Automated reminders keep chasing customers who already paid two days ago. Partial payments and instalments turn into a manual ledger. Multi-currency invoices settle at whatever rate the bank felt like and nobody records the difference. And because there is no machine-readable payment event, none of your Zoho CRM automation — renewal triggers, deal stage moves, delivery release — can key off payment at all.

The rails your customers actually use exist. Mobile wallets, instant bank transfer schemes, card acquirers and aggregator platforms all have documented APIs in each of these markets. They are simply not wired into Zoho. That wiring is what this build is.

What ECOSIRE builds

ECOSIRE builds a payment collection layer for your Zoho organisation covering the specific local providers you nominate during scoping. Nothing here is pre-built and downloadable — the provider list, the currencies, the reconciliation rules and the account mappings are yours, and we build against them.

A hosted payment page tied to your invoice

We build a branded payment page as a Zoho Creator application, reachable from a link that is embedded directly on the invoice — in the emailed invoice template, in the PDF, and as a shareable link your team can send over any channel. The page reads the live invoice from the Zoho Books API, shows the exact balance due, and presents the payment methods you have enabled for that customer's country and currency. Nothing is hard-coded: methods are configuration, not code changes.

Provider integrations in Deluge

For each nominated provider we build the request signing, checkout initiation, redirect or QR handling, and status polling as Deluge custom functions calling the provider's REST API. Where a provider issues a webhook, we build a secured public endpoint to receive it. Where a provider offers no webhook — which is common in these markets — we build a scheduled status-reconciliation job that polls open payment attempts and closes them out, so the absence of a callback never leaves an invoice permanently in limbo.

Automatic reconciliation into Zoho Books

A confirmed payment creates a Customer Payment record against the correct invoice in Zoho Books, with the provider's transaction reference stored in a custom field so you can trace any figure back to the provider's own dashboard. Gateway charges post to a nominated expense account rather than silently reducing revenue. Partial payments apply correctly and leave the residual balance open. Where you allow instalments, each collection applies against the same invoice in sequence.

Failure, retry and idempotency

Duplicate callbacks, browser back-buttons, double-clicked pay buttons and simultaneous retries are the normal condition of payment integration, not the exception. Every payment attempt is recorded with its own identifier and every confirmation path checks whether that attempt has already been settled before writing anything to Books. A payment is applied once, or not at all.

Operational visibility

A Creator dashboard shows every attempt with its status, provider, amount, invoice, timestamp and failure reason. Failed and pending attempts can be inspected and re-checked against the provider without touching the Books record directly. Daily provider-versus-Books totals give your finance team a same-day answer to whether the two agree.

CRM and workflow hooks

A settled payment can fire Zoho Flow flows and Zoho CRM workflow rules — move a Deal stage, stamp a Contact field, release a delivery task, notify a sales owner, trigger a renewal sequence. Because payment finally exists as a real event inside Zoho, the rest of your automation can depend on it.

Who this is for

Merchants, agencies, SaaS businesses, education providers and service firms invoicing from Pakistan, Bangladesh or Sri Lanka who already run Zoho Books or Zoho Invoice and are currently collecting by manual bank transfer. It matters most when invoice volume is high enough that manual payment entry is a daily job, or when payment needs to trigger something else — access, delivery, renewal — with no human in the loop.

How delivery works

1. Scoping call. We identify exactly which providers you hold merchant accounts with (or intend to open), the currencies involved, whether you need partial payments or instalments, which Books organization is in scope, and how charges should post. 2. Fixed quote. A written scope and a fixed price, issued before any build begins. Adding a provider later is a separately quoted change, priced honestly. 3. Build. Deluge functions, the Creator payment page and dashboard, webhook endpoints, reconciliation jobs and field mappings are developed against your test setup. Typical lead time is two to four weeks depending on how many providers are in scope and how quickly provider sandbox credentials are issued. 4. Install in test. We install into a test Books organization and run real sandbox transactions through every enabled method — success, failure, timeout, duplicate callback and partial payment — with you watching the resulting Books records. 5. Production go-live. Live credentials configured, endpoints registered with each provider, first real transactions monitored with your team. 6. Support window. A post-go-live defect-fix and configuration-support period, with documentation covering each provider's configuration and the reconciliation procedure.