Independent research & analysis on payment security Search
paymentsecuritypros.com Payment Security Insights
Emerging Threats & Trends

Razorpay vs Cashfree MCP Servers: AI-Assisted Payment Investigation and Refund Approval Boundaries

A support analyst gets a message: “I paid but my order still says unpaid.” A finance colleague asks why yesterday’s settlement looks short. Both now have an AI assistant that can talk to the payment gateway through the Model Context Protocol (MCP). That is genuinely useful: the assistant can pull the payment attempts, refund history and settlement records in seconds. It also raises a sharper question than “which tool is smarter”: what is the assistant allowed to change?

This guide compares Razorpay’s and Cashfree’s MCP servers on what an assistant can inspect, what it can change, how each is deployed and authenticated, and the approval controls a merchant must add before connecting either to a live account. It is about merchant operations, not customer-facing agentic shopping or webhook design (see our webhook comparison).

Facts come from Razorpay’s MCP documentation and tool table and Cashfree’s MCP documentation, checked on 12 November 2026. Tool lists change often; check the current list before you configure access.

Quick answer: Both providers offer MCP servers that let AI clients query payments and settlements and perform some actions. Razorpay offers a hosted Remote server and a self-hosted Local server; its tool table currently marks create_refund, close_qr_code, create_instant_settlement and create_registration_link as Local-only, while Remote supports reads plus actions such as capturing payments, creating payment links and updating notes. Razorpay also documents a read-only mode and toolset selection. Cashfree offers a Cashfree-managed remote server authenticated through OAuth, requiring owner-level access, with transaction search, settlement, report and payment gateway tools, including create_refund. Neither MCP connection is “read-only by default” in every setup, so the merchant must define approval boundaries before going live.

Key takeaways

  • MCP connects an assistant to provider tools; it does not grant authority to move money. Your configuration and approval process do.
  • Razorpay: Remote (hosted) and Local (self-hosted) deployments; refunds via create_refund are Local-only in the current tool table; a READ_ONLY flag and TOOLSETS selection are documented.
  • Cashfree: a managed remote server over HTTPS with OAuth; requires an active merchant account with owner-level access; its tool list includes create_refund.
  • Investigations should start read-only with exact order and payment IDs, and treat the assistant’s summary as an interpretation until checked against source records.
  • Require human approval for any refund, capture or settlement action, and retain operation IDs.

What is a payment MCP server, and what is it not?

The Model Context Protocol is a standard way for AI clients such as Claude, ChatGPT, Cursor or VS Code to call tools exposed by a server. A payment MCP server wraps the provider’s APIs: fetch a payment, search orders, create a payment link, issue a refund. The assistant decides which tool to call based on the conversation, and the server executes it with whatever credentials it holds.

Two consequences follow. First, the assistant can only do what the exposed tools and credentials allow. Second, if a write tool is exposed with live credentials, the assistant can perform that action when asked or when it misreads a request. MCP is plumbing, not policy.

How do deployment and access compare?

Item Razorpay MCP Cashfree MCP
Deployment Remote (hosted by Razorpay, quick setup via npx) and Local (self-hosted with Docker) Cashfree-managed remote server over HTTPS
Requirements Active Razorpay account with API access; Node.js for Remote, Docker for Local Active Cashfree merchant account with owner-level access; eligible AI client
Authentication API keys from the Razorpay Dashboard; OAuth documented for Remote OAuth handshake via your Cashfree account; disconnecting a client revokes its refresh token
AI clients named Claude Desktop, Cursor, Visual Studio Code Claude (connectors directory), ChatGPT, Cursor, Claude Code
Tool scope controls READ_ONLY mode; TOOLSETS selection (configured on the server) Not stated on the page checked
Refund tool create_refund available on Local only create_refund listed

Client-specific setup matters: the same server can behave differently depending on which client and authentication method you use. Record which deployment each team uses.

How should a read-first investigation work?

Start every investigation by reading, not changing anything. Give the assistant exact identifiers: your order ID, the provider’s order ID and any payment ID the customer has.

Investigation 1: “I paid but my order is unpaid”

Step Razorpay tools Cashfree tools
Find the order and its attempts fetch_order, fetch_order_payments get_order, get_payments_for_an_order, search_orders
Inspect a specific payment fetch_payment get_payment_by_id, get_transaction_details (full lifecycle)
Check for existing refunds fetch_multiple_refunds_for_payment, fetch_refund get_refund
Search more widely fetch_all_payments, fetch_all_orders search_transactions

