Proposal Checkout

When a client accepts one of your individual (non-group) proposals, they now move through the same guided, agency-branded checkout your group booking pages use: Trip → Your details → Payment → Confirmation. Instead of a single "Approve" button, the client picks their option and is walked step by step through confirming their trip and authorizing the deposit — no account, no password, no back-and-forth.

This is the standard experience for standard and split-bundle proposals. Group bookings have their own version (see Group Booking Checkout).

What Your Client Sees

When your client opens the proposal link, they land on your branded proposal — hero photo, your agent note, and the option cards exactly as you built them. This first page is unchanged: they browse the options, open the detail card to read the overview, itinerary, and photos, and compare prices.

Once they've chosen an option (and any add-ons), a "Continue to booking" button drops them into the guided checkout. A numbered stepper appears at the top — Trip · Your details · Payment · Confirmation — and a persistent "Your trip" cost sidebar on the right shows a running total and a highlighted "Due today" box.

Step 1: Trip

This is the proposal page itself — your hero, options, and detail card. The client:

• Picks an option — for a standard proposal they choose one package; for a split-bundle proposal they pick one option from each category (hotel, flight, excursion, etc.), and the cost sidebar lists each selected piece as its own line.
• Toggles add-ons — any optional extras you configured adjust the total live.

When they're happy, they click Continue to booking to move into the details step. They can click ← Back at any point to return here and change their pick.

Step 2: Your Details

A guest checkout — no account required. The client fills in:

• Lead traveler — name, email, and phone. If the client is already in your CRM, their name is pre-filled from the household.
• Each additional traveler — name plus any Required Traveler Info you configured on the proposal (date of birth, passport number, nationality, gender, etc.). The same required fields are collected for the lead traveler too.
• Passport scan — when you ask for passport details, each traveler has a Scan passport button that reads the passport photo and auto-fills the fields, so the client doesn't have to type them.
• Driver's license photo — turn this on when you want a photo ID for trips that don't need a passport (domestic travel, cruises) or to verify identity for a card transaction. The lead booker adds one photo of their license, and it's kept on file under the trip's Documents tab. See below.

Collect a driver's license photo

In the What to collect section of the proposal builder, toggle Collect a driver's license photo. When it's on, the primary booker is asked for a photo of their license at checkout.

• It's collected from the primary booker only, not every traveler.
• The image is stored on file — it shows up as a "Driver's License" entry under the trip's Documents tab, where you can open it to verify identity. (This is different from the passport scan, which reads the photo to auto-fill fields and then discards it.)
• Flip on Require the license photo to make it mandatory before the booker can continue. They can still choose I'll add it later so a phone camera glitch never blocks the booking — if they defer, request it afterward.

There's no AI reading here; it's a straight photo capture, so the saved image is what you check against.

Collect a field from the primary traveler only

In the What to collect section of the proposal builder, each field has a Collect from control next to its Required toggle:

• All travelers (default) — the field is shown for the lead and every additional traveler.
• Primary only — the field is shown for the lead traveler only and hidden from the additional travelers entirely.

Use Primary only when you need a detail from the booker but not the rest of the party, for example a mailing address. The Required toggle still applies to whoever the field is collected from, so "Primary only" plus "Required" means the lead must fill it in and the additional travelers never see it.

• Travel insurance — if you enabled insurance on the proposal, the full insurance panel appears here. Depending on how you configured it, the client can request a quote, accept or decline coverage, and (when you require it) must explicitly decline before continuing.
• Terms acceptance — the client accepts your booking terms. If you set acceptance to typed signature, they type their full name to sign; otherwise they check a box.

Required fields are enforced — the client can't advance until every traveler's required details are complete.

Step 3: Payment

The client reviews their booking summary and the "Due today" amount before entering any card details.

• Deposit or pay in full — when a deposit is configured, the client chooses Pay deposit now or Pay in full. The "Due today" amount updates to match their choice.
• Secure card page — clicking the payment button takes the client to a secure, PCI-certified card page to authorize their card. Credit cards and gift cards are both accepted.
• No money moves at acceptance. The card is authorized, not charged — the client's card details are stored in PCI-certified infrastructure and you charge the card yourself when you're ready to collect, exactly as with any card authorization. The client sees a clear note explaining this.

If your proposal collects no deposit online, this step becomes a simple "Confirm booking" step with no card entry.

Tip: The deposit "Due today" is resolved from your proposal's deposit settings (percentage, fixed, per-person) plus any add-ons you flagged as due at booking — the client sees the exact figure before they commit.

Step 4: Confirmation

After the card is authorized (or the booking is confirmed), the client sees a confirmation screen, and the proposal is marked Accepted on your dashboard. You receive a notification, and the traveler details the client entered are saved to the trip so you can pick up the booking.

A Note on Planning Fees

If your proposal charges an upfront planning fee, that proposal continues to use the existing approval flow (which handles the Stripe planning-fee payment and 3-D Secure) rather than the guided checkout. Everything else about how you build the proposal is unchanged.

Availability

The guided proposal checkout is on by default for all agencies. It applies to standard and split-bundle proposals. Document-only proposals, add-on offers, external-checkout (Book Now) links, and proposals with attached forms or a planning fee keep their existing flow. You don't change anything in the editor — you build options, add-ons, deposits, required traveler info, insurance, and terms exactly as before, and this is simply what your client sees on the public side of the link.

Undo an Accidental Acceptance

It happens: you click through your own preview link, or a proposal gets marked Accepted before you meant it to. Accepting a proposal kicks off a chain of automatic work — a pending deposit payment, a draft invoice, and a card-authorization request are all created for you — so simply flipping the status back to draft would leave those orphaned records behind.

Undo acceptance cleans them up. Open the proposal, click the ⋯ menu in the top-right, and choose Undo acceptance (it only appears while the proposal is Accepted). After a confirmation prompt, the proposal returns to Sent so the client can approve again, and the records the acceptance created are removed — but only the ones nothing has happened to yet:

• The pending deposit payment is deleted — unless you've already collected it.
• The draft invoice is deleted — unless it has been sent, viewed, or has a payment on it.
• The pending card authorization is removed — unless the client has already entered a card or it has been authorized or charged.

Anything that has seen real activity is left untouched, and the toast tells you exactly what was cleared.

What it deliberately keeps: the trip itself (including any edits you've made), the seeded itinerary, the travelers on the booking, and any lead-to-client conversion. When the client re-accepts, the itinerary and travelers reconcile in place rather than duplicating, so undoing and re-accepting is safe.

FAQ

Does my client need an account to accept? No. The whole checkout is guest-only. They enter their contact details in Step 2 and receive confirmation by email.

Is the client's card charged when they accept? No. The card is authorized and securely stored — you charge it yourself later from the trip's card authorization. No money moves at acceptance.

Can the client pay the full balance instead of the deposit? Yes — Step 3 has a Pay in full option alongside Pay deposit now. Their choice is passed to you so you can collect the full amount instead of just the deposit.

Can they still decline? Yes. The Decline option remains on the proposal's first page; the guided checkout is only entered when they choose to move forward.

What if I requested passport or date-of-birth details? They're collected per traveler in Step 2, and the Scan passport button auto-fills them from a passport photo. The details save to the trip when the client accepts.

Does this change how I build proposals? No. You set up options, add-ons, deposits, insurance, required traveler info, and terms the same way in the proposal editor. This is the client-facing experience, not an editor change.