RazorpayPayments & BillingReady to ship

Razorpay API Integration

Accept payments, create orders and disburse payouts through India's most-used payment gateway.

Provider
Razorpay
Version
v1
Uptime
99.99%
Latency
220 ms
Access
Licensed
OrdersPayoutsUPI

What Razorpay API integration does

Razorpay is the most widely deployed payment gateway in India, and our integration covers the three operations most products need from it: creating orders and collecting payments, disbursing payouts, and reconciling settlements.

The part teams underestimate is the callback path. Payment confirmation arrives as a webhook, and webhooks are unreliable by nature — they get retried, they arrive out of order, and occasionally they do not arrive at all while your endpoint is redeploying. Our integration verifies webhook signatures, applies idempotency against your own order reference and replays anything unacknowledged, so a duplicate callback cannot double-credit an order and a missed one cannot leave a paid order looking unpaid.

What teams build with it

Checkout collection

Create orders and collect payments across cards, UPI, netbanking and wallets with confirmation reconciled against your ledger.

Vendor and partner payouts

Disburse to bank accounts and VPAs at scale with beneficiary validation and status tracking.

Subscriptions

Run recurring billing with mandate handling and dunning that survives card expiry.

Marketplace settlement

Collect from buyers and settle to sellers with per-order reconciliation.

Endpoints included

  • POST/razorpay/v1/orders
    Creates a payment order that the checkout widget collects against.

Try it in the sandbox

Creates a payment order that the checkout widget collects against.
POSThttps://sandbox.aeologic.io/razorpay/v1/orders
Requestapplication/json
{
  "amount": 249900,
  "currency": "INR",
  "receipt": "rcpt_AEO_88213",
  "notes": {
    "order_id": "AEO-88213"
  }
}
Response
Run the sample to see a live response
Returns masked / synthetic data in Sandbox

What you need before we start

  • An active Razorpay merchant account with API keys
  • A publicly reachable webhook endpoint
  • An order reference model supporting idempotency
  • A defined refund and dispute policy

How we deliver it

  1. Order model mapping and idempotency-key design
  2. Sandbox integration covering success, failure and refund paths
  3. Webhook signature verification and replay handling
  4. Production cutover with settlement reconciliation and alerting

Solution bundles that use it

Razorpay API integration — FAQs

Do we need our own Razorpay account?

Yes. The connector runs against your merchant account and your negotiated pricing — we integrate, we do not resell.

How are duplicate webhooks handled?

Signatures are verified and operations are idempotent against your order reference, so repeated callbacks resolve to a single ledger entry.

Can we run Razorpay alongside another gateway?

Yes. Multi-gateway routing is a common setup, and because the interface is normalised, adding or switching a gateway is configuration rather than a rewrite.

Ship Razorpay in days

Tell us your stack and we'll wire up Razorpay API integration for your team.

Talk to Aeologic