Apps › Payments

Cashfree automation with Bizomate

A Cashfree payment is the start of the work, not the end. Bizomate makes the payment link or order when it is needed, and the moment Cashfree reports a payment or a refund, it records it and tells the people who need to know. Refunds are marked as steps that move money, and every run leaves a record you can read.

Start free

On every plan, Free included.

At a glance

Label	Value
Plans	Every plan
Connect	App ID and secret key
Starts runs	Instantly
Kind	Connected app · Payments

What can start a workflow

Payment success
When a customer's payment succeeds

Cashfree sends events only to an address set in its dashboard, so you copy the trigger's address into Developers › Webhooks once. Every event's signature is checked with the connection's secret key, and one that does not match starts nothing.

Payment failed
When a customer's payment fails

Refund status
When a refund succeeds, fails or is cancelled

What a workflow can do with it

Create a payment link
A Cashfree link the customer pays by

For an amount and a purpose, to the customer's phone. Cashfree texts or emails the link if you switch those on.

Create an order
An order for Cashfree's checkout to take payment against

For Cashfree's checkout to take payment against, with an order id of your own, or one Cashfree makes.

Get an order
An order's status and amount

Refund an order
Sends money back for a paid order

Moves money: the amount you give, up to the order's full amount. A retry of the step sends the same idempotency key, so the customer is refunded once, and a test run with a production key asks first.

How you connect it

Paste the App ID and Secret key from the Cashfree Merchant Dashboard, under Developers › API Keys, and choose Production or Sandbox (test) — the one the keys came from. Sandbox keys never move real money, and a Sandbox connection shows a Test mode pill wherever it is used. Bizomate tests the keys before saving them, and Test answers "Reached Cashfree · sandbox" or "Reached Cashfree · production". Cashfree charges its own fees on each payment.

The secret is encrypted before it is saved, used only when a step runs, a test calls Cashfree or an event is checked, and never shown again — not to you, your colleagues or Bizomate support. It belongs to one workspace, the Code step cannot read it, and revoking the connection wipes it at once.

In the help centre: Connect Cashfree, Create a Cashfree payment link or order, Refund a Cashfree order, Start a workflow from Cashfree payment events and Steps that move money.

Questions about Cashfree

Why do I paste a webhook into Cashfree myself?

Cashfree sends events only to addresses set in its own dashboard. Copy the trigger's address into Developers › Webhooks, choose the payment and refund events, and save. Bizomate checks each event against your secret key.

Can I build with sandbox keys and go live later?

Yes. A Sandbox connection only ever moves test money. Most people keep a Sandbox connection for building and a Production one for the published workflow, and switch the steps over before publishing.

Can a refund be paid twice by mistake?

A retry of the same step sends the same idempotency key, so Cashfree refunds once. Run again, Test run and Run this step start a new run with a new key, which is why a test run with a production key asks first.

What if I make a new secret key in Cashfree?

Replace the key on the connection. The secret key also checks every event Cashfree sends, so until the connection has the new one, the triggers refuse every event.