Payment Gateway Integration in Delhi (2026)

A trading order is rarely settled once. The buyer releases an advance, sometimes a second tranche before dispatch, and the balance on a credit period that the partner negotiated in person. Each release needs its own reference, its own date and a running balance on the order.

We model the order with an expected value and a set of receipts, so the outstanding figure is computed rather than remembered. That also makes a part payment visible to the dispatch desk as a reason to hold a consignment, instead of a phone call from accounts.

A single current account receiving dozens of transfers a day cannot say who paid. A virtual account gives each party its own number, so an incoming credit identifies the buyer before anyone opens a statement.

For a firm with several hundred dealers or clients, that removes the daily exercise of matching narrations by hand. The mapping is maintained as parties are added, and an unmatched credit stays visible as a task rather than being parked in a suspense line.

Shops in markets such as Karol Bagh and Sadar Bazar take most small payments by scan, and the confirmation a customer sees is not the record the shop needs. The useful build prints or stores a receipt tied to the provider reference, then closes the day with a collection summary per counter.

Where several counters share an account, the summary is what settles an argument about which till took a payment. Where cash is still involved, the same daily sheet carries both, so the cashier reconciles once.

Outstation buyers and corporate purchase departments often want an invoice first and a payment route second. A link that carries the amount, the invoice reference and an expiry date does that work, and it can be forwarded inside the buyer's own finance chain without the seller losing sight of who it was issued to.

We keep a record of every link issued, whether it was opened, and what it settled, because a forwarded link without that history turns into a dispute about which invoice was paid.

Settlement in this market is slower and more staged than a retail checkout, so the state machine is longer: authorised, partially received, dispatched, balance due, closed. A provider event usually moves only one step of it.

The handler verifies the signature, records the event identity and applies the transition in a transaction. A duplicate delivery is discarded, and the audit entry names the event that changed the balance, which is what an auditor will ask for months later.

A trade refund is often an adjustment against a later invoice rather than money returned. Both cases exist and both need a record: one reduces the outstanding balance, the other leaves the firm's account and appears in a settlement.

Keeping them apart prevents the common mess where a credit note is issued, cash is also refunded, and the buyer's account shows a double benefit that nobody can explain at the year end.

The provider settles a net figure, the bank shows a credit, and the ledger has invoices against it. Matching those three is the part finance values most, so the import produces a line per settlement with the fees broken out and the invoices it clears.

Residue is surfaced deliberately: a receipt with no invoice, an invoice with no receipt, and an amount that differs after a chargeback. Each carries a status and a name, not just a number in a total.

Professional firms carry a confidentiality duty that makes a card data leak worse than a lost sale. Hosted payment pages and provider tokenisation keep card numbers out of the firm's systems, which is both the cheapest and the most defensible position.

We also insist on server-side authorisation for anything that touches a client account, secrets held outside the repository, and a written record of who can issue a refund. A payment flow without that last control is an internal risk, not just a technical one.

The list is short and specific: a transfer that arrives without a narration, a link paid twice by a buyer who was unsure, a refund attempted after the settlement cut-off, a counter device that loses its connection mid-scan, and a part payment that exceeds the outstanding balance.

Each is tested and documented, and the expected behaviour is shared with the accounts desk. Knowing what a stuck credit looks like is most of the training.

Send the collection methods in use today, the documents each one settles, the provider if one exists, and a sample of the statement finance works from. The sample usually explains more than a conversation about requirements.

Start with the payment gateway integration page for the national view, or read the payment gateway integration cost breakdown for the line items.