A build-to-order NetSuite connector for UPI, netbanking and card capture in INR with settlement-batch reconciliation. ECOSIRE scopes, quotes and builds it for your account — it is not a ready-made download. Built to order by ECOSIRE for Oracle NetSuite (build-to-order) — indicative price from $399.00 USD; request a quote for a scoped proposal.
A build-to-order NetSuite connector for UPI, netbanking and card capture in INR with settlement-batch reconciliation. ECOSIRE scopes, quotes and builds it for your account — it is not a ready-made download.
Built to order
Payments in India do not arrive in a shape NetSuite recognises. A single business day produces UPI collect requests, UPI intent links, netbanking redirects, card captures, EMI conversions and the occasional wallet debit. The gateway then settles those transactions in batches on a T+1, T+2 or custom cycle, net of platform fees and the GST charged on those fees, and frequently nets a refund or a chargeback off inside the same payout. NetSuite expects something much narrower: a Customer Payment record, applied to a named Invoice, in INR, inside an open Accounting Period, deposited to a specific Bank Account.
Bridging those two shapes by hand means exporting gateway reports, matching them to invoice numbers in a spreadsheet, keying Customer Payment records one at a time, and then trying to explain why the Undeposited Funds balance never clears and why the bank statement line for the payout is a single net figure that ties to no transaction in the ledger. It gets materially worse the moment a partial refund settles inside a payout that also carries the previous day's captures.
This connector is built to order for your account. Nothing here is a shrink-wrapped download. ECOSIRE scopes your capture flows, your chart of accounts and your subsidiary structure, quotes a fixed price, then builds and installs a SuiteScript 2.1 SDF project in your sandbox before anything touches production.
The delivered solution is a set of SuiteScript 2.1 scripts, custom record types, custom transaction body fields, saved searches and script deployments, packaged as an SDF project or unmanaged bundle that you own outright.
A Suitelet renders a branded, tokenised payment page. A User Event script on the Invoice record generates the link on approval and writes it, its expiry timestamp and its current status into custom transaction body fields, so the link can be merged into your Advanced PDF/HTML Template and emailed with the invoice itself. Customers choose UPI, netbanking or card at the gateway; the tender type they used is written back onto the resulting payment record for reporting.
A RESTlet, deployed to a dedicated integration role, receives gateway webhooks. Before any record is touched it verifies the provider HMAC signature using the N/crypto module and rejects anything that fails. Every accepted event is written to a custom record with the provider event id stored in a field marked unique, so a replayed or duplicated webhook is recognised and discarded rather than posting a second payment. Record creation runs asynchronously via N/task so the gateway always receives a fast acknowledgement.
This is the part naive integrations skip. A Map/Reduce script pulls settlement and payout reports from the gateway over its REST API on a schedule, and writes a Settlement Batch parent custom record with Settlement Line children — one per captured transaction, refund, adjustment or fee inside that payout. Each line is matched to its Customer Payment, and the batch total is matched to the single net figure that will appear on your bank feed. Unmatched lines are held in an exception queue with a reason code instead of being silently posted.
When a batch is confirmed, the connector creates the Deposit record for the gross captured amount and a Journal Entry for the gateway fee and the GST charged on that fee, using the expense account, tax code and nexus you nominate during scoping. The net result is a deposit whose value equals the bank line, which means the Match Bank Data screen can actually clear it.
Refund webhooks create a Credit Memo and Customer Refund pair, or apply against an existing credit, following the rule set you choose. Chargebacks and their reversals post to a dedicated account so disputed money is visible rather than buried inside fee noise, and the originating Invoice is stamped with the dispute state.
If you run OneWorld, capture is routed by subsidiary. Gateway credentials, bank accounts, fee accounts and tax codes are configured per subsidiary on a custom record, and every generated transaction is created against the correct subsidiary with the correct currency and exchange rate. A custom segment can be stamped on generated transactions if you need channel-level or entity-level analysis.
Credentials are held in NetSuite so they never sit in script constants. The integration user runs under a purpose-built role with only the permissions the scripts require. Every generated transaction carries a link back to the gateway event record, and the raw payload is retained, so any posting can be traced end to end during an audit.
Saved searches surface unmatched settlement lines, failed webhook events, expired payment links and batches that have not cleared. A Scheduled script emails a daily exception digest to your finance mailbox, and a dashboard portlet shows the current state at a glance.
Indian NetSuite tenants billing domestic B2B or D2C customers in INR; groups with an Indian subsidiary inside a OneWorld account that need local tender types without disturbing the global setup; and finance teams whose month-end close is currently gated by manual gateway reconciliation.
1. Scoping call. We walk your capture points, tender mix, chart of accounts, subsidiary structure, tax treatment and existing bank reconciliation process, and confirm which gateway account and API credentials will be used. 2. Fixed quote. You receive a written scope with the exact record types, scripts and postings that will be built, a fixed price and a delivery window. Nothing starts until you approve it. 3. Build. ECOSIRE develops the SuiteScript 2.1 project against your requirements. Typical lead time is two to four weeks depending on scope and how quickly sandbox access and gateway test credentials arrive. 4. Sandbox install. The SDF project is deployed to your sandbox account. We run capture, webhook, settlement, refund and chargeback scenarios against gateway test mode with you present, and adjust until your team signs off. 5. Production install. The same bundle is promoted to production, credentials are switched to live, and we run a small controlled first payout with you watching. 6. Support window. A defined post-go-live support period is included in the quote for defect fixes and configuration adjustments.
This is not a listed app you install in minutes, and it is not a certified or endorsed extension of any gateway or of NetSuite. It is custom development on your account, delivered as source you own. You keep your own gateway contract, your own merchant fees and your own compliance obligations; the connector moves and posts the data.
A short call to confirm the workflow, your platform version and where the integration boundaries sit.
You receive a written scope and a fixed price. Nothing is built until you approve it.
We develop against a copy of your configuration and test it there. Typically two to four weeks.
We install on your instance, hand over the source, and support it for twelve months.
Owns the close and currently cannot tie gateway payouts to the general ledger without a spreadsheet reconciliation each morning. This gives them deposits that match the bank line exactly, with fees and GST already journalled and an exception queue that names what is actually unresolved.
Is asked to make payments work but does not want to own an undocumented pile of scripts written by whoever was available. They receive a documented SDF project, a least-privilege integration role and saved searches that make failures visible before finance notices them.
Chases customers who claim they paid while the payment sits unapplied or in Undeposited Funds. Payment links go out on the invoice itself and captures apply straight to the right invoice, so the AR ageing reflects reality.
| Criterion | ECOSIRE | Custom Build | Competitor |
|---|---|---|---|
| UPI, netbanking and card capture initiated from the Invoice record | Included | Partial support | Partial support |
| Settlement-batch reconciliation down to the individual payout line | Included |
From $399.00
Starting point — quoted to your scope
| Partial support |
| Automatic posting of gateway fees and GST charged on those fees | Included | Partial support | Partial support |
|---|
| Signature-verified, idempotent webhook handling | Included | Partial support | Partial support |
|---|
| OneWorld per-subsidiary credentials, accounts and tax codes | Included | Partial support | Partial support |
|---|
| Delivered as an SDF project or unmanaged bundle you own | Included | Included | Not included |
|---|
| Fixed-price scope agreed before any build work starts | Included | Partial support | Partial support |
|---|
| Sandbox-first install with a joint test pass before production | Included | Partial support | Partial support |
|---|
A build-to-order NetSuite AP automation suite covering invoice capture, three-way match, approval routing and payment runs. ECOSIRE builds it for your account after a scoping call and fixed quote.
A build-to-order NetSuite statement engine for multi-book, multi-currency and multi-subsidiary reporting — SuiteQL-driven packs with configurable row structures and drill-down from any figure to its source transactions.
A NetSuite AI agent built to order for your account: it drafts dunning emails, predicts payment behaviour and matches remittance advice to open invoices — every action reviewable, nothing sent unapproved.
Multivariate demand and cash-flow forecasting trained on your own NetSuite history, with seasonality and driver variables. Build-to-order: scoped, fixed-quoted, then built and installed in your accounts.