India UPI acquiring · D0 settlement

UPI payments for India
native, intent, hosted

Titan Pay gives teams selling into India three UPI rails: hosted checkout, server-side native collect and mobile intent links, returning one callback format and one settlement file. Payments settle the same day (D0) in INR, callbacks arrive within 5 seconds, and failed orders retry three times. Start in sandbox, then agree channels and rates.

D0same-day settlement
60%hosted gateway success rate
70%native and intent success rate
UPI channel monitor Operational
UPIcollection
INRsettlement
D0batch
Works with
  • Google Pay
  • PhonePe
  • Paytm
  • BHIM
  • UPI
and every UPI-enabled bank app
Channels

Four parts of UPI acquiring

Sandbox first, then agree the rails you need, the rates and the settlement batch.

Hosted gateway

No front-end rewrite: send the buyer to a checkout URL. One integration covers intent links and collect fallback, with three-step retries.

Native collect

Server-initiated collect requests straight to the UPI rail. VPA checks and amount locks return in under 2 seconds, with status polling to a final state.

Intent wake-up

A upi:// link opens GPay, PhonePe, Paytm or BHIM. Desktop falls back to a dynamic QR, and the callback carries the UTR.

D0 settlement

Successful payments enter the same-day batch. Every settlement line matches a UTR, and a missing reference can be attached from the console.

Titan UPI ConsoleSandbox
Gatewayorders · retries · fallback
G
Nativecollect · VPA checks
C
Intentdeep link
I
SettlementD0 batch and UTRs
D
UPI Rails

Three rails, one merchant account

Rates, limits and settlement batches are agreed per rail; the integration guide states where each one fits.

  • Hosted gateway: Web and H5 jump straight to checkout, one link to change
  • Native collect: server-initiated, fits subscriptions and batch collection
  • Intent wake-up: opens an installed UPI app from yours, no VPA typing
  • Callbacks and settlement: all four final states notify, and the file matches UTRs line by line
Onboarding

From sandbox to production in four steps

Every step is confirmed in writing. Rates and limits follow the signed schedule, not a verbal promise.

Sandbox

Get a test key and run a ₹1 payment on all three rails. Callback logs and request bodies stay in the console.

Rates and channels

Rates, per-payment limits and settlement batches are confirmed in writing before integration starts.

Gradual launch

Start at 5% of live traffic, watch success rate and callback latency, then add 20% per day.

Settlement and on-call

The D0 settlement file is pushed daily. Telegram on-call answers integration questions within 2 hours.

Insights

UPI notes from the rails

Evergreen notes on checkout design, settlement and success rates. No news cycle, just what changes conversion.

Run a test payment before we talk terms

Tell us your use case, target market and monthly volume on Telegram. We send sandbox keys, the integration guide and a rate card. The sandbox is free and needs no contract.

Onboarding Telegram