Skip to content

Payments infrastructure, built in India

Accept payments,
send payouts, reconcile automatically

Cards, UPI, net banking and wallets through one integration, with routing that retries a recoverable failure instead of losing the checkout. Payouts and virtual accounts when you need the money to go the other way.

UPICardsNet bankingWallets
CertifiedPCI DSSv4.0ISO/IEC27001:2022

Collections

One integration, every method

Pay-in
  • UPI

    Intent, collect and QR

    Live
  • Cards

    Credit, debit, tokenised

    Live
  • Net banking

    Availability checked live

    Live

A recoverable failure is retried through an alternate acquirer before your customer ever sees an error.

PCI DSSv4.0
ISO/IEC27001:2022
99.94%Uptime

What we do

Three things, done properly

Money in, money out, and knowing which is which. Most businesses need all three and end up buying them from three different providers.

Primary

Payment gateway

Accept payments across every method your customers already use.

  • Cards
  • UPI
  • Net banking
How it works

Bulk payouts

Send money to many recipients at once, by file or by API.

  • Bulk file upload
  • Payout API
  • UPI payouts
How it works

Virtual accounts

Give every customer their own account number, and reconcile automatically.

  • Per-customer accounts
  • Auto-reconciliation
  • Virtual UPI IDs
How it works
Everything included

What every account gets

No feature tiers, no add-on pricing, nothing held back until you upgrade. The rate is the only thing that varies.

UPI collect & intent
UPI QR, static and dynamic
Cards, credit and debit
Net banking
Payment links
Virtual accounts
Bulk payouts, file or API
Merchant dashboard
Webhooks and reason codes

1,260+

Businesses onboarded

Across eight categories

₹63.8 Cr

Processed monthly

Collections and payouts combined

99.94%

Platform uptime

Rolling twelve months

T+1

Standard settlement

Faster cycles on assessment

In practice

UPI is most of Indian checkout now

Which is fine until your provider treats it as one option among four. Method mix decides where routing effort is worth spending, and for most businesses here that is UPI first and cards second.

How customers pay
UPI58.2%
Cards24.6%
Net banking11.4%
Wallets5.8%

Share of transaction count across all businesses on the platform.

94.6%

Transaction success rate

After routing retries

24 hrs

Typical time to go live

Once documents are in

120+

Payment methods

Cards, UPI, banks and wallets

< 2 hrs

First support response

Business hours, median

The path of a payment

Five steps, and only one of them is visible to your customer

  1. 01

    Customer pays

    UPI, card, net banking or wallet

  2. 02

    We route it

    To the acquirer most likely to succeed

  3. 03

    Failures retry

    Alternate path before an error is shown

  4. 04

    You are notified

    Signed webhook on every state change

  5. 05

    Funds settle

    To your account on your agreed cycle

Developer friendly

Integrate once,
then stop thinking about it

One integration covers collections, payouts and virtual accounts. Most teams have a payment moving in sandbox on day one.

  • REST APIs with idempotency keys
  • Sandbox that matches production
  • Signed webhooks, no polling
  • SDKs for Node, Python, PHP, Java
  • Reason codes on every failure
POST /v1/payments200 OK
{  "merchant_id": "mrc_TP4821",  "amount": 250000,          // paise  "currency": "INR",  "method": "UPI",  "status": "captured",  "attempts": 2                // retried once}

Today's overview

Transactions

18,432

+11.2%

Total volume

₹2,13,40,880

+6.4%

Transaction volume across twelve hourly buckets today
00:0012:0023:00

Security

Handling money is a licence to be paranoid

Payments infrastructure fails in expensive, public ways. These are the controls that keep a bad afternoon from becoming a bad quarter.

Encryption in transit and at rest

TLS on every connection, AES-256 for stored data.

Tokenisation

Card numbers are replaced with tokens. Raw PANs never reach your servers.

Fraud monitoring

Velocity checks, blocklists and anomaly rules applied per transaction.

Two-person approval

Maker-checker on payouts, so a single credential cannot move funds.

Full audit trail

Every transaction, retry and state change is recorded and exportable.

Isolated environments

Sandbox runs the same API surface as production, with no live funds.

CertifiedPCI DSSISO/IEC

Built for businesses across industries

Same underlying problem in eight different shapes — more transactions than a person can match by hand.

Questions

The things people ask before signing

If yours isn't here, ask us directly and you'll get a straight answer.

What do I need to open an account?

Business registration documents, PAN, GST registration where applicable, a bank account in the business name, and KYC for the directors or proprietors. Onboarding time depends on how quickly documents come back and how your business category is assessed.

Which payment methods are supported?

Cards, UPI, net banking and wallets for collections. Bank transfers and UPI for payouts. All of it sits behind one integration and one dashboard.

How does pricing work?

Pricing is quoted per business rather than published as fixed tiers, because the rate depends on your monthly volume, business category, the payment methods you enable, and your settlement cycle. Tell us those four things and you get a rate.

When do I get settled?

Settlement runs on a standard cycle for most business categories, with faster cycles available depending on risk assessment and volume. Your confirmed cycle is written into your agreement rather than left to change without notice.

Can I send payouts without building an integration?

Yes. Upload a file from the dashboard and payouts run without a line of code. The API exists for when you want payouts triggered by your own systems instead of a person.

What happens when a payment fails?

Routing retries through an alternate path where one is available, so a single acquirer outage does not become a failed checkout. Anything that still fails is reported with a reason code, not just a generic error.

Is there a sandbox?

Yes. The sandbox exposes the same API surface as production with no live funds, so you can build and test the full flow before going live.

Who should not use TrustPay?

If you take a handful of payments a month, a payment link from any provider will serve you just as well and cost less to set up. This platform earns its keep when you are running volume, paying out to many recipients, or reconciling more transactions than a person can match by hand. We will tell you if that is not you.

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.