iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For a React web app backed by Node.js, the safe Razorpay Standard Checkout flow is: create a payment order on your server, pass its ID to Checkout, verify the returned signature on your server, and fulfill the order only after confirming capture. Keep the Key Secret and trusted order records off the browser.
The official material cited below establishes this integration flow, but does not provide a complete current React-web-and-Node.js example. Treat the code structure as an implementation plan, and check Razorpay’s current web Checkout and API documentation for exact SDK names, package versions, and syntax before deploying. Availability and merchant eligibility can vary by region; confirm them in your Razorpay Dashboard and the documentation for your region.
How the React and Node.js parts fit together
React starts Checkout and displays the result to the customer. Node.js owns the trusted payment operations: creating an order, retaining the order ID, verifying the Checkout signature, and checking whether payment has been captured. Razorpay’s web integration guide describes this flow using a Python server, while its React-labelled guide covers React Native rather than React for the web. The shared server-side order, verification, and capture principles apply, but neither source is a ready-made React web plus Node.js tutorial. Razorpay Standard Checkout integration · Razorpay React Native integration
Free tools Windows power users keep installed
One-click scans. No signup required.
Build the payment flow in this order
-
Create an application order
When a customer is ready to pay, your server should validate the items and price against its own records, then create a corresponding Razorpay order through the Orders API. Store the Razorpay order ID alongside your application’s order record. Create a Razorpay order for each payment attempt; its ID connects the payment to Checkout. Do not let the browser nominate the trusted order ID used later for verification. See Razorpay’s web integration steps and React Native integration steps.
#1 Best Overall
Sale
Identiv SCR3310V2 USB Smart Card Reader Writer CAC/PIV- Fully Compliant - Complies With All Major Industry Standards, Including Iso/Iec 7816, Usb Ccid, Pc/Sc, And Microsoft Whql. As Well As, Emv 2011 Ver 4.3 Level 1 And Gsa Fips 201.
- Seamless Integration - With Identiv-Specific Smartos You’Ll Get Easy, Complete Support Of All Major Contact Smart Card Ics And Technologies In One Simple Reader.
- Universal Compatibility - Works With Virtually All Contact Chip Cards And Pc Operating Systems, Including Windows, Macos, Linux And Android.
- Fast And Convenient- Shorten Your Transaction Time With A Reader That’S Optimized For Speed. It’S Ultra-Compact And Robust Design Is Streamlined For Mobile Operation, Making This Reader The Best Choice For Convenience, Security And Reliability.
- Ergonomic and cost efficient design
-
Open Standard Checkout from React
Your React app requests payment setup from your server and supplies Checkout with the server-created order ID, the public Key ID, amount and currency, and appropriate business display details. The Key ID is intended for client-side use; the Key Secret is not. Checkout’s success response includes
razorpay_payment_id,razorpay_order_id, andrazorpay_signature. Send the response to your server for verification rather than treating a browser success message as proof of payment. Razorpay’s cited sources describe the Checkout flow and callback fields but do not establish the exact current React web package or code syntax. -
Verify the Checkout signature on Node.js
On the server, retrieve the expected Razorpay order ID from your own stored order record. Compute the expected HMAC-SHA256 signature over
order_id|razorpay_payment_idwith the server-held Key Secret, then compare it safely withrazorpay_signature. Do not use a client-supplied order ID as the authority for the signature calculation. Save the relevant payment identifiers and verification outcome in server-side state. See the web integration guide and Razorpay Trust Portal checklist.Rank #2
ZOWEETEK CAC Card Reader Military, USB Smart Card Reader for Windows Mac- Advanced Realtek Chipset; PIV, EMS, ISO-7816 & EMV2 2000 Level 1, CE, FCC, VCCI and Microsoft WHQL certifications.
- Supports ActivClient, AKO, OWA, DKO, JKO, NKO, BOL, GKO, Marinenet, AF Portal, Pure Edge Viewer, ApproveIt, DCO, DTS, LPS, Disa Enterprise Email and etc. CAC chip cards
- Sleek ergonomic flat design, precise slot, convenient to horizontally plug card
- Compatible with Windows10/11, Mac OS 10.15 or later. Driver free, plug and play.
- New generation DOD Military CAC USB smart chip card reader, no firmware upgrade requirements
-
Confirm status and capture before fulfillment
A valid signature establishes the authenticity of the Checkout response; it does not by itself establish that the payment is captured. Check payment status through the API or a webhook, and fulfill only after capture. Capture policy may be configured for automatic or manual handling; whichever policy you use, align your application’s fulfillment decision with captured status. Razorpay’s guidance ties capture settings to server-side use of the Orders API. Web integration steps · Trust Portal checklist
Recommended: PC Feels Slow? A Free Scan Shows What's Dragging Windows Down →Recommended: Crashes or Glitches? A Free Driver Scan Usually Finds the Culprit →Recommended: Fix Windows Errors and Clear Junk Files in Minutes - Free Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Use webhooks for asynchronous updates
Configure webhooks for the events your application needs, and validate each incoming webhook’s signature using HMAC before acting on it. Webhooks are suited to background updates and automation. If the customer-facing flow needs an immediate answer before a webhook arrives, fetch the payment or order status through the API as well; treat that fetch as the prompt confirmation path and the webhook as the asynchronous update path. See Razorpay webhooks and the Trust Portal checklist.
Rank #3
-
Test in test mode, then configure live mode
Run an end-to-end simulated transaction with test-mode keys before switching to live-mode keys. After the integration is validated, confirm the live-mode configuration and required event subscriptions in the Dashboard. The cited integration steps cover testing and the transition to live mode.
Keep secrets and payment state on the server
- Never ship the Key Secret to the browser. Keep it in server-side configuration and out of client bundles, source maps, and public repositories. The Razorpay Trust Portal checklist says API secrets should not be included in final client builds.
- Derive trusted payment details from server records. Validate the amount, currency, and application order on the server, and use the stored Razorpay order ID when checking the signature.
- Keep authentication, authorization, and capture distinct. Authorization or a successful Checkout callback is not a fulfillment signal; confirm capture before delivering goods or services. Razorpay says uncaptured payments are automatically refunded after a fixed time, but the cited material does not state the duration.
- Make updates resilient to repeated notifications. Webhook and API status updates can arrive through separate paths. Design order processing so handling the same payment event more than once does not accidentally duplicate fulfillment.
Interpret Razorpay order status correctly
The Orders API reference identifies created, attempted, and paid as order states. An order can remain paid even if its associated payment is refunded, so represent refund state separately in your application rather than treating it as a reversal of the order’s payment status. See Fetch an Order With ID.
Quick Recap
Best Value
- SmartQ C368 USB 3.0 Card Reader: Four-in-one design, supports Micro SD/SD/MS/CF cards, and reads data independently; ideal for plug and play mobile use during travel.
- High data transfer speed: Supports data transfer speed up to 5GB per second (at USB 3.0 speed), compatible with USB 3.0 and USB 2.0 multi-card readers for CF and MicroSD cards.
- Multi-system compatibility: Compatible with Windows/Mac OS/Linux and other systems, no driver needed, enjoy a plug and play experience.
- Working status: Blue LED light indicator, the indicator LED lights up when powered on, the device status is clearly visible.
- In the Box: SmartQ C368 USB 3.0 Card Reader (memory card not included), Cable organizer, User manual.
Rank #4
- Compact And Lightweight Dongle Form-Factor Card Reader
- Accepts Cards In Id1 Format (Iso8716)
- Ccid Compliant
- Compact and lightweight dongle form-factor card reader
- Accepts cards in ID1 format (ISO8716)
What to confirm before writing production code
- Use the current Razorpay documentation for web Standard Checkout and Node.js server/API syntax. The available sources do not establish current package versions or a complete React web and Node.js sample.
- Confirm merchant eligibility, supported payment methods, regional terms, and account configuration in the relevant region’s current documentation and Dashboard; the cited pages do not settle these questions for every region.
- Confirm that test and live credentials are kept separate, the live account is configured, webhook endpoints are subscribed to the necessary events, and webhook signatures are verified.
- Test the full path, including failed or abandoned attempts and status updates that arrive asynchronously, before relying on payment state for fulfillment.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
