AI agents can already read invoices, chase vendors and reconcile books. The last step is still stuck: actually paying someone. In India that usually means a UPI or IMPS transfer in rupees, and most agent stacks have no clean way to do it.
This guide shows a pattern for letting an agent pay out in India from a USDT balance, without giving it a blank cheque.
Why this is hard today
- Cards work for buying things online, not for paying a contractor's bank account in Pune.
- Many teams hold operating funds in USDT, but the recipient wants INR in their bank account, often within minutes.
- An agent that can move money needs limits, approvals and an audit trail. Without them, nobody in finance will turn it on.
The four-step flow
- Quote. The agent asks for a quote: amount in INR, recipient, method (UPI or IMPS). It gets back a rate, the exact USDT debit including fees, and an expiry. Example: 50,000 INR at 95.00 INR per USDT, debit 531.98 USDT, valid for 15 seconds.
- Policy check. Before anything moves, the payout is checked against rules the business set: daily limit, allowed recipients, maximum single payout, and a threshold above which a human must approve. Within the rules, it goes ahead automatically. Above the threshold, it waits for an approver.
- Payout. The payout is sent over UPI or IMPS. The request carries an idempotency key, so if the agent retries after a timeout, the recipient is never paid twice.
- Receipt. The agent gets a final status with the bank reference number (UTR) and a webhook fires to your system. Finance sees who was paid, how much, at what rate and why.
What the agent actually calls
With an MCP server, the agent only needs three tools:
get_quote(amount=50000, currency="INR", recipient="ravi@upi")
request_payout(quote_id="q_8f2c", reason="Invoice #1042", idempotency_key="inv-1042")
get_payout_status(payout_id="po_51a7")
Notice what is missing: there is no "approve" tool. The agent can ask, but it cannot approve its own payout. Approval belongs to a person or to the rules, never to the agent.
Design rules worth copying
- Bind the approval to the exact quote: same recipient, amount and rate. If anything changes, the approval no longer applies.
- Keep the quote short-lived. A 15-second rate means nobody pays an old price.
- Make every payout traceable. Store the reason (invoice number, task ID) next to the bank reference.
- Return clear statuses: pending approval, processing, paid, failed, refunded. If a payout fails, the USDT goes back to the balance automatically.
Where this is useful
- Finance agents paying vendor invoices in India.
- Platforms paying freelancers, creators or annotators in rupees.
- Web3 teams paying contributors from a treasury held in USDT.
Try it
We're building this at Transavex as Agent Pay: payouts in local currency from a USDT balance, via API, bulk file or MCP, starting with India (UPI, IMPS) and Brazil (PIX). If you're building agents that need to pay people, we'd love to hear how you handle it today. Drop a comment below.
Top comments (2)
the missing approve tool is the load-bearing detail in this whole setup. an agent that can request but never approve turns the approval into a human checkpoint instead of a formality, and binding it to the exact quote rather than the recipient kills the swap-the-UPI-id-after-approval trick. does the 15-second quote expiry apply on the policy check too, or can a stale quote still pass if it was checked in time?
The approve step only counts if it binds to the exact payee and amount the human saw, not to 'payouts this month'.