Razorpay for payments
Razorpay's official server lets an agent create payment links, capture authorized payments, and read payment records, which makes it a strong choice for India-focused commerce. For general payments it is our fourth pick of four, not because the server is thin but because the siblings cover broader global ground; Razorpay's edge is depth in its home market.
The value is driving real commerce flows from natural language. An agent can generate a payment link, capture an authorized charge, look up a transaction, or run the OTP step a regional card payment needs, instead of clicking through a dashboard or hand-coding the API.
How Razorpay fits
Creating and collecting is handled by initiate_payment, which starts a payment with a saved method against order and customer details, and the link tools create_payment_link and create_payment_link_upi for standard and UPI links. capture_payment moves an authorized payment to captured. On the read side, fetch_payment and fetch_all_payments (with filtering and pagination) pull individual and bulk records, fetch_payment_card_details reads the card used, and fetch_payment_link with fetch_all_payment_links read back links. update_payment edits notes, and resend_otp plus submit_otp drive OTP authentication.
The honest framing: this surface is built around payments and payment links, with the OTP and UPI tools showing Razorpay's regional focus. Stripe, the top pick, is the developer-first processor that fits most global stacks, with the broadest payments and billing surface. PayPal is the choice when you need its wallet and buyer network at checkout. Square fits in-person and omnichannel selling in its core markets. Choose Razorpay when you operate in India and want an agent creating links, capturing payments, and reading transactions on a gateway designed for that market; reach for the others when global reach or a specific network is the requirement.
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
- What payment flows can the Razorpay server drive?
- It can initiate_payment with a saved method, capture_payment on an authorized charge, create standard and UPI payment links, fetch individual and bulk payments, and run the OTP step via resend_otp and submit_otp. It reads and creates payments and links rather than managing subscriptions.
- Razorpay or Stripe for payments through an agent?
- Razorpay is the pick for India-focused commerce, with UPI links and OTP flows built in. Stripe is the top pick for most global stacks, offering the broadest payments and billing surface. The choice comes down to your market and how global your payments need to be.