Independent research & analysis on payment security Search
paymentsecuritypros.com Payment Security Insights
E-commerce & Online Payments

Razorpay vs PhonePe Payment Gateway for High-Value UPI: Limits, Declines and Safe Checkout Recovery

A customer wants to pay ₹2,40,000 for a laptop, a semester’s fees or a year of insurance. They have the money. They choose UPI because it is fast and familiar. The payment fails, or worse, it sits on “processing” while their bank app shows the amount as debited. The customer phones you; your support agent sees nothing useful; the sale is at risk and so is trust.

This guide explains why high-value UPI payments fail, which parts of the problem a payment gateway can and cannot control, and what Razorpay and PhonePe Payment Gateway each tell you when an attempt goes wrong. It finishes with a three-case recovery table and a pre-launch checklist. It does not compare pricing or general gateway features; for those, see our Razorpay vs Paytm pricing comparison.

Facts come from each provider’s public documentation and Razorpay’s published UPI limit guide, checked on 12 November 2026. UPI limits are set by NPCI and banks and change periodically, so confirm current figures before publishing them to customers.

Quick answer: Neither Razorpay nor PhonePe Payment Gateway can raise a customer’s UPI limit. Limits come from NPCI rules, the customer’s bank and the merchant’s registered category: the general cap is ₹1 lakh per transaction, and certain categories such as education, hospitals, insurance and tax payments can accept up to ₹5 lakh. Where the gateways differ is in what they show you after a failure. Razorpay documents named UPI error reasons (bank downtime, insufficient funds, invalid VPA, cancellation, timeouts) with suggested actions; PhonePe’s order-status API separates order state from individual attempts and returns errorCode and detailedErrorCode for failed attempts. Use either one’s authoritative status, never a customer screenshot, before you decide what to do next.

Key takeaways

  • A gateway does not override bank or NPCI limits. The merchant’s category registration decides whether customers can pay above ₹1 lakh by UPI.
  • Razorpay publishes a UPI error-code list with a suggested action for each reason, which makes customer messaging easier to script.
  • PhonePe’s order-status API distinguishes an order from each payment attempt, so you can see every retry with its own transactionId, state and error codes.
  • PENDING, FAILED and COMPLETED need three different responses. Treat “pending after debit” as unresolved, not failed.
  • Never advise customers to split a payment to get around a limit; offer another supported method instead.

Why do high-value UPI payments fail when the customer has the money?

A UPI payment passes through several parties, and any of them can refuse it. Before blaming the gateway, separate the layers:

  • NPCI rules: set the default per-transaction ceiling (₹1 lakh for most person-to-merchant payments) and higher ceilings for specific merchant categories.
  • The customer’s bank: applies its own per-transaction and daily limits, which can be lower than NPCI’s, especially at some co-operative and regional rural banks. Banks also apply restrictions to newly registered UPI users; Razorpay’s guide cites ₹5,000 in the first 24 hours.
  • The customer’s UPI app: shows the bank’s limits and may apply its own counts or checks.
  • The merchant’s category (MCC) and registration: decides whether the higher category limit applies to your payments at all. A hospital registered under a generic category may still be capped at ₹1 lakh.
  • The gateway and acquiring bank: carry the payment, report status, and can be affected by partner bank downtime, but they do not set the customer’s limit.

UPI limit layers at a glance

Layer What it controls Who can change it What the merchant can do
NPCI Default and category per-transaction ceilings NPCI by circular Check which category your business qualifies for
Customer’s bank Per-transaction, daily amount, daily count, new-user limits The bank Tell customers limits are bank-set; offer alternatives
Merchant category Whether higher category limits apply Gateway and acquiring bank, based on your business Confirm your registered category in writing
Gateway and acquirer Status, error reporting, downtime routing Provider Read authoritative status; plan recovery
Customer’s UPI app Display of limits, user experience App provider Suggest the customer check limits in their app

Razorpay’s guide lists ₹5 lakh per transaction for categories including capital markets, insurance, education, hospitals and healthcare, government and tax payments, IPO subscriptions, foreign inward remittances and credit card bill payments. Treat these as category-scoped, not universal, and confirm them against NPCI before you show any number on your checkout.

What does each gateway show you when a UPI payment fails?

The practical difference between providers shows up after the failure. You need to know whether the customer cancelled, the bank was down, the VPA was wrong, the request expired, or the payment is still in flight.

Razorpay: named UPI error reasons with suggested actions

Razorpay documents UPI error reasons and what to do about each. Highlights:

