Cashfree Relay: your processor runs your back office

Cashfree moved Relay out of beta this week — a set of AI agents that run payment operations for small merchants. Retry the failed charge. Chase the abandoned cart. Confirm the cash-on-delivery order before dispatch. Fix the failed subscription. File the dispute before the deadline. It is free for every Cashfree merchant at launch, with outcome-based pricing promised "as adoption grows." That last clause is the whole story.

What actually happened

Per IBS Intelligence and SMEStreet, Relay had been in merchant beta since May 2026 and is now available to all Cashfree merchants. The design details are the notable part:

• It acts, it doesn't alert. Relay executes against live merchant transaction data rather than flagging a task for a human to clear.
• Configuration is a prompt. Merchants describe the outcome they want in plain language or by speech — no workflow builder, no rules engine.
• Approval gates on money and contact. Cashfree says merchant approval is required before funds move and before a customer is contacted.
• Data stays on Cashfree infrastructure. The company states merchant transaction data is not sent to external AI providers.

Cashfree's own figures — that the average SMB spends roughly 60 hours a week on payment operations, dropping to under 45 minutes with Relay — are vendor marketing, sourced from the launch announcement and not independently verified. Treat the direction as real and the magnitude as a sales number.

Why it matters for your business

Strip away the India-specific framing and this is the pattern every processor is converging on: the payment vendor absorbing the operations layer above the payment. Stripe did it with Billing and Radar. Shopify did it with Flow. Cashfree is doing it with agents, and giving it away first.

Free is the right price for the version of a product whose job is to become load-bearing. Dunning logic, cart recovery sequences, COD confirmation rules and dispute timelines are not payment infrastructure — they are your revenue operations, encoded. Once they live inside the processor, switching processors stops being an integration project and becomes a business-logic rewrite. That is not a reason to skip Relay. It is a reason to be deliberate about what you let it own.

The practical split we use: let the vendor own the parts that are genuinely their domain — retry timing tuned to their issuer relationships, dispute filing against their acquirer's deadlines. Keep the parts that are yours — who gets contacted, in what sequence, with what message, and what the outcome data looks like when you export it. If Relay can retry a charge but you cannot pull the retry-outcome history into your own warehouse, you have rented visibility into your own revenue.

And test the approval gates before you trust them. "Merchant approval before a customer is contacted" is a claim about default configuration, and defaults change on the vendor's schedule, not yours.

Sources: IBS Intelligence — Cashfree's Relay brings AI agents to SMB payment operations, SMEStreet — Cashfree Relay Automates Payment Workflows for SMBs.