What the analyst needs back: each attempt’s status and timestamp, the amount and currency, and whether any attempt was captured. If the assistant says “the payment succeeded”, ask it to show the payment ID and status field it relied on.

Investigation 2: “Why is settlement short?”

Step Razorpay tools Cashfree tools
List settlements fetch_all_settlements, fetch_settlement_with_id search_standard_settlements, get_standard_settlement_details (transfer timeline)
Reconciliation detail fetch_settlement_recon_details generate_recon_report, get_report_status, download_report
Instant or on-demand settlements fetch_all_instant_settlements, fetch_instant_settlement_with_id search_on_demand_settlements, get_on_demand_charges
Unsettled balance Not listed as a separate tool get_unsettled_amount, get_next_settlement_date

Cashfree’s report tools work asynchronously: generate, check status, then download. Razorpay’s recon details come back from a fetch. Either way, require full result coverage: check pagination, date ranges and time zones, so the assistant does not summarise only the first page.

Rules for any investigation

  • Distinguish the assistant’s interpretation from verified facts: “captured”, “refund processed” and “credited to bank” are different states.
  • Ask for source records (IDs, statuses, timestamps), not just conclusions.
  • Keep the conversation away from card numbers, CVV, full bank details and customer secrets.

Which actions can change money, and where?

Here is the boundary that matters most.

Action type Razorpay Remote Razorpay Local Cashfree managed
Read payments, orders, refunds, settlements Yes Yes Yes
Capture a payment capture_payment capture_payment Not listed
Create or update payment links create_payment_link, update_payment_link Same create_payment_link, cancel_payment_link
Create an order create_order create_order create_order
Update notes on payments, orders or refunds update_payment, update_order, update_refund Same Not listed
Issue a refund Not available (Local only) create_refund create_refund
Create instant settlement Not available (Local only) create_instant_settlement Not listed (on-demand charges and eligibility can be read)
Close a QR code Not available close_qr_code Not applicable
Revoke saved tokens revoke_token revoke_token Not listed

So: do not describe every MCP connection as read-only, and do not assume both hosted servers can refund. Razorpay’s hosted Remote server cannot issue refunds through MCP today; its Local server can. Cashfree’s managed server lists a refund tool.

A safe refund walkthrough

If you allow refunds through an assistant at all, follow this sequence:

  1. Identify the payment by exact payment ID and confirm amount, currency and capture status.
  2. Check existing refunds for that payment to avoid duplicates.
  3. Check eligibility: refund window, partial versus full, and any chargeback in progress.
  4. Draft the action: the assistant states the exact tool, payment ID and amount it intends to use.
  5. Human approval: an authorised person approves outside the chat, or in the client’s confirmation step, with the reason recorded.
  6. Execute through the supported deployment (Razorpay Local or Cashfree managed).
  7. Retrieve status with fetch_refund or get_refund and record the refund ID.
  8. Resolve uncertainty before retrying. If the call timed out, check whether a refund was created before trying again.

What controls should you put in place before connecting a live account?

Separate what the provider documents from what you must implement:

Control Provider support Merchant responsibility
Limit tools Razorpay: READ_ONLY and TOOLSETS options Expose only the tools each team needs; check Cashfree options with Cashfree
Credentials Razorpay API keys or OAuth; Cashfree OAuth Keep keys out of prompts, logs and shared configs; rotate on staff changes (see our key rotation guide)
Test vs live Separate test and live credentials Use test mode for training and prompts; label live connections clearly
Approvals Client-level confirmation prompts vary Require human approval for refunds, captures and settlements
Audit Provider logs API activity Record operation IDs, who approved and why
Revocation Cashfree: disconnecting revokes refresh token Document how to revoke access and the dashboard fallback
Access level Cashfree requires owner-level access Decide who holds that access and review it regularly; see dashboard access controls

Do not promise universal approval gates, idempotency or safety across all clients. Behaviour depends on the client, deployment and configuration.

Example prompts that keep an assistant on the read side

How you phrase requests shapes what the assistant tries to do. These prompts keep investigations safe:

  • “Fetch order order_ABC123 and list every payment attempt with status, amount and timestamp. Do not change anything.”
  • “For payment pay_XYZ789, show refunds already issued and their status.”
  • “List settlements between 1 and 7 November and show the recon details for each. Include all pages of results.”
  • “What is the unsettled amount and the next settlement date? Show the source values.”

