Two Confirmations for One Stay: Who Owns the Refund?

A retried request can create a second reservation. Working out who refunds whom is a sequence, not a negotiation.

Last updated: October 24, 2026

A guest taps book, the request times out, they tap again, and now two confirmations exist for one stay. The refund isn't a matter of goodwill or haggling. It's a question of three things in order: which confirmation the guest will actually use, which side is holding the money, and which cancellation costs least. Answer them in that sequence and the case closes in an afternoon.

Key Takeaways

• Don't call it a duplicate yet. Until you know which confirmation the guest intends to use, both are live and one of them is somebody's booking.
• The refund follows the payment. A refund can normally only be issued by the party that took the money, and that party is set by the channel's terms.
• Order the cancellations by cost. Cancelling the more expensive one first is often the cheaper decision, and it's never the obvious one.
• Never cancel both to start clean. The dates may not come back, and the second cancellation is a second charge.
• One written sequence saves the next hour. The same retry pattern will happen again, on a different night, to a different guest.

How a second confirmation appears

The most common shape is a retry. The guest's first request doesn't return a clear answer — a timeout, a spinner that never resolves, a payment step that hangs — so they submit again. Sometimes the second attempt is on the same channel. Sometimes it's on a different one, because they gave up and went looking elsewhere.

From your side, both arrive looking legitimate, because both are. Each has a reference number, each has a rate, and each has a policy attached. They may not agree on any of those. A retry that crosses channels can land a flexible plan against a non-refundable one, or a rate that changed between the two attempts.

There's a second shape that catches hosts out: the confirmation arrives late. The channel accepted the booking on the first attempt and delivered it after the guest had already booked again. In that case the "second" confirmation is actually the first one, and the timestamps in your inbox will tell you so if you read them.

Whatever the shape, resist the word duplicate for the first ten minutes. It's a conclusion, not an observation, and it pushes you toward cancelling the wrong one.

Who is holding the money

This is the question that decides everything else, and it's the one hosts answer from memory. Don't.

Ask it in three parts. Did the channel charge the guest, or did it only take a pre-authorisation? Is the booking prepaid to the channel, prepaid to you, or paid at the property? And has either payment actually settled, or is one of them still pending?

The answers split the case cleanly. If one confirmation is prepaid and the other is pay-at-property, you probably hold no money at all on the second one, and there's nothing for you to refund — you cancel it and the guest's card is never touched. If both are prepaid through the same channel, one refund is likely to be a channel-side action, and your job is to give them the reference and the reason.

If the two confirmations came from different channels, expect to deal with two support queues, two policies and two refund timelines. Nothing about the first one's goodwill transfers to the second.

Who owns the refund depends on the channel's terms. That's not a dodge — it's the actual mechanism. The party that captured the payment is the party that can release it, and the window, the fee and the form all come from the policy attached to that specific confirmation.

Cancelling the one that costs least

Establish intent first, in writing. One message to the guest: two confirmations exist, here are both reference numbers, which one are you arriving on? Ask for a reply by a stated time, because a held second booking is a night you can't sell to anyone else.

Then price both cancellations, not both refunds. Read the policy attached to each confirmation and write down what cancelling it today would cost — a fee, a percentage, nothing, or a full forfeit. Those four outcomes are what you're choosing between, and they're rarely symmetric.

localsbnb.com keeps the four connected channels — Airbnb, Booking.com, Agoda and Trip.com — in one calendar, with each channel's source rate and status beside the dates. When two confirmations land on the same nights, that's where the collision shows up: one set of dates carrying two arrivals, which is the moment to act rather than the moment to hope.

Cancel in this order. The confirmation the guest won't use goes first, and of the two, always the one whose cancellation is cheaper today. If both are free to cancel, cancel the later-issued one and keep the guest's original arrival details intact. If both carry a fee, cancel the cheaper one and then argue the second fee with the channel separately, with both references in the same message.

What you don't do is cancel both and invite the guest to rebook. The dates may be gone by the time they try, the rate may have moved, and you'll have converted one awkward conversation into an availability problem.

If both confirmations are non-refundable, stop before you touch either. That's a channel decision, not a host decision, and a cancellation you initiate may be the one that forfeits the money.

Writing it down before it repeats

The retry will happen again. Not necessarily to this guest or on this channel, but the mechanism — a slow response, an impatient tap, a late delivery — is structural. A short written record is what turns the second occurrence into a ten-minute job.

Record six things: both reference numbers, the timestamps of both confirmations, which channel each came from, what each policy said about cancelling today, which one was cancelled and what it cost, and who issued the refund. Add one line on what the guest was told, and by whom.

Keep it somewhere you'll find it under pressure — a single running note rather than a folder of screenshots. Screenshots don't age well and can't be searched. In eighteen months, the useful artefact is a sentence that reads: two confirmations, one cancelled free, one refunded by the channel in five days.

There's a second use for the record. If the same channel produces the same pattern twice in a season, you have evidence rather than an impression, and a support conversation that starts with two dated examples tends to move faster than one that starts with a feeling.

FAQ

Should I just cancel the newer confirmation?

Not automatically. Age isn't the deciding factor — the guest's stated intent and the cancellation cost are. A later confirmation can be the one they're actually arriving on, especially when the first attempt's delivery was delayed.

Can't the software refund the guest for me?

No, and you shouldn't expect it to. A refund has to come from whoever captured the payment, and that's set by the channel's terms. What a calendar can do is show you the collision: the same nights carrying two arrivals, across the four connected channels, with each channel's source rate and status beside the dates.

What if the guest won't say which one they want?

Ask once more with a deadline, and say plainly what happens if the deadline passes. Holding both is the worst of the options, because you're carrying an unsellable night and a second cancellation fee that keeps growing. If the guest stays silent, keep the confirmation they arrived on and cancel the other at the cheapest available moment.

None of this needs a policy document. It needs an order of operations, applied the same way every time, and a note afterwards. When the next pair of confirmations lands, localsbnb.com is where the two arrivals meet on one set of dates, and the sequence above is where the conversation starts.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Payment timing, cancellation costs and refund routing depend on the channel's terms and on local consumer rules, and both change. Confirm the current terms of the channel that issued each confirmation before you cancel or promise a refund.