INDEPENDENT PERSPECTIVE. INFORMED DECISIONS. INDIA + GLOBAL
THE CURIOS
NOTEBOOK↗
Meet the editor ↗

B2B PAYMENTS · INDIA COMPARISON

Razorpay vs PayU 2026: Fees, Integrations & Ownership Costs

Compare Razorpay and PayU for Indian ecommerce: fees, integrations, settlements, support, ownership costs and our research-led verdict with ratings.

By Sarang S. Babu · Published · About 15 minutes

ComparisonsAlternatives / B2B payments

Read as Markdown

Listen to article

Enable JavaScript to use audio playback.

BASED ON OUR RESEARCH · INDIA

The Curios Notebook's Verdict

Razorpay is our preferred overall choice for a growing Indian ecommerce business. Compare the applicable quote, integration and operating arrangement before committing.

Editorial category and overall ratings out of five
CategoryRazorpayPayU
Payment options and product breadth20% weight 5.0/5 4.0/5
Developer tools and automation20% weight 5.0/5 4.0/5
International capabilities15% weight 4.5/5 3.5/5
Ecommerce and Shopify fit15% weight 4.5/5 3.5/5
Pricing and long-term value20% weight 4.0/5 3.5/5
Support and settlement clarity10% weight 3.5/5 2.5/5
Overall editorial rating 4.5/5 3.6/5

Scores use the same gateway rubric and reuse the current individual reviews. They are editorial judgments, not customer averages, success-rate measurements or ROI guarantees.

Razorpay review and score rationale · PayU review and score rationale · Rating method

Original illustration of connected checkout interfaces and payment cards
Original editorial illustration by The Curios Notebook. All ratings, terms and comparison data appear as selectable text.

Quick answer: which payment gateway do we prefer?

Razorpay is our stronger overall recommendation for a growing Indian ecommerce business. It earns 4.5/5, while PayU earns 3.6/5 in our payment-gateway rubric. PayU is a credible option to evaluate when its approved configuration and commercial terms match the business, but our recommendation is more conditional.

The comparison is not settled by a headline fee. Both providers publish a similar starting percentage for important domestic methods. The meaningful differences appear in implementation, plugin scope, refund administration, support and the full cost of operating the relationship.

This article explains those differences for an India-based merchant. It is not a comparison of every product carrying either brand, and the ratings are not customer averages or measured payment-success percentages.

Key takeaways

Razorpay versus PayU at a glance

Area Razorpay PayU
Our editorial rating 4.5/5 3.6/5
Listed domestic starting rate 2% plus GST 2% plus GST for listed domestic methods
Commercial detail to clarify Method-specific and optional-product charges UPI quote and method-specific charges
Shopify limitation highlighted in the docs Route and Subscriptions not supported through the documented plugin Offers apply to hosted app; related refunds use PayU dashboard
WooCommerce consideration Confirm the exact recurring-product implementation Recurring payments not supported through the standard plugin
Main strength in our assessment Broad tooling and overall growth fit Documented payment and integration options
Main reservation Higher capability does not guarantee lower ownership cost or better support Plugin scope and support confidence make the fit more conditional

Provider details are supported by the linked pricing and integration documentation. The relative assessment is ours. [1][2][3][4][5]

Scope: compare the same merchant, not different sales pitches

Imagine the same business asking both providers for a proposal. Its legal entity, product, order value, buyer geography and payment mix should be consistent. If one quotation assumes ordinary domestic checkout and the other includes international or recurring capability, the headline prices are not directly comparable.

Our research examines the published terms and operating documentation, along with relevant customer feedback. Razorpay's underlying review was checked on 12 November 2026; its standard pricing was revisited for this article. PayU documentation and customer snapshots were checked on 16 November.

The verdict weights payment breadth, developer tools, international capability, ecommerce fit, value and support/settlement clarity. The individual scores explain why the overall result differs. Readers can place greater emphasis on a category that is unusually important for their own business.

No single gateway is automatically the right answer for every merchant. Our recommendation is strong for the defined growing-store use case, while leaving room for a different conclusion when a negotiated proposal or specialized requirement changes the facts.

Pricing: the same starting rate does not mean the same bill

PayU lists a higher rate for several premium and international categories, and its UPI arrangement requires a quote. Razorpay likewise has method-specific pricing beyond its standard headline. [2][1]

The invoice depends on the transactions the business actually processes. A store should divide its expected volume into meaningful method groups and apply the relevant quote to each. Use the same transaction assumptions for both providers.

