Before paying a foreign hotel through a link described as UPI, verify two things separately: who will receive the money, and whether your app and bank support this exact payment route. Ask the hotel through an independently established channel to connect the displayed beneficiary to your booking and invoice. A familiar app, working link or plausible recipient name is not proof of that connection. If the collector or route remains unexplained, pause and ask for another verified payment option.
AI-generated fictional photographic scene of an Indian couple reviewing a phone and blank booking paper in an unbranded hotel lobby. It is not a real hotel, payment screen or transaction.
Identify the route before checking the name
A message saying "UPI accepted" could describe an overseas merchant QR, a domestic collector's UPI account, or a checkout page that offers several payment methods. Ask which company collects the deposit, in which currency, for which hotel and booking, and how the hotel will credit it. Do not treat these routes as interchangeable, or assume a remittance facility is a hotel merchant-payment facility.
PhonePe's UPI terms describe UPI International for travellers paying merchants in select locations through a QR payment flow. They also describe activation from India or abroad. Activation location does not establish that a remotely supplied foreign-hotel QR or link is a supported payment method. Support for this particular remote transaction remains unconfirmed here. Ask your app or bank through its genuine support route; do not work around a rejected flow by changing the recipient, splitting payments or following a stranger's instructions.
Connect the beneficiary to the hotel's actual collector
Open the booking platform or hotel's established website independently, rather than using the contact details in the payment demand. Ask the hotel to confirm the legal collector or trading name, the beneficiary you should see, the deposit amount and currency, the booking reference, and how the payment will be acknowledged. If a processor or agent collects for the property, ask for a written explanation of that relationship and confirm it through the established hotel or platform channel.
The NPCI consolidated circular dated 18 September 2026, sections 2.6 and 2.14, requires transaction details before authorisation and describes end-beneficiary identity and validated merchant-brand naming. Those are payment-system identification requirements, not a certification that the recipient owns the hotel or is authorised to collect your particular deposit. Compare the app's actual recipient details with the independently confirmed collector. A different name needs an explanation, not an automatic verdict of fraud or automatic acceptance.
Do not ask the person sending the link merely to repeat that it is safe. Ask the established hotel contact to identify the expected beneficiary before you approve anything. A logo, a padlock, a matching booking number or a successful small test transfer is not a substitute for connecting the collector to this booking.
Check the booking obligation as well as the payment address
Compare the request with the original confirmation: deposit versus balance, due date, amount, currency, cancellation terms and who was meant to take payment. Ask how an earlier charge or authorisation is accounted for. A genuine recipient does not prove a second payment is due, and a confirmed reservation does not by itself prove every amount has been collected.
Booking.com's traveller-safety guidance recommends contacting its support if payment requests do not match the confirmation. Its hotel-scam guidance treats requests outside the official payment system as a warning sign. Follow the actual booking's payment terms and get an unexplained change checked, rather than assuming every property collects in the same way.
A familiar hotel messaging thread is not sufficient on its own. Action Fraud's 10 January 2025 alert describes criminals using compromised hotel accounts to send payment requests. That UK alert is evidence of an attack pattern, not a finding about your hotel, an Indian legal rule or proof that all hotel messages are false. For an urgent pay-again demand, use the separate hotel payment-demand checklist.
Read the actual approval, including currency and costs
Only after the collector, obligation and supported route are clear, review the genuine app's recipient, amount and currency before authorising. PhonePe's international terms describe the local-currency amount, an INR amount based on forex rates and markup, and possible issuer processing charges. An INR debit is not evidence of a fee-free payment. Ask your own provider what applies; no universal price or cheapest method is established here.
A UPI PIN may legitimately be used inside the genuine app to activate a supported feature or authorise a payment. Never tell it to hotel staff or a caller, enter it on an unexplained web page, or give remote access to complete the transaction. PhonePe's terms require keeping the PIN and OTP confidential. Do not approve a payment because someone calls it "verification" or says it is needed to receive a refund.
Keep one payment trail, and stop if anything changes
Privately retain the original request, invoice, confirmed collector relationship, booking reference, amount/currency, actual transaction status and payment reference. Ask for a receipt showing which booking and deposit it covers and the remaining balance. A screenshot sent by the requester is not your own bank record, and an app debit alone should not trigger a second blind payment if the hotel says it cannot see it. Check the provider's status and reconcile with the collector first.
If the payee, amount or route changes after confirmation, pause and verify the change independently. If you suspect fraud or have authorised an unintended payment, contact your bank or payment provider promptly through its genuine support route and preserve the evidence. No refund, cancellation protection, dispute deadline or recovery outcome is guaranteed here.
Reviewed 14 November 2026 against the primary sources linked above, including PhonePe's 7 February 2023 launch announcement, used only for historical context, not today's merchant coverage. Current revision dates were not established for the undated PhonePe and Booking.com guidance. No particular hotel, payment link, collector relationship or remote cross-border UPI eligibility has been authenticated. This is a verification checklist, not an instruction to send money.
A Miranda House graduate and lawyer who traded courtrooms for slow travel. Cheshta travels with the batches we host ourselves, with a soft spot for travelling alongside elders.
Planning your next trip?
We'll handle insurance, hotels, airport assistance and the itinerary — the same way we do it for every trip.
Questions on this article
asked by readers, answered by us
Was this helpful?
one tap, no sign-up