Skip to content
Booking Engine

Powering bookings anywhere online — your website, your platform.

Section titled “Powering bookings anywhere online — your website, your platform.”

Hotels put Wink Booking Engine on their own website to turn direct demand into confirmed bookings that sell the whole stay. It’s also the transaction layer the whole Wink platform runs on — so every other route resolves into the same checkout. Payment, confirmation and attribution included.

Your website Your platform 1.5% + processing at cost
book.wink.travel/checkout
Wink Booking Engine checkout — room, rate, add-ons and payment in one flow
Booking Engine mobile checkout

What is Wink Booking Engine?

A full booking engine for your site — and the transaction layer behind every partner.

Section titled “A full booking engine for your site — and the transaction layer behind every partner.”

For your website, it’s everything you expect from a SaaS booking engine: rooms, rates, availability, checkout, payment and confirmation on your own branded site. For your platform, it’s the transaction layer that also converts demand from Wink’s partners, creators and AI agents — all resolving to you, with the hotel in control.

Your website

A complete booking engine, on your own site

Section titled “A complete booking engine, on your own site”

Everything you’d expect from a standard booking engine — your brand, your rates, direct bookings that sell the whole stay. If you’ve run a booking engine before, there’s nothing to relearn.

  • Hotel-branded checkout on your own domain
  • Rooms, rates, availability & policies
  • Payment, confirmation & PMS/channel sync
Your platform

Plus the transaction layer for every partner route

Section titled “Plus the transaction layer for every partner route”

The same engine also powers bookings coming from Wink’s partners, creators, AI agents and developer apps — demand a normal booking engine can’t reach. Every booking still resolves to you: your rates, your inventory, your brand, full attribution. You gain the distribution without giving up control.

PartnersCreatorsAI agentsShareable LinksWinkLinksSocialTravelikoDeveloper apps

Supply flows from Extranet; your rates and attribution stay attached all the way through checkout.

Sell the whole stay

Most booking engines stop at the room. Wink merchandises the whole stay in the same flow — so the average booking is worth more and the guest arrives with the trip already built.

RoomsRate plansPackagesAdd-onsDiningSpa & wellnessExperiencesTransfersUpgradesEarly check-inLate checkout
  • The right room, rate and offer for the route the guest arrived from
  • Live availability and inventory rules from Extranet
  • Cancellation and policy options shown up front
book.wink.travel/rate-plan
Booking Engine rate plan and add-ons — selling the whole stay

The booking flow

The same four steps run behind every route — your website or a partner’s — clean on desktop, built for mobile.

Step 01 · Choose a room

Rooms loaded from hotel-approved supply

The right rooms, photos and availability load straight from Extranet for the route the guest arrived from.

  • Live availability and inventory rules
  • Hotel-controlled content and imagery
  • Dates, guests and occupancy logic
book.wink.travel/rooms
Booking Engine room selection with availability and pricing

Step 02 · Rate plan & extras

Pick the rate, then add to the stay

Rate plans, cancellation options and configured extras — packages, dining, spa, transfers — in the same flow.

  • Meal plans, member rates and promotions
  • Add-ons and experiences where configured
  • Policy and cancellation options up front
book.wink.travel/rate-plan
Booking Engine rate plan selection with extras

Step 03 · Checkout & payment

One checkout, payment collected for the hotel

The guest reviews the stay and pays in a single, hotel-branded checkout — payment collected for the hotel, which stays merchant of record.

  • Hotel-branded, mobile-first checkout
  • Payment collected for the hotel
  • Booking record tied to the hotel and route
book.wink.travel/checkout
Booking Engine checkout and payment summary

Step 04 · Confirmation

Confirmed to the guest, hotel and partner

The booking is confirmed and stays connected to the route, campaign, channel or partner that created the demand — and syncs to the connected PMS or channel manager.

  • Instant guest confirmation
  • Hotel and partner notified
  • Synced to PMS / channel manager, attribution preserved
Booking Engine confirmation screen with booking reference and stay summary

How payment works

Payment and payout, handled for the hotel.

Section titled “Payment and payout, handled for the hotel.”