An illustrative equal-rate scenario

Assume ₹10,00,000 of eligible transaction value is charged at 2% under either arrangement. The processing fee would be ₹20,000. Applying 18% GST to that fee gives ₹3,600, for an illustrative cash charge of ₹23,600 before other items. [6]

The arithmetic is identical under those assumptions. It does not establish that every real merchant pays the same total. A different payment mix, an optional service, a negotiated term or the commerce platform's own charge can change the result.

If the base fee is effectively equal, the founder should spend less time debating the headline and more time examining the workflow. A provider that creates extra manual work can cost more even when its processing percentage is identical.

The quote comparison sheet

Item Why it needs its own answer
Ordinary domestic payments Establishes the basic processing assumption
Premium and international methods Prevents an entry rate from becoming a universal rate
UPI arrangement Identifies the merchant's actual applicable quote
Optional products Separates checkout, settlement or operational additions
Refunds and disputes Clarifies charges and treatment of the original fee
Platform costs Keeps Shopify or other commerce charges visible
Support entitlement Makes the operating relationship explicit

Ask both providers to complete the same sheet. An unanswered item should remain unanswered until clarified; it should not become a zero-cost assumption in the spreadsheet.

Long-term ownership: where the difference can emerge

The owner of a small store may personally handle payment exceptions, customer messages and accounting checks. That time is part of the payment system's cost, even when no separate invoice arrives for it.

Consider an illustrative internal task that takes four hours a month at an assumed staff value of ₹500 per hour. Its operating cost is ₹2,000 a month, calculated as time multiplied by the assumed hourly value. This is not a measured cost for either provider. It shows why a small recurring inefficiency deserves attention.

A useful ownership model includes:

Do not add all these as assumed provider fees. Some are internal business costs, and some may already be covered by a staff role. The point is to make the comparison complete enough to support a real decision.

High ROI needs a defined baseline

A gateway can offer high-return potential when its capabilities reduce meaningful work or support profitable sales. That remains a hypothesis until the merchant measures the relevant change.

Compare contribution margin rather than gross sales alone. An extra order has product, shipping, support and possibly return costs. Similarly, a faster workflow creates value only if the saved time can be used productively or avoids another expense.

We favor Razorpay's overall potential in this rubric, but do not assign an invented uplift to make the recommendation look mathematical. The store should measure the outcome against its own baseline.

Payment breadth: build around the buying journey

A useful gateway gives customers suitable ways to pay and gives the merchant a clear final status. The right configuration depends on what the store sells and how customers make the purchase.

For lower-friction repeat purchases, the priorities may differ from an expensive product requiring an instalment option. An international buyer introduces currency and documentation questions. A subscription business needs ongoing mandate and status management rather than only an initial successful order.

Both providers have documented product options beyond a basic checkout. PayU's customization guidance makes eligibility and agreements relevant to some capabilities. Razorpay's ecommerce offering includes supporting checkout tools. [7][6]

Our advice is to approve the required journey before expanding the feature list. A founder should be able to explain which capability solves which business problem. Otherwise, implementation complexity can grow faster than the value it creates.

Shopify: two different kinds of limitation

Razorpay's Shopify documentation excludes particular Razorpay products from the plugin's scope. PayU's offers documentation distinguishes the hosted app from onsite cards and describes a dashboard-based refund path for offer transactions. These limitations concern different things and should not be flattened into one generic “Shopify supported” tick. [3][4]

For the merchant, the practical question is who performs each task and in which system. A payment app can integrate with the storefront while still requiring staff to use another dashboard for a particular operation.

A useful demonstration request

Ask the implementation partner to show the intended order journey with the exact offer and app configuration. Include the customer's return to the store, the final order status and an appropriate refund operation.

Then ask a nontechnical staff member to explain what they would do if the customer reports a problem. If the process depends on the developer translating several dashboards, include that dependency in the ownership decision.

Shopify's third-party transaction charges should also be included separately. The relevant plan terms, not the gateway's sales quote, determine that additional platform layer. [8]

WooCommerce and recurring payments

PayU's standard WooCommerce plugin does not support recurring payments according to its FAQ. The documentation points towards a web-checkout route instead. [5] That can be a material implementation difference for memberships or repeat-delivery businesses.

It does not mean PayU has no subscription product. It means that a convenient ecommerce integration should not be assumed to expose every product capability. The distinction is important when a developer estimates the project based on installing a plugin.