Razorpay error Meaning Suggested response
bank_technical_error The UPI provider was down Explain the downtime, suggest another UPI app; Custom and S2S integrations can show downtime at checkout using the Downtime API
gateway_technical_error Partner bank technical issue or downtime Ask the customer to retry later; ask Razorpay about multi-terminal routing for repeated partner downtime
insufficient_funds Not enough balance Customer adds funds or uses another account
invalid_vpa UPI ID not active Customer links their bank account to the UPI ID, then retries
payment_cancelled Customer cancelled or pressed back Invite the customer to try again
payment_collect_request_expired / payment_timed_out Customer did not approve within the time limit, usually about 10 minutes, or partner downtime Ask the customer to complete payment within the window
payment_declined Debit could not be completed Retry once, then offer another method
credit_failed Paid from an unregistered account, or partner bank downtime Pay from the registered account; contact support for downtime

On the page we checked there is no separate code labelled “limit exceeded”, so a limit-related refusal may appear as a decline or bank-side error. Your checkout copy should therefore mention limits as one possible reason when the amount is above ₹1 lakh.

PhonePe Payment Gateway: order state versus attempt state

PhonePe’s Order Status API returns the order’s overall state (PENDING, COMPLETED or FAILED) and, with details=true, every payment attempt in paymentDetails. Each attempt carries its own transactionId, paymentMode (such as UPI_INTENT, UPI_COLLECT or UPI_QR), timestamp, state, and on failure errorCode and detailedErrorCode. Adding errorContext=true returns the source, stage and description of a failure. The default response shows only the latest attempt, which can hide earlier failed retries.

That attempt-level view is useful for high-value payments, where a customer may try twice from two apps. One order can carry a failed attempt and a later successful one; reconcile on the attempt, not just the order. PhonePe’s docs also return INVALID_MERCHANT_ORDER_ID when no order matches, which is an integration problem rather than a payment failure.

Side-by-side view

Need Razorpay PhonePe PG
Named failure reasons Documented UPI error list with suggested actions errorCode and detailedErrorCode per failed attempt, plus optional errorContext
Multiple attempts per order Payments listed against an order (order and payment IDs) paymentDetails array with transactionId per attempt
Downtime visibility Downtime API for Custom and S2S checkout Not stated on the pages checked
Pending handling Status via API and webhooks Order stays PENDING until resolved; expireAt marks expiry
Raising a customer’s limit Not possible Not possible

Both providers give you enough to stop guessing. Razorpay’s advantage is a ready-made mapping from reason to customer action, which support teams can turn into scripts. PhonePe’s advantage is a clean separation of order and attempt that suits engineering-led reconciliation.

Why is a screenshot or browser return not proof of payment?

High-value payments attract both honest confusion and fraud. A customer’s screenshot can show a debit that later reverses, a payment to a different payee, or an edited image. A browser redirect back to your site can be lost, delayed or forged. Only two things should move an order to paid: a verified server-to-server notification and a status check against the gateway’s API. Our guide to webhook signature verification and duplicates covers the notification side.

PENDING, FAILED and COMPLETED are not three flavours of the same thing:

  • COMPLETED: fulfil, after checking amount, currency and order reference.
  • FAILED: no money should have moved; you can safely offer another attempt or method.
  • PENDING: money may have moved. Do not cancel, refund or ask for a second payment until the status resolves.

How should you recover a declined or pending high-value payment?

Use this three-case table as the basis of your checkout logic and support script.

Case How you know Authoritative check What to tell the customer What not to do
1. Limit-related decline Decline on an amount above the customer’s likely limit; bank or decline reason Gateway status shows failed; no debit “Your bank’s UPI limit may be lower than this amount. You can pay by card, netbanking or EMI instead.” Suggest splitting into smaller UPI payments; retry repeatedly
2. Technical failure bank_technical_error, gateway_technical_error, timeout, or PhonePe error codes indicating bank or network issues Gateway status failed “Your bank’s UPI service had a problem. No money was taken. Try another UPI app or another method.” Blame the customer; hide the alternative methods
3. Pending after debit Customer reports debit; gateway shows pending or processing Poll status (PhonePe until expireAt); wait for webhook “Your payment is being confirmed. Please do not pay again. We will update you shortly.” Mark failed; ask for a second payment; promise a fixed reversal deadline

For every case, store both the order identifier and the attempt identifier (Razorpay payment ID, PhonePe transactionId) with timestamps, so finance and support can reconcile later.

Why splitting payments is a bad idea

When a customer hits a limit, the tempting fix is to suggest two UPI payments of ₹1.2 lakh each. Avoid it. It may conflict with bank and network rules, creates two payments to reconcile against one order, and can trigger fraud checks. If your business genuinely needs higher UPI limits, the correct route is the right category registration through your gateway. Otherwise offer cards, netbanking or EMI; see our EMI comparison for affordability options on large tickets.

Customer messaging that reduces support calls

  • Show the payment amount and accepted methods before the customer picks UPI, with a short note that some banks cap UPI payments.
  • After a decline, show the reason category in plain words and one-click alternatives.
  • For pending payments, show a confirmation page with the order number and an honest “we’re confirming” message, then email the outcome.

