Money debited, ticket not booked: what breaks in India's travel apps
Failed payments are the top malfunction in the Play Store reviews of India's travel and ticket apps, more often than in UPI or banking apps. What breaks and what to test.
In this article
The money is gone. The ticket isn't there. Do you try again and risk a second debit, or wait while the fare or seat disappears? In the Google Play reviews we read for India's travel and ticket apps, failed payments were the most common malfunction reviewers described. A slow screen is annoying; an uncertain booking can derail a trip.
We looked at 253 storefront reviews across 15 travel and ticket apps in our India App Quality Report, as shown on 23 October 2026. This is a snapshot of reviews, not a transaction failure rate or an app reliability ranking. What stands out is where the complaints cluster: payment and booking need to reach the same outcome, and reviewers often described a gap between them.
The headline: failed payments lead
12.6% of travel reviews described a malfunction (32 of 253; 95% range 9.1-17.3%), close to 10.7% across all 187 apps. What stands out is the type of complaint: failed payments lead at a point where travellers may be left without a ticket.
- Failed payments appeared in 11 of the 32 malfunction reviews, or 4.3% of all travel reviews, versus 1.4% across all apps. These complaints concern payment or its link to booking; they do not establish which system caused the issue.
- Travel reviews mentioned failed payments more often per review than UPI, payment or banking reviews. This compares review samples, not transaction failure rates.
- 12 of 15 apps had at least one malfunction review. One review warrants investigation, not a conclusion about a recurring defect.
- Complaints were nearly evenly split between software (44.4%) and service, fees, support or delivery (43.1%). The causes differ, even when travellers experience them as one problem.
- 54.5% of the latest release notes said only "bug fixes and improvements", versus 44% across all apps, leaving readers unsure whether a reported issue was fixed.
The signal is not that every travel app is unusually buggy. It is that the leading malfunction in this sample affects a high-stakes step in booking.
What breaks
| Malfunction | Travel and tickets | All 187 apps |
|---|---|---|
| Payment and UPI failures | 4.3% | 1.4% |
| A feature doesn't work | 2.4% | 3.3% |
| Login and OTP failures | 2.0% | 1.8% |
| Crashes, freezes, won't open | 1.6% | 2.3% |
| Slow or laggy | 1.2% | 0.9% |
| Wrong or stale data | 1.2% | 1.0% |
Share of each category's storefront reviews that describe each kind of malfunction.
- Payments stand out: 4.3% of travel reviews mentioned a payment or UPI failure, compared with 1.4% across all apps. Crashes were less common in travel reviews than in the full sample.
- Other issues can block the same journey: Login or OTP failures can stop checkout; broken features can interrupt search or booking. Slow screens and stale data add uncertainty when fares, seats or departure times may be changing.
- Different symptoms need different checks: A failed payment, an unresponsive booking button and an incorrect status can all leave someone without a ticket, but may have different causes.
These are shares of storefront reviews, not estimates of how often users encounter each problem.
Why payments fail inside travel apps
Paying and getting a ticket are separate steps. A travel app may hold a seat or fare, send the traveller to a payment gateway or UPI app, then wait for the airline, railway or bus operator to confirm the booking. Payment can succeed while booking is still pending or fails. Returning from another app can make that gap harder to understand.
Reviewers described debits without confirmed bookings, duplicate debits, unclear Pending statuses and slow refunds. Two paraphrased examples from the report:
- IRCTC Rail Connect (Sep 2026): money was deducted twice, the ticket showed failed and the refund took five days.
- Yatra (Nov 2025): the hotel booking amount was debited, but the booking was not confirmed.
Pending does not always mean something is broken. The problem is when the app does not make the outcome clear. If it shows Failed despite a visible debit, should the traveller try again? If it shows Pending, how will they know whether to book elsewhere?
The cause may lie with the app, bank, payment network or booking provider. Testing should cover the whole journey, especially delayed or conflicting responses, and check whether the traveller can see what happened and what to do next.
What the storefronts showed
| App | Rating | Reviews read | Malfunction reviews | Main problem |
|---|---|---|---|---|
| IRCTC Rail Connect | 3.6★ | 18 | 8 | Payment failures |
| RailYatri | 4.4★ | 18 | 4 | A feature doesn't work |
| Air India | 4.8★ | 6 | 3 | Payment failures |
| Cleartrip | 4.4★ | 18 | 3 | Payment failures |
| Goibibo | 4.6★ | 18 | 3 | Wrong or stale data |
| Yatra | 3.9★ | 18 | 3 | Payment failures |
| IndiGo | 4.2★ | 18 | 2 | Slow or laggy |
| ixigo Flights | 4.8★ | 18 | 2 | Slow or laggy |
| EaseMyTrip, ixigo Trains, MakeMyTrip, OYO | 4.2-4.8★ | 14-18 each | 1 each | Mixed |
| AbhiBus, ConfirmTkt, redBus | 4.6-4.8★ | 17-18 each | 0 | - |
The table shows how the visible reviews differed by app, but its columns should not be read as a league table. Air India, for example, had six reviews read, while many others had 18; three malfunction reviews out of six are worth examining, but that small denominator makes a broad comparison especially fragile. Likewise, zero malfunction reviews on show does not mean an app had zero malfunctions.
Ratings provide context, not a substitute for reading the complaint. A high-rated app can still have a review describing a failed checkout, and an app's dominant issue in this small sample may not be its dominant issue across all users. Small samples from one day, and Google changes which reviews it shows: a snapshot, not a verdict on any app.
What to test first in a travel app
Start with the points where the payment record, booking status and on-screen message can disagree. For each scenario, check not just whether the app displays an error, but whether the traveller can tell what happened and what to do next.
- Payment succeeds, booking fails. Use a sandbox where the payment goes through and the booking call times out. The app should say the payment is being checked, not Failed, and show a refund message if it doesn't confirm. Reopen the app and check whether the same transaction still has a traceable status rather than starting the user from an empty booking page.
- No second debit on retry. After a failure or a timeout, tap Retry and count the debits. Then do it on a slow connection with a double tap. Check whether repeated actions create a second payment attempt or whether the app first resolves the original one; the screen should make the risk of retrying understandable.
- The return trip from the UPI app. Pay by UPI, press back before finishing, and kill the travel app while the user is in the UPI app. The booking status should be right when the user comes back. Also test a delayed return: the traveller may reopen the app after the payment is complete but before the booking confirmation appears.
- Session expiry mid-payment. Sit on the payment page past the session timeout, then pay. Check what happens if the held fare or seat can no longer be booked. The app needs to distinguish an expired booking session from a failed payment and avoid presenting an uncertain outcome as final.
- Heavy load when a booking window opens, such as a tatkal-style rush or a sale. Test the queue, the timeouts and what the user sees. Repeat the journey after a timeout to see whether an earlier attempt remains pending, and whether a fresh attempt could create a duplicate charge or booking.
- OTP login on the move, with patchy 4G and a network switch mid-login. Check whether the code remains usable, whether resending it causes confusion, and whether the user can resume the intended booking rather than losing their place.
A useful pass condition across these tests is consistency: the booking screen, payment status and any subsequent message should tell the same story. When they cannot yet do so, the app should communicate that the outcome is still being checked rather than forcing the traveller to guess.
The train ticket booking, payment gateway and UPI payment flows in our free library cover these.
Check your own app
If your team is reviewing a travel booking flow, start by grouping complaints by the outcome users describe: debit without confirmation, duplicate debit, unclear pending status, delayed refund, or a login problem that prevents checkout. Then reproduce the full path from search to ticket, including interruptions outside the app. A review may identify the symptom clearly even when it cannot identify which system caused it.
Read the full travel and tickets breakdown, or scan your own reviews with the free Play Store bug scanner. The travel booking app cost page shows what a release check costs. 99tests testers run your booking and payment cases on their own phones and networks, with a verified report in 3 business days, from ₹9,999 + GST.