ProductPricingDemo
More

Company

AboutCustomersPartnersContact
Sign inStart free
HomeProductDemoStart free
Docs/Payment integration/Cashfree Payments integration

Connect Cashfree Payments to your store

Accept UPI, cards, net banking and pay-later on your Slaby store through Cashfree, with settlements going straight to your own account.

About 20 minutes, plus Cashfree's KYC approval.

On this page

  • Before you start
  • Step by step
  • Webhook settings
  • Test it before you go live
  • If something goes wrong
  • Cashfree Payments links you will need
  • Common questions

Before you start

  • A Cashfree merchant account with KYC completed.

Launch a branded retail and wholesale store in 15 minutes, then run catalogue, orders and delivery from one place.

Product

  • Features
  • Tour
  • Pricing

Explore

  • Demo
  • Compare

Company

  • About
  • Customers
  • Partners
  • Contact
Start freeSign in

© 2026 Slaby. All rights reserved.

  • Terms
  • Your business PAN, GST (if applicable) and settlement bank account.
  • Owner or manage-settings access to your Slaby admin.
  • A phone number on file for every buyer — Cashfree requires one on each payment. Slaby collects this at checkout.

    • Step by step

    1. 1

      Create your Cashfree merchant account

      In your Cashfree dashboard

      Sign up on the Cashfree merchant site and complete their onboarding. As with Razorpay, this account is yours — buyers pay into it and Cashfree settles to your bank.

      Sign up for Cashfree
    2. 2

      Decide: Sandbox or Production

      In your Cashfree dashboard

      Cashfree keeps two completely separate environments. Sandbox is for practice with fake money; Production takes real payments. They have different dashboards, different credentials, and nothing crosses between them.

      Slaby asks you which one your keys belong to, so it talks to the right one. Getting this wrong is the most common cause of 'my keys don't work'.

      • Sandbox — practice mode. Test payments only, no real money moves.
      • Production — live mode. Real buyers, real money, requires completed KYC.
    3. 3

      Copy your App ID and Secret Key

      In your Cashfree dashboard

      In the Cashfree merchant dashboard open Developers → API Keys. You will find an App ID and a Secret Key.

      Make sure you are in the environment you intend to use — the sandbox dashboard and the production dashboard each issue their own pair.

      • App ID — identifies your account (Cashfree sends it as x-client-id).
      • Secret Key — proves the request is yours. Keep it as carefully as a bank password.

      With Cashfree, the Secret Key does double duty: it also signs the webhook notifications. There is no separate webhook secret to create.

    4. 4

      Enter the credentials in Slaby

      In your Slaby admin

      In your Slaby admin go to Settings → Payments. Choose Cashfree, paste the App ID and Secret Key, and select the matching environment — Sandbox or Production.

      The Secret Key is stored write-only: it is never displayed again and never sent to a browser. The page shows only that a key is present.

    5. 5

      Add the webhook endpoint

      In your Cashfree dashboard

      In the Cashfree dashboard go to Developers → Webhooks and add a new endpoint pointing at your store, subscribing to the success and failure events listed below.

      You do not enter a secret here. Cashfree signs each notification with your Secret Key, and Slaby verifies it with the same key you already saved.

      Cashfree webhook documentation

      Add the webhook in the SAME environment as your keys. A sandbox webhook will never fire for production payments.

    6. 6

      Test in Sandbox, then go live

      On your own store

      With sandbox keys in place, order something on your own store and pay using Cashfree's test payment details. Check the order flips to Paid in your Slaby admin.

      Then swap in your production App ID and Secret Key, switch the environment setting to Production, add the production webhook, and place one real low-value order to confirm.

    Webhook settings

    Webhook URL
    https://yourstore.slaby.in/api/webhooks/cashfree-tenant

    Replace yourstore.slaby.in with your own store address. If you have connected a custom domain, use that instead — both work, but use the one buyers actually visit.

    Event to subscribe to
    PAYMENT_SUCCESS_WEBHOOK

    The payment succeeded. This is what marks the order Paid.

    Event to subscribe to
    PAYMENT_FAILED_WEBHOOK

    The payment failed, so the order is not left waiting.

    Cashfree does NOT use a separate webhook secret. Notifications are signed with your API Secret Key — the same one you entered in Slaby. There is nothing extra to configure.

    Test it before you go live

    1. 1.Create sandbox credentials from the Cashfree sandbox dashboard and set the environment in Slaby to Sandbox.
    2. 2.Place an order on your own store and pay with Cashfree's sandbox test instruments (their docs list test UPI ids and cards).
    3. 3.Confirm the order shows Paid in your admin, which proves the webhook is reaching you.
    4. 4.Switch to Production credentials and environment, re-add the webhook in the production dashboard, then place one small real order.

    If something goes wrong

    Payments fail with an authentication error.

    Why it happens: Sandbox keys with the environment set to Production, or the reverse.

    How to fix it: In Settings → Payments, check that the environment matches where the keys came from. Sandbox keys only work against Sandbox.

    The buyer could not start payment at all.

    Why it happens: Cashfree requires a customer phone number on every order and refuses the request without one.

    How to fix it: Make sure the buyer's account has a phone number. Slaby will tell you when this is the cause rather than showing a generic gateway error.

    The buyer paid but the order still shows unpaid.

    Why it happens: The webhook is missing, in the wrong environment, or pointed at the wrong address.

    How to fix it: Check the webhook exists in the same environment as your keys and that the URL matches your store exactly. Cashfree's dashboard shows recent delivery attempts and their responses.

    Every webhook is rejected as an invalid signature.

    Why it happens: The Secret Key stored in Slaby is not the one Cashfree is signing with — usually a sandbox/production mix-up, or a rotated key.

    How to fix it: Re-copy the Secret Key from the correct environment's dashboard and paste it into Settings → Payments.

    Cashfree Payments links you will need

    • Cashfree home page
    • Create an account
    • Merchant dashboard login
    • Sandbox (test) dashboard
    • Current pricing
    • Developer documentation
    • Cashfree support

    Common questions

    How is Cashfree different from Razorpay on Slaby?
    Functionally they do the same job and both settle directly to you. The main practical differences are that Cashfree keeps separate sandbox and production environments you must match, requires a buyer phone number on every order, and needs no separate webhook secret.
    Why does Slaby ask whether my keys are Sandbox or Production?
    Because Cashfree runs two entirely separate systems with different addresses. Slaby has to know which one to talk to; sandbox keys sent to production simply fail to authenticate.
    Do I need to create a webhook secret?
    No. Unlike Razorpay, Cashfree signs notifications with your API Secret Key. Once that key is saved in Slaby, webhook verification works with nothing further to set up.
    Can I switch from Cashfree to Razorpay later?
    Yes. Settings → Payments lets you change gateway at any time. Only the selected gateway's credentials are used, so you can leave the other set in place while you switch.
    What if Cashfree confirms a different amount than my order?
    Slaby refuses it. Every payment is checked against the order total frozen at checkout, and a mismatch is never marked Paid — it is flagged for you to look at instead.
    Razorpay integrationIntegrations & third-party tools
    Privacy
  • Refunds