Razorpay Setting

What this page is for

Razorpay Setting configures gateway account credentials and capabilities for online checkout, customer payment links, mandates, refunds, and webhook reconciliation.

Who should use it

Owner, finance, platform admin

Where to find it

/admin/razorpay-settings

Before you start

• In the Razorpay Dashboard, owner/admin opens Account & Settings, API Keys, generates or views the test/live key, and copies Key ID into SquareOS key ID.
• Use the Razorpay dashboard mode switch deliberately. Test keys should be saved with Test mode enabled in SquareOS; live keys should be saved only after test payment and webhook proof.
• The Razorpay Key Secret is shown only at generation time. Paste it into the SquareOS key secret field immediately and store it only in the approved secret manager; do not send it over chat.
• Create the Razorpay webhook from Dashboard settings, set the SquareOS webhook URL supplied by platform/admin, select payment/link/refund/settlement/dispute events used by the gym, enter a separate webhook secret, and paste that secret into SquareOS Webhook secret.
• The webhook secret is different from the API key secret. SquareOS verifies Razorpay webhook signatures before using the payload.
• Enable checkout, payment links, mandates, and refunds only if the Razorpay account is actually enabled for that capability.
• Merchant reference should be the Razorpay merchant id/account reference or an owner-approved internal reference that finance can recognize.
• After saving, use Verify on the gateway account. Verification must happen before front desk depends on Pay here, payment links, mandates, or refunds.
• Keep Test mode enabled until the gym confirms sandbox payment, webhook, invoice state, refund behavior, and payment-link flow.
• Current backend contract: Razorpay webhook POST /commerce/webhooks/razorpay verifies x-razorpay-signature, stores a webhook event, queues gateway-processing, and reconciles valid payment/payment-link events immediately. Operators must inspect both webhook events and gateway-processing outbox/dead-letter state during failures.
• Production live gate: do not treat a saved Razorpay account as live-ready until a real Razorpay payment.captured or payment_link.paid webhook has updated the SquareOS payment, invoice, audit trail, and provider reference in the same tenant.

Daily workflow

• In SquareOS, open Admin, Razorpay Setting, configure provider Razorpay, account name, merchant reference, key ID, key secret, webhook secret, test mode, and capability switches.
• Create a small test invoice, use Pay online or payment link, complete payment in Razorpay test mode, then verify Transactions shows gateway reference, paid invoice state, and audit record.
• Trigger or wait for Razorpay webhook delivery and confirm webhook health/last delivery state before switching to live mode.
• Switch to live credentials only after owner/finance signs off.

Watch out

• Never paste Razorpay secrets into notes, templates, screenshots, or support chat. Secrets belong only in the credential field.

Related help

• Use the left menu to open related pages in Integrations.
• Use Ask Docs for questions that are already covered in this public documentation.