Express Checkout for airlines
Express Checkout puts an “Express Checkout” button on your booking page that takes the traveler to Movmo’s checkout and back to your page. Travelers pay with the passengers and cards already saved in their Movmo account.
The key principle
Section titled “The key principle”The traveler checks out with the profile and payment method they already keep at Movmo. The booking is created in your PSS under your PNR, and your PSP stays merchant of record.
How it works
Section titled “How it works”| Step | What happens |
|---|---|
| 1. Click | The traveler clicks the button on the step where they have selected a flight. |
| 2. Offer saved | The button saves the selected offer to Movmo (or uses an offer id your backend saved earlier). |
| 3. Checkout | The tab navigates to Movmo’s checkout page, which collects sign-in, passengers and payment. Your page never sees card data. |
| 4. Booking | Movmo books the offer in your PSS and forwards the vaulted card to your PSP. |
| 5. Back to you | ”Return to {airline}” sends the tab to your returnUrl; your onBookingComplete callback receives bookingId and airlinePnr, then onExit fires. |
What you build vs. what Movmo provides
Section titled “What you build vs. what Movmo provides”| You build | Movmo provides |
|---|---|
| The button on your selected-flight step (React component or one script tag) | The checkout UI, sign-in and traveler accounts |
| The offer you already have, passed as-is, or saved server-side at flight selection when it is not in the browser | Offer conversion for each supported provider |
A return page that loads the button (or consumeReturn) on the returnUrl | Card entry and vaulting, forwarding to your PSP |
An onBookingComplete handler that keys your record on bookingId and stores airlinePnr when present | The booking call to your PSS and the traveler’s confirmation email |
An onExit handler that returns the traveler to the right step | Consent, receipts and the traveler’s self-service account |
Details: What you build.
Onboarding checklist
Section titled “Onboarding checklist”- Contact Movmo. Book a call at movmo.io/book-a-demo or reach out through your existing Movmo contact.
- Receive your credentials. An API key, your
iataCode, and your provider id. If you have no live provider connection yet, you get the sandbox provider id for e2e instead. - Register your origins. Every origin that hosts the button or your
returnUrl, production and staging. Identity partners get this automatically from their redirect-URI origins; see Where it can run. - Install.
npm install @movmo/express-checkout-button@^2.0.0, or one<script>tag on a non-React site. See the package reference. - Build. The button on your selected-flight step, a return page, and
onBookingCompleteandonExithandlers, per the integration guide. - Verify on e2e, then set
isProd: truewhen you go live. See Going to production.
Also give Movmo a security contact. Ours is security@movmo.io.
What travelers see
Section titled “What travelers see”The traveler leaves your page for Movmo’s checkout page, where they sign in with an email code or a passkey, pick or add passengers and a card, and book; Return to {airline} brings them back. The screens are under What your users see.