Claude Razorpay connectorWhat Claude can do in your Razorpay account.
The Claude Razorpay connector exposes 25 tools. 24 read your merchant data, 0 write, and 1 is listed without any description. Below: what Claude looks up for you, what it cannot touch, and why Razorpay's own server list says more than the directory.
Verified Trustpilot reviews · AI, automation & growth agency
Why a finance or ops team would plug Razorpay into Claude
The Razorpay dashboard answers one question at a time, and each answer takes a few clicks and a filter. With the connector, you ask Claude where yesterday's settlement stands or which refunds are still pending for a customer, and it looks the records up itself, then answers in a sentence instead of a table you have to read.
Reconcile without the export dance. fetch_all_settlements and fetch_settlement_recon_details bring back settlements and the reconciliation report, so Claude can line up what was paid out against what you expected.
Answer a customer in one go. A buyer says they paid twice. fetch_order_payments lists every payment on the order, and fetch_multiple_refunds_for_payment shows what was already refunded.
Check the counter QR codes. fetch_all_qr_codes and fetch_payments_for_qr_code tell you which codes are in use and what came through each.
Now the part the sheet does not say out loud. By default, everything listed here reads: no tool on the directory sheet captures a payment, issues a refund or creates a link. Razorpay's own server documentation does describe writing tools, but the Claude directory does not list them, and the box further down lays out that gap. Nothing runs on its own either: no tool fires when a payment lands or a refund settles. For that kind of background job, an automation tool fits better, a different trade, like our Razorpay Make integration. The Integrations hub lists the rest.
Five words before you plug it in
The vocabulary you will meet on the way.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named job the connector opens to Claude. Claude picks the ones it needs mid-answer; the directory sheet lists them by name.
- Authorization
- Razorpay's own sign-in screen, where you hand Claude the access it will use afterwards. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Razorpay.
Connect Razorpay to Claude in three steps
- 01
Find Razorpay in Claude
In Claude's settings, open Customize, then Connectors, and look for Razorpay. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first; then each member connects on their own.
- 02
Start the connection
Click Connect on its row and sign in to your Razorpay merchant account in the window Razorpay opens. If the link breaks later, hit Disconnect and connect again from scratch.
- 03
Read the authorization screen
Before you accept, read what the screen asks for. It belongs to Razorpay, not to Claude, and it decides what the access covers. That access can also be withdrawn later from the Razorpay side.
The 25 tools of the Claude Razorpay connector
Razorpay gives Claude 25 tools: 24 that read your account, 0 that change something in it, and 1 no official source describes.
Two groups: what Claude reads, and one tool the sources say nothing about. Names stay exactly as Claude shows them, in English.
- 24 read
- 1 not documented
What Claude reads (24)
24 toolsTwenty-four lookups across payments, orders, links, QR codes, refunds, settlements and payouts. None changes your account.
fetch_payment
Pulls the details of one payment from its ID, so Claude can answer about it without a trip to the dashboard.
fetch_all_payments
Returns your payments with filtering and pagination, which lets Claude scan a period rather than a single record.
fetch_payment_card_details
Shows the details of the card behind a given payment.
fetch_order
Brings back one order from its ID.
fetch_all_orders
Lists your orders so Claude can go through them in bulk.
fetch_order_payments
Lists every payment attached to one order, so Claude can show you whether a basket was paid once, twice or not at all.
fetch_payment_link
Opens a single payment link and reports what Razorpay holds on it.
fetch_all_payment_links
Lists all the payment links on your account.
fetch_qr_code
Looks up a single QR code from its ID and reports what Razorpay has on record for it.
fetch_all_qr_codes
Returns every QR code on the account.
fetch_qr_codes_by_customer_id
Finds the QR codes tied to a given customer ID.
fetch_qr_codes_by_payment_id
Works back from a payment ID to the QR code it came through.
fetch_payments_for_qr_code
Lists the payments received through one QR code, which turns a sticker on a counter into a readable sales history.
fetch_refund
Gives the status and details of one refund from its ID.
fetch_all_refunds
Brings back every refund on the account, so Claude can total them or spot unusual ones across a period.
fetch_multiple_refunds_for_payment
Lists every refund made against a single payment, which matters when a purchase was refunded in several parts.
fetch_specific_refund_for_payment
Retrieves one precise refund tied to a given payment, rather than the whole list.
fetch_settlement_with_id
Shows what is inside one settlement, looked up by its ID.
fetch_all_settlements
Lists all your settlements with the details Razorpay keeps on each, so Claude can walk through a quarter in one go.
fetch_instant_settlement_with_id
Returns one instant settlement from its ID.
fetch_all_instant_settlements
Lists every instant settlement on the account.
fetch_settlement_recon_details
Fetches the settlement reconciliation report, the breakdown finance needs to tie deposits to transactions.
fetch_all_payouts
Per payout, you get its details along with an account number, according to Razorpay's documentation.
fetch_tokens
Lists the payment methods a customer has saved, found by customer ID or contact number.
Undocumented (1)
1 toolThe directory lists this name and nothing else. No official text says what it does, and we will not guess from its name.
fetch_payout_with_id
This name appears in the directory's tool list, and that is all. Razorpay's server documentation does not describe it under this name, and no Claude page does either, so the page will not say more.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request shows up in the conversation, at the moment it matters.
With Razorpay as listed today, that default rarely comes up, since every documented tool reads. The rest of the rule still matters. On Team and Enterprise, owners decide whether a member may let some actions through without being asked. They can also cap what a connector may do for the whole organization, keeping reading open and closing writing, and nobody gets around that from their own account. Claude works with your rights, nothing more.
Which plans include it
Of the 819 sheets in the official directory, none shows availability by plan. The per-connector answer is published nowhere, a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members can connect. For the current state, open the Razorpay sheet in the directory from your own account.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing starts when a payment lands or a settlement clears.
This connector is documented only by its publisher: neither Claude's help center nor Anthropic's developer docs cover it. By default, its sheet exposes only reading, which is an observed floor, not a guarantee, since an administrator can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic says on every sheet that it does not decide which tools a publisher exposes.
Can Claude create or change payments through the Razorpay connector?
- Claude directory sheet ↗September 30, 202625 tools, all lookups: payments, orders, links, QR codes, refunds, settlements, payouts and saved methods.
- Razorpay's official server README (GitHub) ↗read September 30, 2026Razorpay lists writing tools too, such as capturing a payment, creating a payment link or revoking a saved method, marked as supported on its hosted server.
What this page followsRazorpay's server announces writing tools that the directory sheet does not show. This page describes what the sheet shows, which is reading. What your own account displays after connecting is what counts, and any writing tool that shows up there falls under the general approval rule.
Need help connecting Razorpay to Claude?
A person reads every message.
