Setu generated 7,394 single-use UPI links and dynamic QRs for RedBus between Sept 15 and Oct 4. 898 users dropped off before scanning or opening their UPI app (12.14% pre-scan drop rate). The remaining 6,496 checkouts attempted at the bank switch converted at an exceptional 95.67% SR.
4. Bank Switch Failure Taxonomy (281 Attempted Drops)
5. Multi-Channel Action Items & Recovery Playbook
1. Eliminate Dynamic QR on Mobile Web (mWeb) — Force Intent
898 users abandoned generated checkout links before attempting payment. Rendering QR codes on mobile web forces customers to take screenshots and upload them to scanner apps, creating fatal friction.
Action: Detect mobile user-agents and automatically invoke native UPI intent (upi://pay), bypassing QR code generation entirely on mobile browsers.
2. Automated WhatsApp / SMS Checkout Recovery for >₹2,000 Fares
Pre-scan drop-offs jump to 13.4% on Long Haul (₹2k–₹5k) and 14.8% on Premium (₹5k+) tickets (₹3.66 Lakh unrealized GMV).
Action: If a generated link remains unattempted after 90 seconds, dispatch an automated WhatsApp / SMS payment nudge before the seat reservation expires.
3. Dynamic Fallback to RuPay Credit on UPI for Insufficient Balance (Z9)
60.85% of bank attempt failures (171 drops, ₹2.22 Lakh lost) are due to Z9. RedBus already enjoys a 94.42% conversion rate on Credit on UPI.
Action: When Z9 is returned, trigger an instant bottom sheet: "Account balance low. Complete booking using RuPay Credit on UPI" without losing the bus seat.