Commerce & Payments · Integration
Razorpay
Add Razorpay to your product for your customers, and give your AI agents governed access to it.
Razorpay is built for Indian payments, which means the methods matter more than they do elsewhere: UPI, netbanking, cards and wallets behave differently, and settlement and refund timelines vary by method rather than being uniform. An integration that treats a payment as method-agnostic will give customers wrong answers about when money arrives. Orders and payments are separate objects and the mapping between them is not always one to one, particularly with partial captures. Webhooks carry the state changes worth acting on, and they need signature verification rather than trust. fastn scopes each customer's keys and verifies the events before they reach your product.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Razorpay account so payment state appears inside your product.
Read payments with their method, since settlement and refund behaviour depend on it.
Reconcile orders against payments, including partial captures.
React to a captured or failed payment with the event signature already verified.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which payments failed and groups them by method.
An agent issues a refund within governed permissions, with the action audited per tenant.
An agent explains when funds for a given payment are expected to settle.
Example prompt
Which payments failed today, and which method were they attempted on?
Set up Razorpay in 4 steps
- 01Enable the Razorpay connector from your fastn dashboard.
- 02Have each customer authorise their own Razorpay account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Razorpay integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Razorpay integration without building it. Your customers connect their own Razorpay account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Razorpay update is not your on-call problem.
- One integration serves your product and your agents. The same governed Razorpay connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Stripe
Paddle
PayPalOften used alongside
Tools the same teams tend to run next to Razorpay, across other categories.
NetSuite
Notion
Box
DocusignRazorpay integration FAQ
How do I add a Razorpay integration to my product?
Enable the Razorpay connector in your fastn dashboard, then let each customer authenticate their own Razorpay account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Razorpay client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Razorpay account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Razorpay account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Razorpay integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which payments failed and groups them by method.
Who maintains the Razorpay integration?
fastn does. When Razorpay changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Razorpay integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Razorpay integration?
A common starting point: let a customer connect their own Razorpay account so payment state appears inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Razorpay integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Razorpay does not change your per-connector cost. You can start free with 3 connected accounts.
Add Razorpay to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.