What happens when a guest's retreat payment fails

When a card is charged months after the guest saved it, a few things commonly get in the way:

• The card expired or was replaced after fraud or loss
• A spending or daily limit, or not enough money on a debit card that day
• The bank flagged an unexpected charge from abroad
• The bank asks the guest to confirm the payment themselves

Almost none of these mean the guest has changed their mind. They mean the guest needs to be told quickly and given an easy way to pay.

An installment due on 3 March, with retries 1, 3 and 5 days after the due date and a 14-day grace period:

If the guest pays at any point before the release, by updating their card or using the pay link, everything carries on as normal and the next installments are charged to the new card.

The first email sets the tone. Keep it short, friendly and practical:

• What happened (“your payment of $375 on 3 March didn't go through”), without guessing why
• One button to pay or update the card
• When you'll try again, and the date the place is at risk
• A way to reply to a person if something is wrong

Avoid words like “failed” and “final notice” in the first message. Save firmness for the email before the release date.

Long enough for a guest to get a new card in the post, short enough that you can still resell the bed. Two weeks suits most retreats. Shorten it close to the retreat, or rely on your final-payment cutoff, which should leave time to resell.

Put the rule in your booking terms: what happens to the place and to money already paid if a payment stays unpaid. A release is much easier to explain when the guest agreed to it at checkout.

With payment links and a spreadsheet, every step above is a task: noticing the missed payment, emailing, checking again, chasing, deciding. It works for a handful of guests. Past that, it's worth having software do the retries and reminders. When forms and payment links stop working.

Banks give a reason when they decline a charge. Roughly, declines fall into two groups, and they need different handling:

Your payment provider sees the reason; your system should use it. There's no point retrying a closed account three times, and no point asking a guest for a new card when their bank simply wants them to confirm.

Keep each one short, with one button. Long explanations get skimmed; a clear link gets clicked.

Decide this before it happens, and write it into your terms. Common approaches:

• Treat the release like a cancellation on that date, and apply your normal refund tiers.
• Keep the non-refundable deposit, refund later installments minus any costs you can't recover.
• Hold the money as credit towards a future retreat for a set period.

The first is the easiest to explain because it's the rule the guest already agreed to. Whatever you choose, apply it the same way every time.

• Remind before every charge, with the card's last four digits, so guests update an old card in time.
• Avoid charging on awkward days. Charging on the same day of the month as the booking keeps it predictable for the guest.
• Make updating a card one click from the reminder and the trip page.
• Watch long plans. A 10-month plan will meet expired cards. Some payment providers and card networks update expiring card details automatically, but don't rely on it.
• Keep the final payment well before arrival, so a last-minute failure doesn't become an empty bed.