R

RazorpayX Payouts

India's most-integrated bulk-payouts API — pay any Indian bank account via IMPS, NEFT, RTGS or UPI through one endpoint, at ₹2–5 per payout, on top of partner-bank current accounts (ICICI, Axis, RBL, YES)

Payouts API / Vendor Payments 4.6 / 5 (1 Rating) Free account / ₹2–5 per payout Updated May 2026 🇮🇳 Bengaluru HQ

Quick Verdict

This page covers RazorpayX from a pure payments / payouts angle — the most common reason Indian product and finance teams integrate it as their first touchpoint. RazorpayX is the business-banking arm of Razorpay (founded 2014 in Bengaluru by Harshil Mathur and Shashank Kumar; RazorpayX itself launched in 2018), and its Payouts API has become the de facto "send money to any Indian bank account from your application" infrastructure for Indian SaaS, marketplaces, fintechs, and consumer-internet companies. The pricing is straightforward: free current account, ₹2–5 per payout depending on rail and volume — comparable to Cashfree Payouts, the main competitor in this category. As of 2025 figures, 45,000+ businesses use RazorpayX. For the full business-banking story (corporate cards, payroll, escrow, tax payments — i.e. everything beyond payouts), see the dedicated RazorpayX banking-api page; this page focuses specifically on the payouts integration that 90% of payments-curious teams care about first.

Payouts API maturity
4.8
Rail coverage (IMPS/NEFT/RTGS/UPI)
4.8
Settlement & reconciliation
4.5
Developer experience
4.6
Pricing transparency
4.2

What is the RazorpayX Payouts API?

RazorpayX Payouts is a single REST API that lets your application disburse money to any Indian bank account — by IFSC + account number, by UPI VPA, or by saved contact — on whichever rail makes sense (IMPS for sub-₹5L instant, NEFT for batch, RTGS for ₹2L+ value, UPI for low-ticket high-frequency). Behind the API sits a Razorpay-managed current account at one of four partner banks (ICICI Bank, Axis Bank, RBL Bank, YES Bank); your funds sit in that account, and each payout call debits the balance and instructs the bank to send the money to the destination. Webhooks fire on each state change (queued → processing → processed / failed / reversed), making the integration pattern straightforward for any product team that has ever consumed a webhook.

The API has become a default for several payment-adjacent use cases in Indian SaaS: vendor payments (paying suppliers, contractors, freelancers), marketplace settlements (paying out to sellers / drivers / partners after a transaction), refunds (returning money to customers when needed), salary disbursement (although for full payroll the dedicated RazorpayX Payroll product is usually a better fit), insurance / claim payouts, reward credits and loan disbursement for NBFCs.

The reason the Payouts API became the wedge product for RazorpayX more broadly is partly distribution: most Indian teams already used Razorpay's payment gateway for accepting consumer payments, and the path of least resistance for "now we also need to send money out" was Razorpay's same-vendor business-banking layer. The settlement reconciliation alone — gateway in + payouts out flowing through one dashboard — eliminates the kind of multi-vendor reconciliation pain that Indian finance teams spent the 2010s manually fighting.

This page sits in tools/payments/ and intentionally focuses on the payments / payouts use case. For the full RazorpayX business-banking surface — current accounts, RazorpayX Corporate Cards (launched June 2025), RazorpayX Payroll, tax payments, Escrow+, automated approvals — see the dedicated tools/banking-api/razorpay-x page, which covers all the non-payout features in detail.

Capabilities (payouts focus)

💸 Bulk & single payouts API

Single REST endpoint to send money via IMPS / NEFT / RTGS / UPI / card. Supports single-payout calls and bulk-batch CSV uploads (up to ~10K rows per batch). Idempotency keys for safe retry. Webhook callbacks on every state change.

👤 Contacts & fund accounts

