How Razorpay fits UCP and ACP
The payment flow is the same whether the session originates from Google AI Mode (UCP) or ChatGPT (ACP) — your backend calls Razorpay after the protocol layer confirms the purchase:confirm_purchase tool fires, your backend triggers a Razorpay Agentic Payment within the customer’s authorised limit — no additional PIN required.
End-to-end integration
Sign up for access and check eligibility
Razorpay Agentic Payments is currently available to Indian merchants through an early-access programme.
- Confirm your use case: in-merchant app assistants or conversational commerce (for example, a grocery app with an AI assistant)
- Sign up at razorpay.com/m/agentic-payments
- Review Razorpay’s API documentation once access is granted
- Ensure your product feed and checkout endpoints are agent-ready — see Feed Specs and UCP Getting Started
Implement one-time authorisation (UPI mandate)
When a customer opts into AI-assisted shopping, prompt them to authorise a spending limit. This creates a UPI mandate that your backend stores and reuses for subsequent AI-initiated payments.Surface clear consent language to the user at this step:
- What they are authorising
- The maximum spend limit
- How to view and revoke the mandate
Execute payment in your checkout handler
When the AI initiates a payment within the authorised scope, look up the customer’s mandate and call Razorpay:
Payment token flow
The payment token (mandate ID) ties the customer to their authorised spending limit across sessions. Store it securely server-side and never expose it to the client.
When a mandate is revoked or expires, clear it from your database and prompt the customer to re-authorise the next time they use AI checkout.
| Token field | Where it comes from | How long it lasts |
|---|---|---|
mandate.id | Razorpay mandate creation response | Until the customer revokes it |
payment.id | Each individual payment execution | Per-transaction reference |
Trust, compliance, and India-specific considerations
Razorpay is an RBI-authorised payment aggregator. Your integration must comply with both Razorpay’s terms and RBI guidelines for payment aggregators and UPI:
- Surface clear consent and limit controls to the user at authorisation time
- Provide a real-time view of spending against the limit
- Allow instant limit changes and revocation
- Follow Razorpay’s and RBI’s guidelines for payment aggregators and UPI
₹5,000 = 500000 paise. Do not mix decimal rupee values with the paise field.Test mode setup
Test the full authorisation and payment flow in Razorpay’s sandbox before going live:Use Razorpay’s test UPI IDs (Go live per Razorpay’s launch process, then monitor these metrics:
success@razorpay, failure@razorpay) to simulate authorisation and payment outcomes. Run a full Asva Readiness Score after your sandbox integration is complete:- Authorisation rate — percentage of customers who set a mandate
- Payment success rate — percentage of AI-initiated payments that complete
- Average time to complete — target under 3 seconds
Use cases
| Use case | Example |
|---|---|
| Grocery ordering | ”Order my usual basket” via a grocery app’s AI assistant |
| Subscription reorder | ”Reorder my protein powder” — payment executes within mandate |
| Event ticketing | ”Book 2 tickets for Friday” — single-tap confirmation |
| Food delivery | In-app AI assistant completes reorder without PIN |
Related
- ACP Getting Started — ACP endpoints for ChatGPT
- UCP Checkout and Payments — UCP payment integration
- Feed Specs — product feed requirements
- Razorpay Agentic Payments (official)