USDT to INR via UPI
The honest, regulator-aware playbook for sending USDT into India — how UPI handles the local leg, what the RBI requires, why some payouts bounce, and what it actually costs versus a SWIFT wire.
TL;DR
To send USDT to India, the recipient gets Indian rupees credited to their bank account through UPI — the country’s instant payment rail — typically within minutes. DPT charges 0.1%–0.5% on the send amount and a small flat network fee, with mid-market FX locked for 10 minutes. The constraints are not in the rail (UPI runs 24/7 with sub-minute settlement); they’re regulatory: India’s RBI requires the inbound side to be processed by a licensed Payment Aggregator – Cross-Border (PA-CB) entity, with FEMA purpose codes attached, and the sender’s annual outflow may be capped under LRS rules if they’re an Indian resident sending out.
India Is the Largest Stablecoin Off-Ramp Market
India receives roughly $125 billion in remittances annually — more than any other country. The IT services industry generates additional flows from US/EU clients to Indian freelancers and contractors. UPI processes over 16 billion transactions per month, by far the highest-volume real-time payment system in the world.
Stablecoin off-ramps into INR through UPI have grown sharply since 2023, driven by the cost gap between SWIFT wires (1.5%–4% all-in for small amounts) and direct stablecoin-to-UPI settlements (0.1%–0.5% on transparent providers). The cap on this growth is regulatory clarity, not technology — UPI has always supported the speed.
How a USDT-to-UPI Payout Actually Settles
The sender holds USDT on TRON, Ethereum, or Solana. The recipient gets INR in their bank account via UPI. The path between them runs through a licensed Indian payment aggregator on the off-ramp side.
Sender selects India + UPI in the DPT app
Choose India as the destination, UPI as the rail, and enter the recipient’s UPI ID (e.g. recipient@okhdfcbank, recipient@ybl, recipient@paytm) or their full bank account number plus IFSC code if they prefer direct bank credit.
Source asset and chain selection
Pick USDT (or USDC) and the chain. For India remittance flows, USDT on TRON is the default — recipient-side exchanges and aggregators have the deepest TRC-20 liquidity, and the network fee is roughly $1. USDT on Solana is a strong alternative if your wallet supports it. ERC-20 works but the gas cost adds noticeable overhead on small transfers. See USDT TRC-20 vs ERC-20 vs Solana.
Quote lock — FX, fee, and INR amount
DPT quotes the mid-market USDT/INR rate (sourced from interbank FX), the provider fee (0.1%–0.5%), the network fee for the chosen chain, and the final INR amount the recipient will see. The quote is locked for 10 minutes.
On-chain settlement and FX execution
On confirm, USDT moves on-chain to the settlement wallet. The provider’s Indian PA-CB partner sells the USDT into INR at the locked rate and prepares the UPI push.
UPI push and recipient credit
The PA-CB initiates the UPI credit. NPCI routes the payment to the recipient’s bank, which credits the account and pushes a notification through the recipient’s UPI app. Typical end-to-end time from confirmation to credit is under five minutes.
The RBI PA-PG Framework — What Actually Governs This
India’s Reserve Bank regulates the inbound side of cross-border payments through the Payment Aggregator – Cross-Border (PA-CB) framework. Any entity that processes inbound money for credit to Indian beneficiaries must either hold a PA-CB authorisation directly or route through one that does.
For a stablecoin payout into INR, this means the on-chain leg can be conducted by a foreign provider (DPT), but the conversion-and-settlement leg into the Indian banking system must be performed by a PA-CB-authorised partner. DPT routes through such partners; the result for the sender is identical to any other stablecoin payout, but the regulatory chain on the Indian side is what makes the UPI credit legally possible.
Two constraints follow from this framework that affect what you can do on the corridor:
- Purpose code attachment: FEMA requires every inbound foreign-currency credit to be classified under a purpose code (P0103 for personal remittance, P0801 for IT/ITES services, P0205 for software exports, etc.). The provider attaches this in the background based on the sender’s declared reason.
- Beneficiary-side reporting: Inbound credits above certain thresholds may trigger Form 15CA/15CB filing requirements for the recipient at year-end, depending on their tax status.
LRS — Only Relevant If You’re an Indian Resident Sending Out
The Liberalised Remittance Scheme (LRS) caps how much an Indian resident can send out of India each financial year — currently $250,000 per resident — and requires the outflow to be reported and tagged with a purpose code. It does not apply to non-resident senders or to inbound payouts; if you’re outside India sending USDT into India, LRS does not apply to you.
LRS becomes relevant in the reverse case: an Indian resident wanting to send USDT or USDC out to a foreign recipient. That outflow counts toward the $250k annual ceiling and follows the same purpose-code framework.
What This Costs vs SWIFT Wire and Wise
A common scenario: a US-based client paying an Indian freelance contractor $1,000 monthly. Modelled against the three common alternatives:
| Method | Provider fee | FX rate vs mid-market | INR delivered (approx) | Speed |
|---|---|---|---|---|
| DPT (USDT TRON → UPI) | approx $4.00 (0.4%) + $1 network | Mid-market | approx ₹83,931 | Minutes |
| Wise (USD → INR, UPI receive) | approx $6.00 | Mid-market | approx ₹83,761 | Hours to 1 day |
| SWIFT wire (US bank → Indian bank) | $30–$45 + correspondent lift | 1.5%–3% retail margin | approx ₹81,000 | 2–5 business days |
DPT and Wise are within $2 of each other on a $1,000 transfer — both transparent, both at mid-market FX. SWIFT is the outlier: $30–$45 in explicit fees plus 1.5%–3% baked into the bank’s retail FX rate, plus correspondent lifting fees that often get deducted before the credit lands. For monthly contractor payments, the difference compounds to thousands of rupees per year.
Note on numbers
Illustrative values at a USD/INR mid-market rate near 84.35. Actual rates fluctuate. The structural pattern — transparent providers within a few dollars, SWIFT $20–$50 more expensive — has been stable across multiple snapshots.
Why Some India Payouts Bounce
The UPI rail itself is exceptionally reliable. Most rejected India payouts trace back to one of a handful of recoverable issues at the sender’s input or the recipient’s bank.
Common India-corridor reject reasons
- UPI ID typo: A single wrong character in
recipient@okhdfcbanksends the credit to the wrong handle (rejected) or the wrong person (irreversible). DPT runs a UPI ID validation lookup before letting you confirm. - Beneficiary name mismatch: Under PA-CB rules the inbound credit must match the registered name on the bank account. A nickname or initial-only name causes the partner bank to reject the credit, and the funds reverse.
- Purpose code mismatch: If you declare “remittance” but the recipient’s tax status or transaction history suggests business income, the PA-CB partner may flag the credit for review and request clarification before releasing.
- Receiving bank’s UPI down: Some smaller cooperative banks experience UPI outages. The PA-CB partner usually retries on the next available NPCI window, but the credit may take an extra few hours.
- Recipient account dormant or frozen: A bank account inactive for over 24 months, or one under regulatory hold, will reject the credit.
- Daily inbound aggregate limit at the recipient bank: Some banks impose conservative daily limits on aggregate inbound credits per account; very large transfers may be partially credited and the remainder reversed.
Failed payouts return the stablecoin to your DPT account within 1–2 business days, minus the network fee. The reason is surfaced on the transaction detail screen.
Who This Setup Is Best For
US/EU clients paying Indian freelancers
The cleanest path for $500–$5,000 monthly contractor payments. Skip SWIFT entirely; the contractor receives INR in UPI within minutes and you save $30–$50 per transfer.
NRIs sending family remittances
Mid-market FX and 0.1%–0.5% provider fee comfortably beats most legacy NRI remittance services on small-to-mid amounts. UPI lets the family receive without needing to visit a bank branch.
SMEs paying Indian software vendors
For recurring B2B IT services payments above $10k, the savings vs SWIFT compound quickly. PA-CB partner attaches the appropriate purpose code (P0801 for IT/ITES) to keep the inbound side clean.
Crypto-native earners
If you’re already paid in USDC or USDT for work — DAO contributions, on-chain consulting, content royalties — sending part of it directly to UPI for living expenses is faster and cheaper than going via an exchange off-ramp.
Send your first USDT payout to India
DPT supports UPI ID and direct bank account+IFSC for INR payouts. Mid-market FX, 0.1%–0.5% provider fee, locked for 10 minutes. PA-CB-routed for clean compliance on the Indian side.
Frequently Asked Questions
Can the recipient receive USDT directly into UPI?
No — UPI moves Indian rupees, not crypto. The conversion happens on the off-ramp side: USDT is sold for INR by the PA-CB partner, and INR is pushed to the recipient’s UPI ID or bank account. The recipient sees a standard INR credit.
Does the recipient need a crypto wallet or KYC?
No on both counts. The recipient just needs a UPI-enabled bank account or a UPI ID. They receive INR exactly the way they receive any other UPI credit. Their bank’s KYC remains the only verification layer they ever interact with.
Which UPI handle providers does DPT support?
All major NPCI-registered handle providers — bank-issued (@okhdfcbank, @okicici, @oksbi, @okaxis, @ybl, @paytm, @upi, @ibl, @apl, etc.) and PSP-issued. If your recipient’s UPI ID is valid and active, DPT can credit it.
Are there transfer limits per transaction?
UPI’s per-transaction limit is set per bank, typically ₹100,000 for personal accounts (₹500,000 for some specific use cases like education or healthcare). For larger amounts, splitting into multiple UPI transactions or using direct bank account credit (NEFT/RTGS via the PA-CB partner) is usually the cleanest path.
How does the recipient’s tax exposure look?
Inbound INR credits are treated like any other foreign remittance for income-tax purposes. If the inflow represents business or professional income (freelance work, contractor invoicing), the recipient declares it under their normal business income. If it’s a personal remittance from an NRI family member, it’s typically tax-exempt up to the standard limits. Recipients above the Form 15CA/15CB threshold should consult their CA. We don’t write tax advice — read the general crypto tax guide for context.
Can I send USDC instead of USDT?
Yes. USDC is fully supported on the IN corridor — pick USDC at the source asset step and choose your chain (Base, Solana, or Ethereum). USDT on TRON tends to dominate India remittance flows for historical liquidity reasons, but USDC pricing on DPT is identical, and Circle’s transparency profile is preferred by some senders.
Why do you require the recipient’s name to match the bank account?
It’s not a DPT requirement — it’s enforced by the PA-CB framework and the receiving bank. Inbound foreign credits to Indian bank accounts must match the registered KYC name; mismatches cause the bank to reject and reverse. We surface the name field at input time so the issue gets caught before the on-chain leg fires.