Prompts to avoid unless a human has approved the action outside the chat:

  • “Refund this customer.”
  • “Capture all authorised payments from yesterday.”
  • “Create an instant settlement for the full balance.”

A useful habit is to ask the assistant to describe the tool call it intends to make, including tool name and parameters, before running anything that changes data.

How should you roll out payment MCP in phases?

  1. Phase 1: test mode only. Connect with test credentials, train the team on prompts and check that results match the dashboard.
  2. Phase 2: live, read-only. On Razorpay, use READ_ONLY mode or restricted toolsets; on Cashfree, confirm with Cashfree how to limit tools, and restrict who can connect given the owner-level requirement.
  3. Phase 3: low-risk writes. Allow payment link creation or notes updates for a small group, with logging.
  4. Phase 4: approved money movements. Only if needed, enable refunds through Razorpay Local or Cashfree with a documented approval step and daily review of operations.
  5. Review regularly. Revoke access for leavers, rotate keys, and review which tools are actually used.

Why we recommend Razorpay for teams that want a read-first AI rollout

For operations teams introducing AI assistants carefully, we recommend Razorpay when its tools and deployment match the use case. Our reasons:

  • Two deployments with a clear boundary: the hosted Remote server excludes refunds and instant settlement creation, which suits a read-heavy support rollout; the Local server is available when a team deliberately needs those actions.
  • Documented scope controls: READ_ONLY mode and TOOLSETS selection let teams expose only what they need.
  • Broad, granular read tools: payments, orders, refunds, settlements, recon details, instant settlements, payouts and QR codes, which cover most investigations.
  • Wide client support: Claude Desktop, Cursor and VS Code are named in the documentation.

These are configuration reasons. They are not a guarantee of safety, and any write tool still needs your approval process.

When Cashfree may fit better

Cashfree’s MCP server may suit finance teams that want settlement and cash-position questions answered quickly: unsettled amount, next settlement date with holidays, standard settlement timelines, on-demand eligibility and charges, and asynchronous reconciliation and summary reports. It connects through OAuth from popular clients without hosting anything. Because it requires owner-level access and lists create_refund, define who connects it and how refunds are approved before use.

FAQs

1. Can an AI assistant issue refunds through Razorpay’s MCP server?

Only through the Local (self-hosted) deployment, according to Razorpay’s current tool table, which marks create_refund as unavailable on the hosted Remote server. Teams that enable it should require human approval for every refund.

2. Does Cashfree’s MCP server support refunds?

Yes. Cashfree’s documented payment gateway tools include create_refund and get_refund. Because it connects with owner-level access, set clear rules for who can ask the assistant to refund and how approvals are recorded.

3. Is a payment MCP connection read-only?

Not by default. Both providers expose some write tools. Razorpay documents a READ_ONLY mode and toolset selection to restrict access. Check what your connection exposes before using it with live credentials.

4. What is the difference between Razorpay Remote and Local MCP?

Remote is hosted by Razorpay, needs no infrastructure and updates automatically, but excludes certain tools such as create_refund and create_instant_settlement. Local runs on your own infrastructure with Docker and gives access to all tools.

5. What access do I need to connect Cashfree’s MCP server?

An active Cashfree merchant account with owner-level access and an eligible AI client, such as Claude or ChatGPT with connector support, Cursor or Claude Code. You authenticate through OAuth; disconnecting the client revokes its refresh token.

6. Can I trust an assistant’s summary of a payment’s status?

Treat it as a starting point. Ask for the payment ID, status field and timestamp it used, and check against the dashboard for anything consequential. “Captured”, “refunded” and “settled to bank” are distinct states.

7. Should support agents share card or customer details with the assistant?

No. Investigations need payment and order IDs, not card numbers, CVV or full bank details. Keep sensitive data out of prompts and logs.

8. Can I use MCP with test mode first?

Yes, and you should. Connect with test credentials first so the team can learn prompts and check results against the dashboard without touching live money. Switch to live credentials only after access rules and approvals are agreed.

Author

  • Praneetha S R

    Praneetha S R writes about payment fraud from the merchant’s side, covering UPI and payment-link scams, chargebacks and friendly fraud, account takeover, card testing and new threats such as deepfakes and AiTM phishing.

PS

Praneetha S R

Praneetha S R writes about payment fraud from the merchant’s side, covering UPI and payment-link scams, chargebacks and friendly fraud, account takeover, card testing and new threats such as deepfakes and AiTM phishing.

Leave a Reply

Your email address will not be published. Required fields are marked *