How is this different from connecting Razorpay MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the Razorpay MCP API changes?

We track the Razorpay MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different Razorpay tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in Razorpay?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the Razorpay MCP server myself?

No. TrustGate connects to the Razorpay MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to Razorpay directly.

Connect Razorpay MCP to your AI agents, securely.

Q: Is Razorpay MCP secure?

The server itself exposes 45 tools, and some of them can write to your Razorpay account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches Razorpay.

One secured endpoint for every Razorpay call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try Razorpay MCP now

What your agents can ask once Razorpay MCP is connected.

Select the tools your AI agents can call

45 tools from the Razorpay MCP schema.

Showing 45 tools

fetch_paymentreadFetches payment details by ID.
fetch_all_paymentsreadFetches all payments with filtering and pagination.
fetch_payment_card_detailsreadFetches the card details used for a payment.
update_paymentwriteUpdates the notes field of a payment.
resend_otpwriteResends an OTP if the previous one was not received or expired.
capture_paymenthigh riskChanges a payment's status from authorized to captured, taking the funds.
initiate_paymenthigh riskInitiates a payment using a saved payment method with order and customer details.
submit_otphigh riskVerifies and submits an OTP to complete payment authentication.
fetch_payment_linkreadFetches the details of a payment link.
fetch_all_payment_linksreadFetches all payment links.
update_payment_linkwriteUpdates a standard payment link.
create_payment_linkhigh riskCreates a new standard payment link: a live, payable URL.
payment_link_upi_createhigh riskCreates a UPI payment link with a specified amount and additional options.
payment_link_notifyhigh riskSends or resends the notification for a payment link by SMS or email.
fetch_orderreadFetches an order by ID.
fetch_all_ordersreadFetches all orders.
fetch_order_paymentsreadFetches all payments for an order.
create_orderwriteCreates an order.
update_orderwriteUpdates an order.
fetch_refundreadFetches refund details by ID.
fetch_all_refundsreadFetches all refunds.
fetch_multiple_refunds_for_paymentreadFetches multiple refunds for a payment.
fetch_specific_refund_for_paymentreadFetches a specific refund for a payment.
update_refundwriteUpdates a refund's notes by ID.
create_refundhigh riskCreates a refund, returning money to the customer. Not available on the remote server.
fetch_qr_codereadFetches a QR code by ID.
fetch_all_qr_codesreadFetches all QR codes.
fetch_qr_codes_by_customer_idreadFetches QR codes by customer ID.
fetch_qr_codes_by_payment_idreadFetches QR codes by payment ID.
fetch_payments_for_qr_codereadFetches the payments made against a QR code.
create_qr_codewriteCreates a QR code that customers can pay against.
close_qr_codewriteCloses a QR code so it can no longer be paid. Not available on the remote server.
fetch_all_settlementsreadFetches all settlements.
fetch_settlement_with_idreadFetches settlement details by ID.
fetch_settlement_recon_detailsreadFetches the settlement reconciliation report.
fetch_all_instant_settlementsreadFetches all instant settlements.
fetch_instant_settlement_with_idreadFetches an instant settlement by ID.
create_instant_settlementhigh riskCreates an instant settlement, moving funds to the merchant's bank ahead of the normal schedule. Not available on the remote server.
fetch_all_payoutsreadFetches all payout details for an account number.
fetch_payout_with_idreadFetches a payout's details by its ID.
fetch_tokensreadGets all saved payment methods for a customer, by customer ID or contact number.
revoke_tokenhigh riskRevokes a customer's saved payment method, breaking any recurring mandate attached to it.
create_registration_linkhigh riskCreates a registration or auth link for subscription registration, setting up a recurring mandate. Not available on the remote server.
detect_stackreadDetects the project's language and framework for checkout integration.
integrate_razorpay_checkoutreadGenerates end-to-end Razorpay Standard Checkout integration code for supported frameworks.

What Razorpay MCP exposes

Razorpay MCP groups its 45 tools into 10 categories, each with a suggested starting policy.

All 45 tools as JSON, ready to paste.

Category	Covers	Access	Suggested policy
Payments	Fetching payments by ID or in bulk, expanded card details, updating notes, capturing an authorized payment, initiating a payment against a saved method, and resending and submitting OTPs	Read / Write	capture_payment, initiate_payment and submit_otp all move a payment forward against a real customer. fetch_payment_card_details returns card data, so restrict it separately from the other reads
QR Codes	Creating QR codes, fetching them by ID, customer or payment, listing them, listing their payments and closing one	Read / Write	A created QR code is a live payment instrument; close_qr_code is restricted on the remote server
Payment Links	Creating standard and UPI payment links, fetching one or all, updating a link and sending it to a customer by SMS or email	Read / Write	payment_link_notify reaches a real customer over SMS or email; creating a link produces a payable URL that can be shared anywhere
Refunds	Creating a refund, fetching one by ID or in bulk, updating refund notes, and fetching the refunds attached to a payment	Read / Write	create_refund returns money to a customer and is restricted on the remote server; the rest is read-only or notes-only
Settlements	All settlements and settlement details, the reconciliation report, and instant settlements with their listing and detail	Read / Write	create_instant_settlement moves funds to the merchant's bank ahead of schedule and is restricted on the remote server
Orders	Creating an order, fetching one by ID or in bulk, updating it and listing its payments	Read / Write	An order is the pre-payment record; creating one does not move money by itself
Payouts	Fetching all payouts by account number and a single payout by ID	Read	Read-only; payouts cannot be created through this server
Tokens	Listing a customer's saved payment methods by customer ID or contact number, and revoking one	Read / Write	fetch_tokens enumerates stored payment instruments by phone number; revoke_token destroys a customer's saved method and breaks any recurring mandate on it
Integration Helpers	Detecting the project's language and framework, and generating end-to-end Standard Checkout integration code	Read	Developer convenience tools that do not touch the merchant account
Registration Links	Creating a registration or auth link for subscription registration	Read / Write	Sets up a recurring mandate against a customer. Restricted on the remote server

Connect Razorpay MCP to your AI agent

Four steps, under ten minutes.

01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
03
Connect Razorpay
Find Razorpay in the tool list and connect it.
04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.

Permissions down to the single tool

You do not allow Razorpay MCP or block it. You allow the exact tools each agent can call, one by one.

Razorpay MCP	45 TOOLS AVAILABLE
Code review agent	4 tools, read only
Issue triage bot	9 tools
Platform team assistant	all 45 tools

Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
Default denyA tool you have not enabled is never exposed to the agent.
Approval on writesTools that change or delete things can require a human to confirm.

Is Razorpay MCP secure?

One endpoint instead of raw credentials. Every call is checked against policy and logged.

AI agentsConnect through your MCP client configuration.	NeuralTrustApply controls based on your configuration.	Razorpay MCP45 documented tools. Four are withheld from the hosted server and reachable only from a local install, which also supports a READ_ONLY mode and a TOOLSETS filter.
Coding assistants	Connection & credentialsper user	Payments8 tools
Internal copilots	Tool access policiesdeny by default	QR Codes7 tools
Workflow automations	Request & response inspectioninline	Payment Links6 tools
Compatible MCP clients	Activity monitoringalerts and logs	All other tools24 tools