Это содержимое пока не доступно на вашем языке.
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.


What is Wink Booking Engine?
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.
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
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.
Supply flows from Extranet; your rates and attribution stay attached all the way through checkout.
Sell the whole stay
More than a room night.
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.
- 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

The booking flow
From any route to a confirmed booking.
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

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

Step 03 · Checkout & payment
One checkout, payment handled by Wink
The guest reviews the stay and pays in a single, hotel-branded checkout — payment handled by Wink, the merchant of record.
- Hotel-branded, mobile-first checkout
- Payment handled by Wink
- Booking record tied to the hotel and route

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

How payment works
Payment and payout, handled by Wink.
Wink is the merchant of record and handles payment end to end. It runs checkout, policy and settlement so the hotel never wires up a processor — and it’s included in one all-in rate.
- Tokenized cards, 3DS and multi-currency
- Cancellation, deposit and rate-plan policy enforced at checkout
- Split payouts and partner attribution settled together
How the money moves
- 1
Guest pays in full at checkout
The full booking amount is captured in the hotel-branded Wink checkout.
- 2
Wink holds the funds
Collected on behalf of the hotel, with policy and cancellation logic applied.
- 3
Released at guest check-in
Funds are paid out to the hotel at check-in, after Wink's all-in fee.
- 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
Designed for how guests actually book.
Most travel demand starts on a phone. Every step — discover, choose, add, pay — is built for it.

Discover

Choose

Add to the stay

Pay
Developers & AI agents
The fulfillment layer, on tap.
Every Agentic AI handoff and developer integration resolves in Booking Engine — booking creation over REST with OAuth2, 64+ 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.
Who fulfills here
One engine, three ways to use it.
Convert your direct demand
Power booking on your own website, links, QR codes, Web Components, WinkLinks and Traveliko — sell the whole stay and keep the guest.
Explore for hotels For partnersFulfill the demand you create
Send guests from your links, storefronts and campaigns into a real checkout — with attribution attached through confirmation and payout.
Explore for partners For developersBuild on hotel commerce
Use Booking Engine as the fulfillment layer behind search, booking, payment and confirmation — including merchant-of-record on API integrations.
See documentationBooking Engine FAQs
The two jobs, routes, payment and how to build on it.
What is Wink Booking Engine?
Can Booking Engine sell more than rooms?
Which routes does Booking Engine fulfill?
How does payment work?
How is Booking Engine connected to Extranet?
Can developers and AI agents create bookings?
Does Booking Engine sync bookings to my PMS or channel manager?
Is Booking Engine the same as an OTA?
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.