Razorpay payment gateway for WooCommerce

Two accounts have to exist first: an approved Razorpay account and a working WooCommerce store on HTTPS. Razorpay's own prerequisites list a created account, completed KYC, business activation after their activation email, and generated API keys. Until the review finishes, only test keys do anything useful.

The store side needs WooCommerce active, at least one product, a checkout page, and a valid SSL certificate — the Razorpay checkout window will not open on an insecure page. If you are still fixing that, start with the SSL troubleshooting guide. The plugin talks to Razorpay over HTTPS, so a server that blocks outbound requests breaks it at checkout.

Use test keys while the review is open. A live key pasted too early either fails checkout outright or charges a real customer while you are still learning the settings screens.

Set the payment action to "Authorize and Capture" unless you have a reason to capture each payment by hand. With auto-capture, a successful payment is captured at once and the order moves on. With "Authorize" only, you capture manually from the Razorpay dashboard — and Razorpay's documentation warns that uncaptured payments are automatically refunded after 5 days, leaving you with no money and a confused customer.

• Authorize and Capture: the default choice for digital goods, normal retail, and any store without a manual review step.
• Authorize only: for stores that verify stock or fraud-check each order before taking the money. Capture within the window or lose the payment.

Since plugin version 3.5.0, webhooks are auto-configured the moment you save the Key ID and Secret in the plugin settings. The plugin registers the events it needs — payment.authorized, payment.captured, payment.failed and order.paid — on your Razorpay account. Verify them under Dashboard → Account & Settings → Webhooks; if you regenerate API keys, re-save them in the plugin so the auto-configuration runs again.

This matters because Razorpay can capture the money while WooCommerce still shows Pending or Failed — the browser closed before the store heard the result. When that happens, open the webhook settings in the dashboard, confirm the payment.captured event is present, and use Razorpay's "Resend" on the stuck event. The order is fixed when its note carries the payment id and the status moves to Processing.

Once a week, match WooCommerce orders against Razorpay payments so a missed update or an unrecorded refund stands out early.

The plugin itself is free; Razorpay charges per successful payment, and the exact rate for your account sits in the Razorpay dashboard, not on this page. Razorpay's pricing varies by method (UPI is typically the cheapest), and GST applies on their fee. Read the number off your own dashboard or pricing page before you build it into product prices.

Settlement timing is a property of the Razorpay account — on-hold period, business category, and bank — not something the WooCommerce plugin controls. Do not assume another store's payout schedule is yours. Reconcile payouts to orders in the dashboard before deciding a week looks short.

Razorpay's fee invoice is not the GST invoice your customer downloads with the order — that is a separate WooCommerce job, covered in the GST invoice guide.