A hotel message arrives while your group is still debating trains and dinner. It has the right name and dates, but asks for a payment or an update you were not expecting. The awkward part is deciding whether to act—and whether everyone else needs to get involved.
For a shared Tokyo trip, a useful plan gives the person holding the reservation a way to check without carrying every decision alone. Start with the request in front of you; the dated hotel notices below provide context, not a verdict on your booking.
Open the service you booked through independently. Compare the request with your original reservation before replying or paying.
The conversations below are editorial planning examples.
EmmaIt knows our hotel and dates. That makes it feel convincing.
MinaminaIt does—but matching details do not authenticate the request. Open your booking independently and check what is being asked.
Three checks before you reply
| What arrives | What to check | Next action |
|---|---|---|
| Urgent payment or update request | Original payment terms and reservation status | Open the booked service independently |
| A familiar hotel name and dates | The request itself, not just matching details | Use contact details obtained independently |
| A forwarded screenshot | What is confirmed and what remains unresolved | Ask one person to verify, then share the result |
A deadline needs checking, too. Do not enter personal or card details through a suspicious link. A genuine deposit deadline may still apply to your reservation: compare it with the original terms instead of assuming that every request is fraudulent—or that urgency proves it is genuine.
If card details have already been entered
EmmaSomeone has already entered their card details. Should we wait until everyone has read the message?
MinaminaContact the card issuer promptly through a verified route and follow its instructions. Report the message to the booking provider as well; the group discussion can wait.
If you booked through Booking.com, its traveller safety page explains provider-specific reporting and account guidance. It is an official help resource, not a reservation or payment link.
Share the checking, not the uncertainty
Forwarding a screenshot may alert everyone, but it can also leave several people wondering whether someone else has replied. A clearer handover names the checker and keeps the request marked as unverified until there is an answer.
EmmaI want someone to double-check, without sending everyone through the same link.
MinaminaShare what needs checking and who is handling it. Then pass on the confirmed answer and the official channel used—not an invitation to follow the message’s link.
Keep a record of what arrived without using its link to sign in or pay.
Use the app or website you booked through, or independently find the hotel’s official contact route. Compare the request with your confirmation.
Record who checked, which official channel answered and what action was confirmed. Keep unresolved requests clearly marked.
A backup is more useful than a family job title. Choose someone who is available and comfortable with the booking service or language involved. Age does not tell you who that will be, and sharing the task does not require sharing account passwords.
What the Tokyo hotel notices actually say
In its 29 October 2026 update, karaksa hotels lists TOKYO STATION among affected properties. The stated reservation conditions are bookings made on or before 21 September 2026 for stays on or after that date. The notice says booking details may have been exposed through its reservation-system provider; it does not say every future Tokyo booking is affected. Read the current notice for your circumstances.
A separate The Okura Tokyo notice describes messages threatening cancellation unless information is updated. These are property-specific notices, not a finding that all hotels or all booking messages are compromised.
- Original confirmation and payment terms are accessible.
- An independently verified hotel or booking-provider contact route is saved.
- A checker and backup know who is handling the request.
- Forwarded messages distinguish unverified requests from confirmed answers.
For the separate question of arriving after reception hours, see AGI’s Tokyo late-arrival guide.
