Travel Booking Checkout

Review travelers, room or flight details, fees, add-ons, and payment before confirming a trip. This example brings Trip and Travelers together so travelers and booking teams can find the next task without losing context.

It includes representative records such as Harbor House · 3 nights and Flight AI 507 · Economy. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Travel Booking Checkout
Use this template in Figr

Template facts

Screen

Checkout

Primary action

Confirm booking

Pattern

Checkout

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to confirm booking while keeping trip total, travelers and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Trip gives users an obvious place to start.
  • Supporting view: Travelers keeps the related context close.
  • Primary action: Confirm booking stays visible when people need it.
  • First signal: Trip total shows a useful value (1,248).
  • Second signal: Travelers gives additional context (2).
  • Sample record: Harbor House · 3 nights.
  • Next record: Flight AI 507 · Economy.

States worth designing

  • Missing billing details: say what changed, protect progress, and offer a clear next step.
  • Payment method declined: say what changed, protect progress, and offer a clear next step.
  • Price or tax changed: say what changed, protect progress, and offer a clear next step.
  • Payment processing: say what changed, protect progress, and offer a clear next step.
  • Purchase confirmed: say what changed, protect progress, and offer a clear next step.
  • Order confirmation delayed: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Trip → Travelers → Confirm booking → Review outcome

Patterns used

Checkout, Trip, Travelers, contextual actions, error recovery

Why these choices work

Show the final total before payment, validate near affected fields and preserve the order if payment fails.

Pay attention to trip and travelers. People need to distinguish Harbor House · 3 nights from Flight AI 507 · Economy. Keep trip total visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Confirm booking”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Flight Search, Trip Itinerary, Hotel Detail.

Start from this in Figr

Design a travel booking checkout screen inside our existing product. Use our current components, tokens and content language. Include Trip and Travelers views, credible records like Harbor House · 3 nights, and a clear “Confirm booking” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr