A Cashfree connection uses the API keys of your own Cashfree Payments account. Cashfree steps make payment links and orders there and refund its orders; Cashfree charges its own fees on each payment.

Who can do this

Workspace Admins and Editors, on any plan — Cashfree is not a premium connection. Viewers see the connection but cannot add or change it.

On Cashfree's side, someone who can see API Keys in the Cashfree Merchant Dashboard.

Before you start

A Cashfree Payments account. Sandbox keys work straight away; production keys need the account to be activated in Cashfree.

Steps

In Cashfree, find the keys:

  1. Sign in to the Cashfree Merchant Dashboard, and open Payment Gateway.
  2. Choose the environment: the sandbox (test) environment for test keys, or production.
  3. Go to Developers, then API Keys.
  4. Generate a key if there is none, then copy the App ID and the Secret key.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Payments, select Cashfree. It reads "Stored credential".
  3. In Connection name, type a name — for example Consulace Cashfree sandbox.
  4. Paste the ID in App ID — Cashfree Merchant Dashboard › Developers › API Keys.
  5. Paste the key in Secret key — Beside the App ID. It also checks every event Cashfree sends. It is hidden as you type.
  6. In Environment, choose Production (the default) or Sandbox (test) — Sandbox keys work only with Sandbox, and never move real money. Choose the one the keys came from.
  7. Leave Test the connection before saving ticked. Bizomate asks Cashfree for an order that does not exist: good keys get "not found", wrong ones are refused.
  8. Select Save connection. The button reads Testing, then the dialog closes.

The toast "Connection added" says "“Consulace Cashfree sandbox” is ready. Every workflow in this workspace can use it."

What happens next

  • A Sandbox connection shows the Test mode pill on Connections, on every step that uses it, and in the step's settings.
  • Cashfree steps list it under Connection: Create a payment link, Create an order, Get an order and Refund an order. Its triggers use it too.
  • Test in the connection's panel answers "Reached Cashfree · sandbox" or "Reached Cashfree · production".

Good to know

  • Test mode comes from Environment, not the keys. Keep a Sandbox connection for building and a Production one for the published workflow — see Steps that move money.
  • The Secret key also checks Cashfree's events. If you make a new key in Cashfree, reconnect with it, or triggers refuse every event.
  • A new key. In Bizomate, open the connection's panel, select Revoke and Revoke connection, then Reconnect, fill in the fields and select Reconnect.

If something goes wrong

What you see Why What to do
"Fill in App ID." / "Fill in Secret key." A box is empty. Copy it from Developers › API Keys.
Cashfree refused it — "Cashfree refused: … Check the connection's details on Connections. Nothing was saved." The keys are wrong, or are from the other environment — sandbox keys with Production, or the other way round. Copy both again, and choose the Environment they came from.
"The connection has no Secret key. Reconnect it on Connections and fill it in." (in a run) The connection's details are incomplete. Revoke it and Reconnect with every field filled in.
"Could not reach Cashfree: …" or "Cashfree did not answer within 30 seconds." Cashfree could not be reached. Try again in a few minutes.