Apply the same discipline to Razorpay. Confirm the exact recurring integration, merchant approval and lifecycle events for the intended configuration. A company's subscription feature and a particular store's working subscription flow are different levels of the decision.

What a recurring business should map

Stage Business question
Signup What confirms that the customer has successfully authorized the arrangement?
Scheduled collection How does the store learn the final payment state?
Failure What happens to access, delivery and customer communication?
Cancellation Which system records the customer's instruction?
Change How are product or plan changes reflected in billing?
Migration Which records and customer actions would a future move require?

These questions define the acceptance criteria. They are not claims that either provider supports every possible variation without additional work.

Developer tooling and automation

Razorpay's developer-tools directory and MCP announcement are part of why it scores strongly in our implementation assessment. PayU provides integration and verification documentation that can support a conventional merchant workflow. [9][10][7][4]

The label “AI” is less important than the task being improved. A tool that helps locate the right documentation can be valuable. It does not remove the need to review payment code, protect secrets and understand how order state changes.

For an early-stage business, the most useful implementation is usually one another competent developer can maintain. Keep configuration, credentials ownership, deployment steps and failure-handling notes clear enough for a handover.

Avoid making the storefront depend on a single person's undocumented understanding. That creates an ownership risk regardless of which gateway was selected. A better provider toolkit helps, but the merchant and implementation partner remain responsible for using it properly.

Settlements: matching numbers can hide different definitions

Razorpay documents a standard domestic T+2-working-day cycle from capture. PayU's dashboard FAQ describes T+2 working days from the successful transaction. [11][12]

The numbers look similar, but the event that starts the clock and the account's applicable conditions should be understood. A comparison that says only “both settle in two days” discards information a finance team needs.

The founder should be able to answer when funds become available and how the settlement is matched to orders. Keep bank receipts distinct from payment success in the cash forecast, particularly during a period when advertising and inventory spending rise together.

Plan for the exception, not only the normal cycle

An operating arrangement should explain what to do when a bank credit does not match expectations. Who investigates, what references are required and how does the issue escalate?

These questions do not assume a provider routinely delays payments. They recognize that even a well-documented normal process needs an exception path. A small store should establish that path while the sales team is still engaged.

Refunds: PayU's documented range is broader

Razorpay's normal-refund guidance describes five to seven working days. PayU's refund documentation gives a typical five-to-twenty-one-day range, with some cases taking longer. These are provider descriptions with different conditions, not results from a controlled head-to-head timing study. [13][14]

The difference deserves attention when writing customer-facing policies. Do not promise the shortest figure found on a marketing page without checking the account's actual refund flow.

A merchant should distinguish store approval, gateway initiation and customer receipt. The buyer needs an accurate update at each stage. Clear communication can reduce repeat enquiries even when a remaining processing step is outside the store's control.

For partial returns, verify that staff can connect the refunded amount with the right items and order reference. The business needs a reliable record for accounting and customer support, not merely a confirmation that an API request was accepted.

International commerce: configuration comes before country counts

Razorpay documents international card acceptance and related merchant requirements. PayU offers multiple international flows whose settlement and documentation details depend on the chosen product. [15][16]

PayU's Dynamic Currency Conversion FAQ describes INR settlement and a route for FIRC through account management. That should not be generalized to every PayU cross-border arrangement. [17]

For an Indian exporter, define the buyer countries, displayed currency, settlement currency and paperwork requirements. Then request a proposal for that exact flow. An overseas merchant collecting from India is a different use case and should not be used as evidence for the Indian export journey.

The better choice is the provider that can support the required market and finance process clearly. A long currency list is less useful than a complete answer about the market where the store expects to make its first overseas sales.

Support and public customer feedback

PayU's grievance policy provides a formal escalation process. That is useful operational information, but it is not the same as a measured response time for an urgent merchant issue. [18]

Its public review profiles show mixed experiences. On 16 November 2026, G2 displayed 3.1/5 from 25 reviews, Capterra 4.0/5 from 49, and Trustpilot's payu.in profile 1.8/5 from 54. The first two are broader PayU profiles rather than controlled India-only samples. [P_G2][19][20]

Our PayU review covers positive integration and dashboard accounts alongside onboarding and support concerns. A relevant Reddit account also reports a smooth Shopify onboarding experience. We retain that counterexample rather than presenting every account as negative. [21]

