The last mile is mobile: how AI-driven direct bookings are won on a phone

Is checkout the only place mobile bookings leak?

No — it’s just where the leak gets measured. By the time a guest reaches your payment step, they’ve survived the property page: a photo gallery designed for a cursor, a calendar widget that wants a hover, a quote that needs a page reload, a total that doesn’t appear until three screens in. Each of those is a form field by another name — friction between intent and confirm — and on a phone inside an in-app browser, each one costs a share of the bookings the AI just sent you.

The OTA apps understood this a decade ago. Their advantage isn’t only the stored card at the end; it’s that every screen before it — browse, dates, price — was built for a thumb from the first pixel. A mobile-native booking path means the whole sequence, not just the last tap: a gallery that swipes, dates that pick in two touches, a live total that shows up early and never surprises, and then — only then — the wallet sheet. Express checkout finishes the job. The shopping flow decides whether the guest is still there to finish it.

What counts as express checkout?

Express checkout means the guest pays with credentials that are already stored and verified somewhere they trust — their device or a payment network — instead of typing them into your form. Apple Pay and Google Pay hold cards at the device level and confirm with Face ID or a fingerprint. Link (Stripe's network) recognizes a guest by email or phone across every merchant that supports it. PayPal works the same way at network level. In every case the interaction collapses to: see the total, confirm identity, done. No card number, no billing address retyped, no account created.

How big is the wallet shift, really?

It’s not a trend anymore; it’s the default. Worldpay’s 2026 Global Payments Report — built on 63,000+ consumers across 42 markets — puts digital wallets at 56% of global e-commerce transaction value, and 40% in the US, ahead of any other online payment method. (Worldpay, 2026) The majority of the online spending world has already stopped typing card numbers. A booking flow without wallet buttons is asking guests to pay the way they paid in 2015.

Why does typed checkout fail on a phone?

Because the form was designed for a keyboard the guest doesn’t have. Baymard Institute’s checkout research — the reference dataset on this — finds the average US checkout presents 23.48 form elements against an ideal of 12–14, and that 18% of US shoppers have abandoned an order purely because the checkout was too long or complicated. Average cart abandonment across 50 studies: about 70%. (Baymard Institute) On a phone, every one of those fields costs more: fat-thumb typos, autofill misfires, the keyboard covering the button. Travel runs worse than retail, and every field you remove is friction gone. Express checkout removes almost all of them at once.

What does AI traffic change?

It concentrates all of this on the hardest surface. More than 70% of AI-referred guests arrive on a phone (Kismet first-party data, H1 2026) — and specifically, most arrive through the in-app browsers of the ChatGPT and Claude apps: WebViews where saved browser autofill is unreliable, cookies are partitioned, viewport quirks punish desktop-first layouts, and a typed form is at its absolute worst. Wallets are the most resilient credential in that context, because they don’t depend on browser autofill or cross-site cookies — Apple Pay rides the device, Link rides the network. The in-app browser degrades the whole session, not just the payment step — which is why the shopping flow has to be built for it too.

And the conversion math is measured, not hypothetical. Stripe ran a controlled holdback experiment across its checkout volume: businesses offering Apple Pay saw an average 22.3% increase in conversion, with digital wallets the standout payment family overall. A separate Stripe study found roughly 2x conversion when Apple Pay is surfaced early in the flow versus buried at the end. (Stripe, 2025) There’s a forward-looking reason too: a wallet-ready flow — tokenized credentials, a structured payment confirmation — is the same shape agent-completed checkout will take. Build for the guest’s thumb today and you’ve built most of what the agent needs tomorrow.

Is this why Airbnb and Booking.com are so dominant on mobile?

It’s a structurally underrated part of it. Airbnb told its shareholders in Q1 2026 that nights booked on its app grew 22% year over year and now account for 63% of all nights booked, up from 58% a year earlier — and credited its app strategy for the momentum. (Airbnb Q1 2026 shareholder letter, SEC) Booking.com has run the same playbook for years. Think about what the app actually is: a logged-in surface with the guest’s card on file, where completing a booking is a biometric confirm. That is express checkout, institutionalized — sitting at the end of a shopping experience designed for the phone from the first screen. The stored credential gets the credit; the flow does half the work.

So when an AI assistant recommends your property and the guest taps through to a form asking for name, email, address, card number, expiry, and CVC — their realistic alternative is an app where the same trip books in two taps. The OTAs didn’t just win supply and brand; they won the stored credential. Express checkout is the independent operator’s equalizer: Apple Pay gives your direct booking path the same two-tap completion the OTA app has, without asking the guest to create anything.

What does "mobile-native" mean for a booking flow?

Eight properties, in journey order. A gallery that swipes — no pinch-zoom, no cursor assumptions. Date selection in two touches, on a picker built for thumbs, with availability visible in the calendar itself. A live total — nightly rate, fees, taxes — that appears early and travels with the guest, so the confirm sheet never surprises. Then the payment step: wallet buttons at the top, not after the form — Stripe’s data says early placement is worth roughly double. Guest checkout by default; no account creation standing between the guest and the confirm. No mid-payment redirects or domain hops — every bounce to an unfamiliar URL resets trust and can break the wallet context. The fewest possible fields for whatever can’t come from the wallet. And the full total — nightly rate, fees, taxes, deposit schedule — visible before the confirm sheet, because a surprise at the Face ID moment is an abandonment. All of it first-party, on your own domain, machine-legible end to end.

Do I have to rebuild my booking engine for this?

No. Like everything else in getting booked through AI, this is a layer, not a replatform. The booking endpoint the AI hands your guest to can be wallet-ready and mobile-native while your PMS and channel manager keep doing exactly what they do today — the PMS stays the system of record, and nothing gets ripped out to start. What matters is that the last tap — the one that turns a recommendation into a reservation — happens on a surface built for a thumb and a stored credential.