A Razorpay connection uses your own Razorpay account's API key. Razorpay steps make payment links, orders, invoices and customers there, and capture and refund its payments; Razorpay charges its own fees on each payment, as it does for any other.

Who can do this

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

On Razorpay's side, someone who can see API Keys in the Razorpay Dashboard — usually the account's owner or an admin.

Before you start

A Razorpay account. Test keys work straight away; live keys need the account to be activated in Razorpay.

Steps

In Razorpay, make a key:

  1. Sign in to the Razorpay Dashboard.
  2. Choose the mode at the top of the Dashboard: Test Mode for a test key, or live mode for a live one. Each mode has its own key.
  3. Go to Account & Settings, then API Keys.
  4. Select Generate Key — or Regenerate Key if the mode already has one.
  5. Razorpay shows the Key ID and Key Secret once. Copy both, or download them, before you close the window. A test Key ID starts rzp_test_, a live one rzp_live_.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Payments, select Razorpay. It reads "Stored credential".
  3. In Connection name, type a name — for example Consulace Razorpay test or Consulace Razorpay.
  4. Paste the ID in Key ID — Razorpay Dashboard › Account & Settings › API Keys. A test key (rzp_test_) never moves real money. For example rzp_test_<your key id>.
  5. Paste the secret in Key secret — Shown once, when the key is made. Lost it? Regenerate the key in Razorpay. It is hidden as you type.
  6. Leave Test the connection before saving ticked. Bizomate asks Razorpay for one payment before keeping the details.
  7. Select Save connection. The button reads Testing, then the dialog closes.

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

What happens next

  • A test key shows the Test mode pill beside the connection on Connections, on every step that uses it, and in the step's settings. A live key shows no pill.
  • Razorpay steps list it under Connection: Create a payment link, Create an order, Fetch a payment, Capture a payment, Refund a payment, Create a customer, Create an invoice and Cancel a payment link. Its triggers use it too.
  • Test in the connection's panel answers "Reached Razorpay · test mode" or "Reached Razorpay · live".

Good to know

  • Test or live comes from the key. A rzp_test_ key only ever moves test money, and Razorpay shows its payments only in Test Mode in the Dashboard. Most people keep two connections — one test, one live — and switch steps to the live one before publishing. See Steps that move money.
  • Regenerating a key in Razorpay stops the old one at once. In Bizomate, open the connection's panel, select Revoke and Revoke connection, then Reconnect, paste the new Key ID and Key secret, and select Reconnect. With Test the connection before saving ticked, Reconnect tries them first and changes nothing if Razorpay refuses.
  • Triggers do not use the key to listen. Razorpay sends events to an address you paste into its Dashboard, with a secret Bizomate makes — see Start a workflow from Razorpay payment events.

If something goes wrong

What you see Why What to do
"Fill in Key ID." / "Fill in Key secret." A box is empty. Copy it from API Keys in the Razorpay Dashboard.
Razorpay refused it — "Razorpay refused: Authentication failed. Check the connection's details on Connections. Nothing was saved." The Key ID and Key secret do not belong together, one was regenerated, or one has a space or a missing character. Copy both again from the same mode, or regenerate the key.
"The connection has no Key secret. Reconnect it on Connections and fill it in." (in a run) The connection's details are incomplete. Revoke it and Reconnect with both fields filled in.
"Could not reach Razorpay: …" or "Razorpay did not answer within 30 seconds." Razorpay could not be reached. Try again in a few minutes.
Payments made in the Dashboard do not show to the steps The connection holds a test key and the payments are live, or the other way round. Use a connection with a key from the same mode as the payments.