# Cashfree — MCP Server

> Query payments, orders, settlements and refunds on India’s payment rails.

**Source:** https://mcpplaygroundonline.com/mcp-servers/cashfree  
**Transport:** http  
**Requires auth:** Yes

---

## What it does

The server exposes Cashfree’s payment APIs as MCP tools. Orders and payments are readable by id or filter, so an agent can answer the question support teams get all day: what happened to this specific transaction, and why did it fail. Refunds can be inspected and, depending on your credential scope, initiated. Settlement data is available, which is the finance-side question — what was actually paid out, when, and which transactions it covered. Payment links and beneficiary details round it out. Because Cashfree operates on Indian payment rails, the failure modes it surfaces are the locally specific ones — UPI collect timeouts, bank-side declines, mandate issues — that a generic payments integration describes poorly. Sandbox and production are separate environments with separate credentials, and pointing an agent at the wrong one is the usual first mistake.

## Tools exposed

- orders — create and read orders, including status and metadata
- payments — payment detail and failure reason for a transaction
- refunds — read refund status and initiate refunds where scoped
- settlements — settlement batches and the transactions they cover
- payment links — create and read hosted payment links
- beneficiaries — payout destination details

## Example queries you can run

- "Why did order 4821 fail, and was the customer charged?"
- "List refunds initiated this week that have not yet settled."
- "Which settlement batch included the payments from last Tuesday?"
- "Summarise payment failure reasons for the last thousand transactions."

## Details

- **Recommended model:** anthropic/claude-sonnet-4.5 — Payment states are subtle — authorised is not captured, and failed is not always unpaid. Sonnet 4.5 respects that distinction rather than collapsing it into success or failure.
- **Transport:** http
- **Authentication:** Required — Cashfree app credentials. Sandbox and production are separate environments — confirm which one the credential belongs to before an agent touches refunds.
- **Hosted endpoint:** https://mcp.cashfree.com/mcp
- **Official source:** [Cashfree Payments documentation](https://docs.cashfree.com/)

## Frequently asked questions

### What is the Cashfree MCP server?

Cashfree’s hosted MCP server at mcp.cashfree.com. It exposes orders, payments, refunds, settlements, payment links and beneficiary data as MCP tools for an AI assistant.

### Can an agent issue a refund?

Only if the credential permits it. This is the one capability to think hard about: a refund is real money leaving, it is not reversible, and an agent acting on a misread instruction is an expensive mistake. Read-only credentials for anything investigative.

### How do I avoid touching production by accident?

Use sandbox credentials. Cashfree keeps the environments fully separate, so a sandbox key simply cannot reach live transactions — which makes it the right default while you are working out what to let an agent do.

### Is it useful for support workflows?

That is the strongest fit. "What happened to this payment" requires joining order, payment and settlement records, and an agent does that in one turn instead of three dashboard lookups by a support rep.

### How does it compare with the Stripe MCP server?

Similar shape, different rails. Cashfree is built around Indian payment methods — UPI, netbanking, local mandates — so its failure reasons and settlement model reflect those. Stripe is the better fit for card-led international flows.

---

_Test this server across 40+ models on MCP Playground: https://mcpplaygroundonline.com/mcp-servers/cashfree — free, no install._