What should you check before accepting high-value UPI payments?

  1. Confirm your merchant category with Razorpay or PhonePe and the acquiring bank in writing, including whether category limits up to ₹5 lakh apply to your account.
  2. Check the checkout channel. Intent, collect and QR flows can behave differently on timeouts; test each one you offer.
  3. Publish only verified numbers. Source wording differs: Razorpay’s own documentation and blog do not state daily transaction counts consistently, and PhonePe’s limits guide describes category increases whose dates need independent confirmation. If in doubt, say “limits are set by your bank”.
  4. Wire up authoritative status. Webhooks plus a status API check before fulfilment, with PhonePe’s details=true and errorContext=true where used.
  5. Script support responses for the three recovery cases above.
  6. Offer alternatives on the same page: cards, netbanking and EMI for high-value carts.
  7. Monitor declines by amount band. A spike in failures above ₹1 lakh usually points to category or bank limits, not gateway health.
  8. Escalate properly. Know your provider’s escalation path for stuck payments; our support and escalation comparison sets these out.

Why we recommend Razorpay for high-value UPI operations

For a merchant whose main risk is losing large UPI payments to confusing failures, we recommend Razorpay when its category registration and checkout fit the business. Our reasons:

  • Documented reason-to-action mapping: each UPI error reason comes with a suggested response, so support scripts and checkout messages can be built directly from the documentation.
  • Downtime awareness: the Downtime API lets Custom and S2S integrations warn customers before they choose an affected method.
  • Clear limit education: Razorpay’s published UPI limit guide explains the bank, NPCI and category layers that customers often misunderstand, which helps merchants write accurate checkout copy.
  • Alternatives on the same checkout: cards, netbanking, EMI and Pay Later can be offered in the same flow when UPI is refused.

These are operational reasons. They are not evidence that Razorpay can raise customer limits, has fewer outages or achieves higher success rates.

When PhonePe Payment Gateway may fit better

PhonePe PG may suit businesses whose customers overwhelmingly pay with the PhonePe app and whose engineering team wants attempt-level detail in one status call. Its order-status API returns every attempt with transactionId, payment mode, timestamp and error codes, plus optional error context, which is well suited to automated reconciliation of multiple attempts per order. Confirm your category limits, the timeout behaviour of each UPI flow and amount formatting in the API before launch.

FAQs

1. Can a payment gateway increase the UPI limit for my customers?

No. Neither Razorpay nor PhonePe Payment Gateway can raise a customer’s UPI limit. Limits come from NPCI rules, the customer’s bank and your registered merchant category. What a gateway can do is register your business under the correct category, report failures clearly and offer alternative payment methods in the same checkout.

2. What is the UPI limit for merchant payments in India?

The general ceiling is ₹1 lakh per transaction for most person-to-merchant payments. Certain categories, such as education, hospitals, insurance, tax and capital markets, can accept up to ₹5 lakh per transaction. Banks may apply lower limits and new-user restrictions. Check current NPCI circulars and your bank before relying on a figure.

3. Why does a UPI payment show debited but the order is still pending?

The payment may still be in flight between banks and the gateway. Do not cancel or ask for a second payment. Check the gateway’s authoritative status through its API and webhooks; PhonePe returns PENDING until the order resolves or expires, and Razorpay reports status through its payment APIs. If it later fails, the debit is normally reversed by the bank.

4. Should I tell customers to split a large payment into smaller UPI payments?

No. Splitting to avoid limits can conflict with bank and network rules, complicates reconciliation and may trigger risk checks. If your category qualifies for higher limits, register it correctly. Otherwise offer cards, netbanking or EMI for the full amount.

5. Which Razorpay error means the customer’s bank was down?

Razorpay’s documentation uses bank_technical_error when the UPI provider was down, and gateway_technical_error or credit_failed for partner bank issues. Suggest another UPI app or method, and contact Razorpay about multi-terminal routing if partner downtime recurs.

6. How do I see all attempts on one order with PhonePe Payment Gateway?

Call the Order Status API with details=true. The response lists every attempt in paymentDetails, each with its own transactionId, payment mode, timestamp, state and, for failures, errorCode and detailedErrorCode. Without that flag, only the latest attempt is returned.

7. Is a customer’s payment screenshot enough to release an order?

No. Screenshots can show reversed, misdirected or edited payments. Release an order only after a verified webhook and a status check confirm the payment is completed for the right amount and order reference.

Author

  • Gokul GS

    Gokul GS is the lead editor of paymentsecuritypros.com and writes its Indian payment gateway comparisons, covering fees, settlement, merchant support and dispute handling across Razorpay, Cashfree, PayU, Pine Labs and others.

GG

Gokul GS

Gokul GS is the lead editor of paymentsecuritypros.com and writes its Indian payment gateway comparisons, covering fees, settlement, merchant support and dispute handling across Razorpay, Cashfree, PayU, Pine Labs and others.

Leave a Reply

Your email address will not be published. Required fields are marked *