Integrations
Connect your agent to the places it buys from
Connector categories
What your agent will be able to buy
Nothing is live yet. Next means it works in our sandbox or is being built now; Planned means a later wave.
Groceries
Weekly shopping from grocery apps on ONDC, inside a household budget.
- Sandbox simulator
- Next
- Real merchants
- Planned
Cab booking
Book a ride for the airport run; fares above the cap wait for you.
- Sandbox simulator
- Next
- Real merchants
- Planned
Food delivery
Order lunch for the team within a per-person limit.
- Sandbox simulator
- Next
- Real merchants
- Planned
Cloud and software bills
Bills like your hosting provider's: watched, budgeted and flagged before they cross a limit.
- Sandbox simulator
- Next
- Real merchants
- Planned
Online shopping
Shops that accept agent checkout over MCP, ACP or AP2.
- Sandbox simulator
- Next
- Real merchants
- Planned
Forex and travel
Forex for a trip and corporate travel with an AD Category-II partner's dealer.
- Sandbox simulator
- Next
- Real merchants
- Planned
Local shops and D2C brands
Any shop that adds TatvaPay agent checkout and gets paid by agents.
- Sandbox simulator
- Next
- Real merchants
- Planned
Paid APIs
Pay-per-call APIs that charge agents with an HTTP 402 challenge.
- Sandbox simulator
- Next
- Real merchants
- Planned
How payment works
How your agent pays, by kind of merchant
- Next
Type A: The shop uses TatvaPay checkout
For example: A grocery store, a local bakery, a seller on ONDC
Your agent pays at the shop's TatvaPay checkout. The money is debited from your bank under your mandate, through a licensed payment aggregator, and you get a signed receipt.
- Planned
Type B: The shop uses another payment company
For example: A store whose payments run elsewhere
Either the shop adds TatvaPay agent checkout next to what it has, or the payment goes through a second payment aggregator we route to. Your mandate and receipt work the same way.
- Next
Type C: The company bills you itself and has no agent API
For example: Cloud hosting, software subscriptions, many apps
You keep paying them by your own AutoPay. Our agent watches the bills, keeps them inside your budget, asks you before a limit is crossed and helps raise a dispute. It never logs in as you.
- Planned
Type D: Any UPI merchant
For example: Any shop with a UPI QR
When NPCI's agent payment standard is final, agents will be able to pay any UPI merchant within a mandate.
Spend firewall
One gate in front of every connector
- Next
Every spend is checked
Actions that can spend money must pass your mandate, the rules and any approval first. - Next
Every spend is receipted
What was bought, under which mandate, approved by whom: in one signed receipt. - Next
Agents say who they are
Each request carries a signed "I am an AI agent" header the merchant can verify. - Next
No scraping, no logging in as you
We connect only where a merchant offers an API or MCP server and agrees.
Underneath
Where the money actually moves
- Next
Sandbox rails
Fake bank rails and two simulated payment providers, for building and testing
- Next
UPI, cards and netbanking
Through a licensed payment aggregator; first planned integration: Razorpay (test mode now)
- Next
UPI AutoPay and e-mandates
Recurring mandates through the same payment aggregator
- Planned
A second payment aggregator
Routing and fallback between two providers
- Next
Forex and LRS remittances
Through an AD Category-II partner; simulated in the sandbox
- Planned
UPI Reserve Pay and NPCI's agent standard
When they are available to us
TatvaPay is a technology service provider. It holds no RBI licence and never holds customers' funds: payments run on licensed payment aggregators (first planned integration: Razorpay) and forex through an AD Category-II partner.
Building agents or a store? See the developer overview
Run a shop or a service agents should buy from?
Add agent checkout, or tell us about your API, and we will build a connector with you.