Product Design
A concept redesign of Airbnb’s booking flow. Guests could see what they’d pay today, but not when they’d be charged or what they’d lose if they cancelled. I rebuilt how money is explained across the listing card, Request to book and the cancellation pop-up, without changing a single price or rule.
The problem in one line
What the guest sees
“€0 today · Free cancellation before December 6.” The good news leads every screen.
What the guest has to work out
When the €200 is charged, and that cancelling between Dec 6 and Dec 11 means €50 back and €150 lost. That figure appears nowhere in the flow.
Why it matters
Money is where trust is decided. A guest who can’t answer “what if I cancel?” either hesitates at checkout or feels misled later.
It’s real and checkable
I walked the live flow on airbnb.com on 31 Oct 2026, signed out, for one Helsinki listing. Every “before” screen on this page is a capture of that walkthrough.
It’s where money meets trust
Choosing when to pay is the moment a guest decides whether to hand over €200. Confusion here costs bookings now, or creates angry cancellations later.
It changed recently
Reserve Now, Pay Later launched in August 2025 and cancellation policies changed in October 2025. New payment logic on top of old explanations is where clarity tends to break.

Listing card
The headline is the good news: “€0 today · Free cancellation before December 6”. What you’d lose after that isn’t on the card.

Cancellation policy pop-up
The refund rule is in percentages: “Get back 50% of every night but the first one.” The guest has to do the maths to find out it’s €50.

Request to book
Three ways to pay. The charge date sits in small grey text under one option; the refund deadline sits in the side card.

Pay later details
The only reminder in the flow is for the charge. Nothing reminds the guest before free cancellation ends.

Real walkthrough
Walked airbnb.com from search to the payment step and captured every screen.
Task check
Two questions a guest asks: “When am I charged?” and “What do I get back if I cancel on Dec 8?” I tracked where each answer lives.
Heuristic review
Nielsen’s heuristics on each step, mainly visibility of system status and recognition over recall.
Public record
Airbnb’s own announcements and industry coverage of pay later and the 2025 policy changes.
Pay later is new
Reserve Now, Pay Later launched on 14 Aug 2025 for US guests and later worldwide. Payment is due shortly before free cancellation ends. Source: Airbnb Newsroom.
Flexibility matters to guests
In Airbnb’s own survey, 60% of US adults said flexible payment options matter. Source: Airbnb × Focaldata, July 2025, 2,159 adults.
The rules just changed
On 1 Oct 2025 Strict was retired in favour of Firm, a new Limited tier arrived, and the free window went from 48 to 24 hours. Source: Rental Scale-Up.
Insight 01
The page sells “€0 today”. The real commitment shows up later, somewhere else.
Insight 02
Refunds are written as percentages. Guests think in euros.
Insight 03
Four dates, five places, no single timeline.
Insight 04
Pay later moved the risk later, and only the charge gets a reminder.
It worked if
More guests can answer “when am I charged?” and “what if I cancel?” correctly, and fewer leave Request to book after opening the cancellation policy.
It’s wrong if
Guests answer correctly but book at the same rate, which would mean clarity wasn’t the blocker, or the extra information slows booking down.

01 · Listing card
Before

After

Why
The good news stays, it just isn’t alone. Both refund windows sit on the card in euros, so the first thing a guest learns is the real deal: full refund until Dec 6, then €50 back.
02 · Request to book
Before

After

Why
This is where the guest decides how to pay, so every date belongs here. One timeline shows each charge and each refund in euros and updates with the payment option, Klarna included. An opt-in reminder lands the day before free cancellation ends.
03 · Cancellation pop-up
Before

After

Why
Same pop-up, opened from the same places: “See what you’d get back” on Request to book, or “Show more” on the listing. Instead of a rule to decode, the guest picks when they might cancel and sees what they get back and what they lose. The host’s policy is still quoted word for word.

1) Usability test first
Five to eight guests book this exact listing in the current flow and in the redesign, then answer “When will you be charged?” and “What do you get back if you cancel on Dec 8?” I’d measure correct answers and time to answer.
2) A/B test if it holds
Split traffic on Request to book. Primary metric: booking completion. Guardrail: time to book. Secondary: cancellation-related support contacts and refund disputes per 1,000 bookings.
3) What would change my mind
If guests answer correctly but still don’t book, price or trust is the blocker, not clarity. If completion drops, the timeline adds friction and should be collapsed by default.





