Ask the travel portal for the refund-specific bank or network trace reference, not only the booking number or its internal refund ID. The useful reference depends on the actual payment route: it may be an ARN, RRN, STAN, UTR or another supported reference. First confirm who collected the payment, where the refund was sent, its amount, currency, processing date and current status. A portal label saying "processed" does not by itself prove a visible bank credit.
AI-generated fictional photographic scene of a daughter and mother reviewing blank papers beside a laptop and luggage. It is not a bank screen, refund record or evidence of payment.
Start with the original payment, not the booking label
Privately match the booking to the actual debit. Record the collector shown on the statement, payment method, date, amount and currency, and masked account or card identifier. Ask whether the refund goes to that payment route, a portal wallet, another balance or a different agreed destination. Do not expect a savings-account credit until the provider identifies where it sent this refund.
Who collected the money matters. Booking.com's partner guidance applies specifically when a property handles payments itself and Payments by Booking.com is not enabled. It says the property handles that refund through its own payment tools. That is not a rule that every portal booking is refunded by the hotel, or that every portal took the money.
Request the record behind "processed"
Ask the responsible collector for the refund amount and currency, date, current payment-team status, internal refund ID and available bank/network reference. Ask whether the status means requested, submitted to the payment provider, completed, reversed, rejected or returned in that system. Do not translate all providers' labels into the same stage.
If the booking had several charges, travellers, deductions or partial refunds, ask which original payment and amount each refund covers. Keep each attempt on a separate line. A full booking total is not necessarily the amount sent in one refund, and a service cancellation acknowledgement is not the transfer record.
Which reference should you ask for?
Razorpay's customer-refund documentation distinguishes its refund ID from a banking reference such as RRN, ARN or UTR, which the customer can take to the bank to trace the refund. Its tracker also accepts certain payment, refund, order or booking IDs. An identifier useful in a processor's tracker is not automatically the reference an issuer needs. This is a Razorpay example, not proof that your portal uses Razorpay.
Stripe's refund documentation describes card references including an Acquirer Reference Number (ARN), System Trace Audit Number (STAN) or Retrieval Reference Number (RRN). For local payment methods it describes references generated by Stripe or financial partners and passed to the receiving institution. Ask the collector for the available refund-specific reference and its type. Do not insist that every payment method must produce the same identifier.
Ask whether a supplied number belongs to the original debit, this refund, the portal's support case or a bank complaint. Keep all useful IDs, but label them. Do not invent an ARN from a booking number, call a complaint number proof of receipt or assume one successful partial refund proves another arrived.
No ARN or separate credit? Check the operation before alleging failure
Stripe's technical documentation says some references become available later, some partners do not support ARNs, and an early refund may be a reversal: the original charge drops off rather than a separate credit appearing. It says an ARN is unavailable for that reversal. Its broader ARN explainer, updated 23 September 2026, uses more general language about refund ARNs. Keep the technical exceptions attached rather than reading the explainer as "every refund must have an ARN".
Ask the payment team to identify whether this case is a refund, reversal, pending attempt or final failure, and provide the relevant evidence. Check the original debit as well as later credits. No ARN alone proves neither success nor dishonesty. Razorpay's error guide is another processor-specific reason to distinguish a failed request from a successfully processed refund. It does not establish an automatic alternative payout for your booking.
Give the bank a short, consistent trace request
Use the bank or issuer's verified private support route. Provide the original debit, collector, refund amount/currency/date, reference type and value, and the portal's current evidence. Ask whether it can locate the credit, whether it was received, returned or posted elsewhere, and what next step applies. Request a bank case number and expected response date. Keep the portal and bank timelines together without sharing passwords, PINs, OTPs, CVV or unnecessary full account records.
If the bank cannot locate it, ask the collector's payment team to trace its side and reconcile the result. Do not replace that work with repeated requests for the same booking ID. If a dispute is appropriate, ask the issuer for the correct reason, evidence and deadline. Do not promise recovery or wait through a made-up universal period. Tell the issuer about a later merchant credit so the same loss is not recovered twice.
Provider estimates are not one common clock. The Booking.com partner-booking guest FAQ gives different processing estimates in different cancellation answers; those do not establish a fixed deadline for every portal, bank or payment method. Ask for the applicable estimate and escalation route for this payment. A pending refund does not by itself change what an issuer says is payable on a bill.
If the original card account was cancelled, use the separate cancelled-card refund guide: tracing the merchant credit and paying out a card credit balance are different jobs. For a normal portal refund, do not request a replacement card or change the destination merely to force a trace.
Reviewed 14 November 2026 using the six primary pages linked above. No particular portal refund, bank posting, payout route, fee or resolution deadline is confirmed here. This is a reconciliation workflow, not a refund-entitlement ruling or authority to buy, pay or open a dispute.
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