Payment is collected on the hotel’s behalf, as its agent, and Wink runs checkout, policy and settlement — so the hotel never wires up a processor, and card processing is passed through at cost.

  • Tokenized cards, 3DS and multi-currency
  • Cancellation, deposit and rate-plan policy enforced at checkout
  • Split payouts and partner attribution settled together
1.5%platform fee on confirmed direct bookings, plus card processing at cost — no separate processor contract. See pricing.

How the money moves

  1. 1

    Guest pays in full at checkout

    The full booking amount is captured in the hotel-branded Wink checkout.

  2. 2

    Collected for the hotel

    Collected as the hotel’s agent and held separately, with policy and cancellation logic applied.

  3. 3

    Released at guest check-in

    Funds are paid out to the hotel at check-in, after the 1.5% platform fee, card processing at cost and any commission.

  4. 4

    Partner split — only if applicable

    Direct bookings have no partner. When a partner, creator or AI route created the booking, attribution and payout settle together.

Mobile-first

Most travel demand starts on a phone. Every step — discover, choose, add, pay — is built for it.

Mobile hotel card and availability

Discover

Mobile room details

Choose

Mobile add-ons and extras

Add to the stay

Mobile checkout and payment

Pay

Developers & AI agents

Every Agentic AI handoff and developer integration resolves in Booking Engine — booking creation over REST with OAuth2, 70 webhook events, PMS and channel-manager sync, Web Components, and a hosted MCP server agents can read. Use Wink for payment and settlement, or — on direct API integrations — be your own merchant of record and run payment yourself.

Create bookings over RESTOAuth2 + generated clients70 webhook eventsBooking syncWeb ComponentsHosted MCP serverBe your own merchant of record (API)

Who fulfills here

Booking Engine FAQs

The two jobs, routes, payment and how to build on it.

What is Wink Booking Engine?
Wink Booking Engine is two things at once. For your website, it's a complete booking engine — rooms, rates, availability, checkout, payment and confirmation on your own branded site. For your platform, it's the transaction layer that also converts demand from Wink's partners, creators, AI agents and developer apps — every booking resolving to the hotel, with the hotel in control.
Can Booking Engine sell more than rooms?
Yes. Where configured, it sells the whole stay around the room: rate plans, packages, add-ons, dining, spa, experiences, transfers, upgrades, early check-in and late checkout — not just the room night.
Which routes does Booking Engine fulfill?
Your own hotel website plus every other Wink route: Shareable Links, QR codes, Web Components, WinkLinks storefronts, Social posts, partner storefronts, Traveliko, Agentic AI handoffs and developer-powered apps. They all resolve into the same engine.
How does payment work?
Payment is collected on the hotel's behalf, as its agent, so the hotel stays merchant of record. Booking Engine runs the checkout UI, cancellation-policy logic, tokenized cards, 3DS, multi-currency and split payouts. The full booking amount is collected for the hotel and released at guest check-in, after the 1.5% platform fee, card processing at cost and any commission.
How is Booking Engine connected to Extranet?
Extranet is where hotels manage content, rooms, rates, availability, promotions, policies and channel rules. Booking Engine uses that approved supply to display offers and complete checkout — two connected layers, never the same surface, so the hotel stays in control.
Can developers and AI agents create bookings?
Yes. Booking creation is a REST API operation, every feature is callable externally with OAuth2, and a hosted MCP server lets AI agents read the live contracts. Subscribe to booking.create and 70 webhook events, or embed bookable inventory with Web Components. On direct API integrations you can also be your own merchant of record and run payment yourself.
Does Booking Engine sync bookings to my PMS or channel manager?
Yes. When bookings are created, updated or cancelled, they sync to the connected PMS or channel manager with full lifecycle tracking, and the hotel, traveler and (where relevant) partner receive confirmation.
Is Booking Engine the same as an OTA?
No. It's the fulfillment and transaction layer — it never replaces the hotel's brand with an OTA brand. It helps hotel-controlled supply convert across your website, partner, creator, Traveliko, AI and developer routes, with attribution preserved.

One engine for your website and your platform.

Section titled “One engine for your website and your platform.”

Turn demand into confirmed bookings on your own website — and across every partner, creator, AI and developer route — with payment, confirmation and attribution built in.