Money in, money out, and the ledger in between

Collections is the core of what we do. Payouts and virtual accounts exist because the same businesses that need to accept money usually need to send it somewhere afterwards, and buying that from a second provider means reconciling two systems by hand.

Primary product

Payment gateway

Cards, UPI, net banking and wallets behind one integration. Routing moves a failed transaction to a working path instead of returning an error to your customer.

For businesses selling online that want fewer abandoned checkouts and one reconciliation view across every payment method.

Payment gateway in detail

Cards

Credit and debit, with saved-card tokenisation

UPI

Intent, collect, and static or dynamic QR

Net banking

Major banks, with live availability checks

Wallets

The wallets your customers already hold

Payment links

Shareable links for invoices and one-off collection

Smart routing

Retry through an alternate acquirer on failure

Bulk payouts

Upload a file or call the API. Payouts go to bank accounts or UPI IDs, with a webhook on every state change so your ledger stays current without polling.

For teams paying vendors, partners, contractors or refunds in volume, who need an audit trail per transaction rather than a bank statement to unpick.

Bulk payouts in detail

Bulk file upload

CSV in, itemised result out, with per-row status

Payout API

REST endpoints with idempotency keys

UPI payouts

Pay to a UPI ID without collecting bank details

Scheduled runs

Recurring payouts for payroll and retainers

Webhooks

Callbacks on queued, processed, failed and reversed

Approval flows

Maker-checker before funds leave the account

Virtual accounts

Issue a unique virtual account or UPI ID per customer. Incoming money arrives already attributed, so matching payments to invoices stops being a manual job.

For businesses invoicing repeat customers — lending, education, B2B supply — where the hard part is not collecting money but knowing who sent it.

Virtual accounts in detail

Per-customer accounts

A unique account number for each payer

Auto-reconciliation

Inbound credits matched to the payer on arrival

Virtual UPI IDs

The same attribution model over UPI

Real-time notifications

Webhook the moment a credit lands

Ledger export

Statements and custom date-range exports

Sub-account structure

Separate lines for branches or business units

Together

Why these three belong on one platform

A business collecting through one provider and paying out through another has two ledgers, two reconciliation processes and two support relationships. The join between them is done by a person in finance with a spreadsheet.

On one platform, a collection and the payout it funds share a record shape, an export and a dashboard. That is the whole argument, and it is worth more than a few basis points on rate.

Developers

API principles, endpoints, webhooks and SDKs.

Security

Certifications, controls and how TrustPay handles data.

Tell us what you move, and we will quote it

Your volume, category, payment methods and settlement cycle. Four answers and you have a rate.

Talk to sales How pricing works