Razorpay for payment gateways
Razorpay is a leading gateway in India and nearby markets, and its official server lets an agent create orders and payment links, capture and refund payments, and read payment records. For payment gateways it is our third pick of four: the right choice when your market is India, and a regional specialist rather than the broad global default the top pick is.
Where it earns the spot is regional fit and a hands-on payment surface. An agent can look up a transaction, see why a charge needs another step, capture an authorized payment, or generate a UPI link, which covers the day-to-day gateway questions for an India-focused stack.
How Razorpay fits
The read tools cover investigation: fetch_payment and fetch_all_payments (with filtering and pagination) to find and inspect charges, and fetch_payment_card_details to see the card used. The action tools handle the flow: capture_payment moves an authorized payment to captured, initiate_payment starts a payment with a saved method, and update_payment edits a payment's notes. For authentication, resend_otp and submit_otp drive the OTP step that regional card flows often require. Payment links round it out: create_payment_link and create_payment_link_upi generate standard and UPI links, while fetch_all_payment_links and fetch_payment_link read them back.
The honest framing: Razorpay's strength is regional, and the OTP and UPI tools reflect that focus rather than a global feature set. Stripe, the top pick, is the developer-first global processor that fits most stacks worldwide. Adyen is the choice for large enterprises needing broad global coverage and unified processing. Square fits in-person and omnichannel commerce, especially in its core markets. Reach for Razorpay when you operate in India and want an agent reading payments and driving links and captures on a gateway built for that region; for global reach, the others fit better.
Tools you would use
| Tool | What it does |
|---|---|
| capture_payment | Changes the payment status from authorized to captured. |
| fetch_payment | Fetches payment details with an ID. |
| fetch_payment_card_details | Fetches the card details used for a payment. |
| fetch_all_payments | Fetches all payments with filtering and pagination. |
| update_payment | Updates the notes field of a payment. |
| initiate_payment | Initiates a payment using a saved payment method with order and customer details. |
| resend_otp | Resends the OTP if the previous one was not received or expired. |
| submit_otp | Verifies and submits the OTP to complete payment authentication. |
| create_payment_link | Creates a new standard payment link. |
| create_payment_link_upi | Creates a new UPI payment link. |
FAQ
- Can the Razorpay server handle UPI and OTP flows?
- Yes. create_payment_link_upi generates a UPI payment link, and resend_otp with submit_otp drive the OTP authentication step that regional card flows often require. These reflect Razorpay's India focus, which is why it is the regional pick here rather than the global default.
- When should I choose Stripe or Adyen over Razorpay?
- Stripe is the developer-first global processor that fits most stacks worldwide, and Adyen suits large enterprises needing broad global coverage. Razorpay is the pick when your market is India and you want a gateway built for that region.