Migrate Payment Gateway - Razorpay to Cashfree Payments

Follow a seven-step process: inventory all Razorpay SDK calls and webhook handlers, obtain Cashfree credentials, swap the SDK package, rewrite order creation and verification, replace Checkout JS with payment_session_id flow, rewrite webhooks, then parallel-run before full cutover.

The equivalent is PGCreateOrder (POST /pg/orders), which takes order_amount in rupees instead of paise, requires customer_id and customer_phone, and returns a payment_session_id for the client instead of exposing any API key.

Cashfree computes HMAC-SHA256 over the timestamp plus raw body and encodes it as base64, while Razorpay hashes only the body and encodes as hex. You must prepend the x-webhook-timestamp header value and switch the digest encoding to base64.

No. Cashfree has no public client-safe key; only the short-lived payment_session_id is sent to the browser. Payment success must be verified by re-fetching the order status from the backend, never by trusting a client callback.

Yes. RazorpayX Contact plus Fund Account maps to a single Cashfree Beneficiary object, and Razorpay Subscriptions map to Cashfree Plans and Subscriptions with different status values and webhook events, covered in the reference sections 7 and 9.

Skip it when the project has no existing Razorpay code, since a fresh Cashfree integration is simpler. It also does not migrate historical payment data; old Razorpay orders remain in Razorpay and only new traffic moves.