Skip to main content
Razorpay support and its configuration must be confirmed in the target SpurtCommerce v6 checkout. Use the provider’s test environment until the complete order and webhook flow is verified.

Credentials and setup

Keep the Key Secret and webhook secret on the server only. The public Key ID may be exposed only where the integration’s official client flow requires it. Configure the exact callback/webhook URL registered with Razorpay.

Payment lifecycle

The backend should calculate the amount and currency, create the provider-side order/payment session, and persist the provider reference. The client completes the provider checkout. The backend verifies the returned signature and/or authenticated webhook before treating the payment as successful.

Reliability

Make webhook processing idempotent, validate amount/currency/order association, handle out-of-order events, and reconcile provider status with local order state. Do not trust a browser redirect as proof of payment.

Verify

Inspect the release’s payment adapter, environment variables, webhook/controller code, and dependencies. Document exact route names and signature fields only when confirmed.