Pre-create vendor / payee / beneficiary contacts with their bank-account or UPI VPA so subsequent payouts only need a contact-id reference. Reduces per-payout payload size and eliminates re-validation overhead. Useful for marketplaces with thousands of repeat sellers.

🛡️ Account-validation API

Penny-drop validation (₹1 transfer + reverse-lookup of account-holder name) to verify a beneficiary's bank account before sending real money. Standard practice in Indian disbursement to avoid failed payouts and customer-support tickets.

🔁 Auto-recharge & balance management

Configurable auto-debit from your linked source bank account when the RazorpayX current-account balance falls below a threshold. Eliminates manual top-ups for product teams running steady-state payout volume.

🧾 Reconciliation & settlement reports

Daily reconciliation reports with transaction-level matching, fee breakdowns, success/failure analytics. Especially useful when paired with Razorpay's payment-gateway settlements — same dashboard, single ledger.

👥 Multi-user approvals

Maker-checker workflow for high-value or high-risk payouts. Configurable approval thresholds, role-based access, audit logging. Important for finance / risk team controls in companies that have outgrown a single-founder approval model.

Pricing (payouts angle)

Razorpay publishes the payouts price card; rates are usage-based, no monthly subscription:

  • Current account — free. No setup fee, no minimum balance, no maintenance fee.
  • IMPS payouts — typically ₹3–₹5 per transaction, depending on volume and ticket size. Volume tiers can pull this down to ₹2–₹3 at scale.
  • NEFT payouts — usually ₹2–₹3 per transaction; cheapest rail for non-urgent transfers.
  • RTGS payouts — typically ₹10–₹20 per transaction; used for ₹2L+ ticket sizes.
  • UPI payouts — typically ₹2–₹5 per transaction; cheapest for low-ticket high-frequency payouts.
  • Card payouts — small fee + interchange; less commonly used.
  • Volume contracts — anything over ~₹5 Cr/month payout volume is worth a custom quote; expect 10–30% off list at that scale.

For most Indian SaaS teams running a steady-state payout product (e.g. paying out 10K vendors per month at average ₹50K), monthly RazorpayX Payouts spend lands in the ₹30K–₹2L range. Validate the live price card on razorpay.com/x/pricing; rates do change.

When RazorpayX Payouts is the right call

  1. You're already a Razorpay payment-gateway customer — settlements from your gateway can flow directly into the RazorpayX current account, and reconciliation lives in a single dashboard.
  2. You need a payouts API live in days, not weeks — RazorpayX has the most polished documentation and developer experience among Indian payouts vendors.
  3. You're running a marketplace, vendor-payment workflow, or seller settlement product — the contacts + fund-accounts model + bulk-batch upload is purpose-built for these patterns.
  4. You're a fintech or NBFC disbursing loans — RazorpayX is widely used for low-ticket consumer-loan disbursement at sub-second latency on IMPS and UPI.

RazorpayX Payouts is the wrong call when: you specifically need cross-border / multi-currency payouts (use Wise Business or Stripe); you want a different banking partner than the four RazorpayX uses; or you're a very high-volume payouts customer where a direct bank API integration becomes more economical than a layered vendor.

Pros & cons (payouts only)

✓ Pros

  • Most polished Indian payouts API — among the two best in the category alongside Cashfree
  • All major rails (IMPS, NEFT, RTGS, UPI, card) through one API
  • Free current account; usage-based pricing with no subscription
  • Excellent webhook + idempotency design for reliable production integration
  • Tight reconciliation with Razorpay payment gateway — single dashboard for in + out flows
  • Maker-checker controls and role-based access — finance-team friendly

✗ Cons

  • Underlying current account at a partner bank — issue resolution can span two support teams
  • India-only / INR-only; no cross-border or multi-currency payouts
  • Per-payout fees stack up at very high volumes (~50M+ payouts/year may justify direct bank API)
  • Locked into Razorpay vendor relationship — hard to switch later if you want a different partner-bank stack

Related insights & playbooks