Cancel payment link
USE WHEN: The user wants to cancel/deactivate an existing payment link so no further payments can be made. Cancel a payment link. Only links in ACTIVE status can be cancelled.
ActionTry it
Integrate Cashfree MCP
with your AI CRM
Cashfree Payments MCP lets authorized agents manage payment links, orders, refunds, payment simulation, settlements, reconciliation reports, and related merchant payment workflows.
Explore Triggers and Actions
Create order
USE WHEN: The user wants to create a payment order to accept a payment. Requires amount, currency, and customer details. Create a new payment order. Returns order_id and payment_session_id needed to collect payment. NEXT: Call get_order(order_id) to verify the order was created and retrieve the payment session.
ActionTry it
Create payment link
USE WHEN: The user wants to create a shareable payment link to collect money from customers. Create a new payment link with an amount, purpose, and customer details. Returns the link URL. NEXT: Call fetch_payment_link_details(link_id) to verify the link was created and check its status.
ActionTry it
Create refund
USE WHEN: The user wants to initiate a refund for a payment. Create a refund against an order. Requires order_id and refund details in the body. NEXT: Call get_refund(order_id, refund_id) to track the refund status.
ActionTry it
Download report
USE WHEN: A report has reached DONE status and the user wants the download URL. Download a completed report.
ActionTry it
Fetch payment link details
USE WHEN: The user wants to check the status or details of an existing payment link. Fetch all details and status of a payment link by its link_id.
ActionTry it
Fetch simulation
USE WHEN: The user wants to check the result of a simulated payment. Fetch simulated payment details by simulation_id.
ActionTry it
Generate recon report
USE WHEN: The user wants to generate a settlement reconciliation report. Generate a settlement reconciliation report asynchronously. NEXT: Call get_report_status(reportId) to poll until the report is DONE, then download_report(reportId). DATE RANGE LIMIT: startDate and endDate must be supplied together and be either a custom range of 31 days or less, or exactly one full financial year — April 1 to March 31 of any financial year that has already begun (the current one may also be requested as April 1 to today). There is no limit on how far back the range starts, but a custom range must not extend into the future. Anything else is rejected with HTTP 400 — split wider custom periods into 31-day chunks.
ActionTry it
Generate summary report
USE WHEN: The user wants to generate a transaction summary, settlement, refund, or ledger report. Generate a summary/download report asynchronously. NEXT: Call get_report_status(reportId) to poll until the report is DONE, then download_report(reportId). DATE RANGE LIMIT: every date pair (startDate/endDate, bbpsStartDate/bbpsEndDate, subscriptionStartDate/subscriptionEndDate) must be either a custom range of 31 days or less, or exactly one full financial year — April 1 to March 31 of any financial year that has already begun (the current one may also be requested as April 1 to today). There is no limit on how far back a range starts, but a custom range must not extend into the future. Anything else is rejected with HTTP 400 — split wider custom periods into 31-day chunks.
ActionTry it
Get instant settlement rates
USE WHEN: The user asks about the charge rate for instant/on-demand settlements. Get instant/on-demand settlement charge rates.
ActionTry it
Get merchant free trial credits
USE WHEN: The user asks about free trial credits for on-demand settlements. Get merchant free trial credits for on-demand settlements.
ActionTry it
Get next settlement date
USE WHEN: The user asks when the next settlement will happen or about settlement schedule. Get the merchant's next settlement date and holiday information.
ActionTry it
Get on demand charges
USE WHEN: The user wants to preview charges/fees for an on-demand settlement withdrawal. Calculate exact charges for a specific on-demand withdrawal amount.
ActionTry it
Get on demand daily limit
USE WHEN: The user asks about on-demand settlement withdrawal limits. Get on-demand settlement maximum daily limit. NEXT: Call get_on_demand_eligible_funds() to see the actual withdrawable amount.
ActionTry it
Get on demand eligible funds
USE WHEN: The user wants to know how much money can be withdrawn via on-demand settlement. Get eligible funds for on-demand settlement withdrawal. NEXT: Call get_on_demand_charges(requestedAmount, freeTrialRequest=false) to preview fees before withdrawal.
ActionTry it
Get on demand settlement activation status
USE WHEN: The user asks if on-demand/instant settlements are available or activated. Get on-demand settlement activation status. NEXT: If activated, call get_on_demand_eligible_funds() to check available balance.
ActionTry it
Get order
USE WHEN: The user wants to check the status of an order or retrieve its payment session details. Fetch order details using the order_id. NEXT: Call get_payments_for_an_order(order_id) to see all payment attempts against this order.
ActionTry it
Get order extended
USE WHEN: The user needs extended order information including address, cart items, offers, and customer details. Fetch extended order data using the Cashfree order_id.
ActionTry it
Get orders for a payment link
USE WHEN: The user wants to see all orders created against a specific payment link. View all order details for a payment link. NEXT: Call get_order(order_id) or get_payments_for_an_order(order_id) for specific order details.
ActionTry it
Get payment by
USE WHEN: The user wants to view details of a specific payment attempt on an order. Get payment details by order_id and cf_payment_id. NEXT: To refund this payment, call create_refund(order_id, body={refund_amount, refund_id}).
ActionTry it
Get payment modes
USE WHEN: The user wants to filter transactions by payment method but you need the numeric code. Also useful to show what payment methods are available. Retrieve the merchant's available payment method codes. NEXT: Use the returned code in search_transactions(paymentCode=<code>) to filter by payment method. Returns: Mapping of payment method display names to numeric codes
ActionTry it
Get payments for an order
USE WHEN: The user wants to see all payment attempts made against a specific order. View all payment details for an order. NEXT: Call get_payment_by_id(order_id, cf_payment_id) to view details of a specific payment.
ActionTry it
Get refund
USE WHEN: The user wants to check the status of a specific refund. Fetch a specific refund by order_id and refund_id.
ActionTry it
Get report status
USE WHEN: You need to check if a report is ready for download. Poll this after generate_recon_report or generate_summary_report. Get report status and details (polling endpoint). NEXT: If status is DONE, call download_report(reportId). If REQUESTED or IN_PROGRESS, poll again.
ActionTry it
Get settlement recon routes
USE WHEN: The user wants to generate a Flowwise Recon report and you need the gateway route names. Get settlement recon gateway routes. NEXT: Use route names in generate_recon_report(reportType='flow_wise_recon_report', pg=<route_name>). Returns: Array of gateway route objects
ActionTry it
Get standard settlement details
USE WHEN: The user wants to track where settlement money is in the banking pipeline. Get real-time transfer timeline for specific settlements.
ActionTry it
Get tool guide
USE WHEN: You are about to perform a multi-step task and need to know which tools to call and in what order. CALL THIS FIRST before starting any complex task. Returns the recommended tool chain for a user's intent. Describe the user's goal in natural language. Examples: - "search for failed transactions in the last 7 days" - "generate a settlement reconciliation report" - "create a payment order for 500 INR" - "check the status of a refund" - "verify a PAN number" NEXT: Follow the returned step-by-step tool chain to complete the task.
ActionTry it
Get transaction details
USE WHEN: The user wants to see the full details of a specific transaction including timeline, settlement, and gateway response. View the complete lifecycle of a single transaction. Returns timeline events, order details, customer details, settlement info, gateway response, and optionally EMI and OCC charge breakdowns.
ActionTry it
Get unsettled amount
USE WHEN: The user asks about unsettled balance, money held by Cashfree, or pending settlements. Get the total unsettled amount held by Cashfree. NEXT: Call get_on_demand_eligible_funds() to check how much can be withdrawn immediately, or search_standard_settlements() for history.
ActionTry it
Get vendor settlement details
USE WHEN: The user wants to track where vendor settlement money is in the banking pipeline. Get real-time transfer timeline for specific vendor (Easy Split) settlements.
ActionTry it
List reports
USE WHEN: The user wants to see previously generated reports or check if a report exists. List all previously generated reports for this merchant. NEXT: Call download_report(reportId) to get the download URL for a completed report. DATE RANGE LIMIT: startDate and endDate must be supplied together, span 31 days or less, fall within the last 2 years, and not extend into the future. Wider requests are rejected with HTTP 400 — split them into 31-day chunks. Unlike the generate_* tools, there is no financial-year option here.
ActionTry it
Search on demand settlements
USE WHEN: The user wants to search past on-demand/instant withdrawal settlements. Search on-demand (instant withdrawal) settlements. DATE RANGE LIMIT: startDate and endDate must be supplied together, span 31 days or less, fall within the last 2 years, and not extend into the future. Wider requests are rejected with HTTP 400 — split them into 31-day chunks.
ActionTry it
Search orders
Search for orders with filters OR fetch a specific order by ID
ActionTry it
Search product docs
USE WHEN: The user asks about Cashfree Developer Documentation product features, API usage, integration guides, or how something works. Searches Cashfree Developer Documentation product documentation and returns matching help articles with titles, content, and links. NEXT: Use the returned content to answer the user's question directly.
ActionTry it
Search standard settlements
USE WHEN: The user wants to search settlement history, check settlement status, or find a specific settlement by UTR. Search standard (scheduled) settlements with filtering and pagination. NEXT: Call get_standard_settlement_details(settlementIds=<id>) to track a specific settlement through the banking pipeline. DATE RANGE LIMIT: startDate and endDate must be supplied together, span 31 days or less, fall within the last 2 years, and not extend into the future. Wider requests are rejected with HTTP 400 — split them into 31-day chunks.
ActionTry it
Search transactions
USE WHEN: The user wants to find, search, filter, or list payment transactions. Search for payment transactions matching the given filters. This is the primary discovery endpoint. NEXT: Call get_transaction_details(txId=<refId>, txTime=<txTime>) to view a specific transaction's full lifecycle. DATE RANGE LIMIT: startDate and endDate must be supplied together, span 31 days or less, fall within the last 2 years, and not extend into the future. Wider requests are rejected with HTTP 400 — split them into 31-day chunks.
ActionTry it
Search vendor settlements
USE WHEN: The user wants to search vendor split (Easy Split) settlement payouts. Search vendor split settlement payouts (Easy Split only). NEXT: Call get_vendor_settlement_details(settlementIds=<id>) to track vendor payouts. DATE RANGE LIMIT: startDate and endDate must be supplied together, span 31 days or less, fall within the last 2 years, and not extend into the future. Wider requests are rejected with HTTP 400 — split them into 31-day chunks.
ActionTry it
Simulate payment
USE WHEN: The user wants to test/simulate a payment in sandbox mode. Simulate a payment for testing. Create an order first using create_order. NEXT: Call fetch_simulation(simulation_id) to check the simulation result.
ActionTry it
How the Cashfree MCP integration works
The Cashfree MCP integration connects your Dench AI CRM directly to Cashfree MCP, so agents can read and act on your Cashfree MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
38 actions are available for agents to invoke on your behalf. Every call runs through Cashfree MCP's own authorization, scoped to the account you connect.
Set up Cashfree MCP in Dench
- 1
Sign in to your Dench workspace and open Integrations.
- 2
Find Cashfree MCP and click Connect — you'll authorize access through Cashfree MCP's own sign-in flow. No API keys or code required.
- 3
Ask an agent to use Cashfree MCP in chat, or call it from an automation.
- 4
Manage or disconnect the connection any time from workspace settings.
Frequently asked questions
How does the Cashfree MCP integration work with Dench?
The Dench Cashfree MCP integration connects your AI CRM to Cashfree MCP, so AI agents can work with your Cashfree MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
What actions can AI agents perform with Cashfree MCP via Dench?
The Cashfree MCP integration currently exposes 38 actions, including Cancel payment link, Create order, Create payment link, Create refund, Download report, and Fetch payment link details. Agents invoke them on your behalf from chat or from automations.
Do I need to write code to connect Cashfree MCP to Dench?
No. You connect Cashfree MCP from your Dench workspace using Cashfree MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Is the Cashfree MCP integration secure?
Connections are authorized through Cashfree MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Cashfree MCP connection from your workspace settings at any time.