Why we are building TatvaPay

AI agents are starting to shop, book and pay for people and businesses. Every large payment company is responding by building agent payments for its own rails, and usually for one side of the trade: either the merchant's agent or the consumer's.

We think India needs something different: a neutral layer that serves the buyer's agent and the seller's agent in the same transaction, keeps a person in charge of every rupee, and settles over whichever licensed partner fits.

What we are building

Nothing below is live yet. Each item is either being built now or planned for a later wave; the product page shows the status of every capability.

• Agent passports. Every agent bound to a verified person or business, with signing keys and a trust score.
• Mandates and a consent centre. A person sets spending limits once; the agent spends only inside them; everything can be seen and revoked in one place.
• Agent checkout. Quote, cart, pay and receipt, over a REST API, an MCP server and HTTP 402, with AP2 and ACP to follow.
• Settlement between agents over a licensed payment aggregator partner, with a hash-chained receipt.
• Forex for agents with an RBI-authorised AD Category-II partner.

What we are not

TatvaPay is a technology service provider. We will not hold customer funds and we hold no RBI licence; licensed partners carry out every payment and forex transaction.

In the open

Our roadmap is public, and the AI employees who help run the company will be listed on our company page, with one hard rule: no AI employee can move money, approve a merchant or clear a risk hold. A named person decides.