Razorpay's own review includes mixed customer feedback too. Our higher score should not be read as a claim that its support is consistently excellent for every account. The practical comparison is the support arrangement each provider will actually make available to this merchant.

Which business should choose which?

Choose Razorpay as the starting shortlist leader when growth flexibility matters

Our research favors it for a business that expects to use a broader toolkit and can implement it responsibly. The strongest case is a store that can connect the documented capabilities with specific operational needs.

Do not select it because the score relieves the business of due diligence. Confirm the quote, product approval, platform integration and support route. A recommended provider still needs to satisfy the merchant's acceptance criteria.

Keep PayU in consideration when its proposal fits a defined workflow

A clear approved configuration and a satisfactory commercial arrangement can make PayU relevant. The store should resolve the specific plugin and support questions identified in this comparison rather than assuming the brand's overall scope covers them.

For a simple one-time-purchase store, a subscription limitation may not matter. For a recurring business, it may change the project. The same factual limitation can have very different importance depending on the selling model.

If the current gateway already works well, define the reason to migrate

A review score alone is not a migration business case. Identify the existing cost or constraint, the desired improvement and how the replacement will be evaluated. Include outstanding refunds, historical records and the work of changing staff routines.

If the proposed move does not solve a clear problem, migration itself may create more work than it removes. Compare the expected benefit with the complete transition cost, not only the new processing quote.

Conclusion: Razorpay leads, with PayU a conditional alternative

Our verdict is Razorpay 4.5/5 and PayU 3.6/5. Razorpay offers the stronger overall fit in our research-led assessment for a growing Indian ecommerce store. PayU merits a more conditional evaluation focused on the exact integration and service arrangement.

The most useful comparison combines fees, capabilities and ownership. Ask both providers the same questions, price the same transaction mix and demonstrate the same order lifecycle. That produces a more durable decision than choosing whichever headline looks most attractive on the day of signup.

Frequently asked questions

Are the two gateways equally priced?

Only under a defined set of assumptions. The example above uses the same standard rate for eligible transactions. Real bills depend on methods, product choices, platform costs and negotiated terms.

Does PayU's WooCommerce limitation mean it cannot serve subscriptions?

No. It limits that plugin route. Establish the alternative integration and its operating requirements before choosing PayU for a recurring business. [5]

Which provider guarantees better ROI?

Neither editorial score establishes guaranteed ROI. Define the business outcome, measure the implementation and calculate incremental value after relevant costs.

Should I compare platform star averages directly?

They are useful context, but the samples and audiences differ. Read relevant accounts and keep their dates and product scope attached. Our editorial score uses a separate published rubric.

What is the next practical step?

Request comparable proposals and run the same focused acceptance exercise for both configurations. Use the results to confirm or challenge the recommendation before committing the business to the operating relationship.

Sources and verification notes

Published 16 November 2026. Cashfree and PayU sources checked on that date. Razorpay product documentation and Shopify pricing draw on our 12 November research; Razorpay standard pricing was revisited on 16 November. Provider terms, attributed customer accounts, author research and editorial judgments are distinguished. Calculations and recommended merchant checks are identified in the text.

  1. Razorpay pricing, standard rate revisited 16 November 2026
  2. PayU India pricing, checked 16 November 2026
  3. Razorpay Shopify product scope, checked 12 November 2026
  4. PayU Shopify offers: supported app and refund workflow
  5. PayU WooCommerce FAQs: recurring and international scope
  6. Razorpay ecommerce product and GST example, checked 12 November 2026
  7. PayU payment-page customization and eligibility
  8. Shopify India pricing and third-party payment charges, checked 12 November 2026
  9. Razorpay developer tools, checked 12 November 2026
  10. Razorpay MCP announcement, checked 12 November 2026
  11. Razorpay settlement cycles, checked 12 November 2026
  12. PayU dashboard FAQs: settlement and account prerequisites
  13. Razorpay refund guidance, checked 12 November 2026
  14. PayU refund introduction and timelines
  15. Razorpay international card acceptance, checked 12 November 2026
  16. PayU Dynamic Currency Conversion introduction
  17. PayU Dynamic Currency Conversion FAQs
  18. PayU grievance policy and escalation process
  19. Capterra PayU reviews, snapshot 16 November 2026
  20. Trustpilot payu.in profile, snapshot 16 November 2026
  21. Reddit: merchant account of PayU Shopify onboarding

Disclosure: the publisher reports no employment, consulting, sponsorship or affiliate relationship with Razorpay. Material updates will be recorded here.