Channels, direct booking & payments: questions and answers

Yes. It pushes rates and availability out to connected channels, at each channel's own price and as far ahead as you choose, and brings bookings, changes and cancellations in as real reservations.

bedsKey has an adapter built against Booking.com's Connectivity API, including automatic reservation retrieval, and supports the published OpenTravel (OTA) XML message set with framework adapters for Expedia, Agoda, Hotelbeds and RateHawk.

bedsKey now has certified OTA connections, and each connection goes live only after its sandbox test has been recorded.

Every channel booking is compared with the rate that channel was sent, so price mismatches surface instead of slipping through. Read rate parity explained.

It waits in an overbooking queue on screen instead of being lost, so staff can resolve it.

No. Reservation delivery is idempotent: a retry never books twice.

Channel codes for room types and rate plans can be bulk-pasted, and they are validated before they apply. Delivery visibility shows what each channel confirmed, what failed and why.

No. A connection cannot go live until its test against the channel's own sandbox has been recorded.

Yes. Guests search, price and book on your own booking page with no commission. Web bookings use the same path as the front desk, so the no-double-booking guarantee holds. See Direct Booking Engine.

Yes, in one checkout.

A web booking stays tentative until confirmed. Unconfirmed bookings lapse and the room returns to sale automatically. The guest confirms their email address, and bookings whose email is never opened release sooner.

No deposit, the first night, a percentage or a fixed amount. The guest pays on the gateway's own page and the payment posts to the folio automatically.

Yes. A card hold freezes the amount and takes it only if the guest never arrives.

Yes. An emailed link lets the guest cancel and release the room, up to a cut-off you set.

Stripe, bKash, Nagad, SSLCommerz and bank gateways (Brac Bank, City Bank and DBBL) are integrated for deposits, card holds and refunds.

No. Every payment happens on the gateway's own page, so card data never reaches bedsKey.

Yes. bKash go-live depends on the hotel's own bKash merchant account.

Yes. Every gateway starts in sandbox and must be tested before it goes live.

Yes, in whole or in part, back through the gateway. Gateway refunds need manager permission.

Yes. It generates a complete branded website from your PMS account: home, rooms with a page per room, facilities, gallery, about, location with map, contact and your own custom pages. Every Book Now button opens your booking engine, with prices shown including tax. See Hotel Website Builder.

Yes. Connect www.yourhotel.com with on-screen DNS steps and automatic SSL. Every property also gets a free yourhotel.bedskey.com address.

Yes. Each page has its own SEO title and description, the sitemap and robots file are generated for you, and pages are lightweight with no scripts or external fonts, so they load fast on mobile.

Yes. Nothing goes public until you press Publish.

Contact, booking and event enquiries land in an enquiry inbox at the reservations desk.

Yes. A five-endpoint REST API lets partners search availability, price, book, look up and cancel. Credentials are issued by the hotel, scoped to search-only or booking, and limited to one property. It supports amendments, group holds, multi-room-type bookings, signed webhooks and idempotent retries, with Swagger documentation. See Partner API.

Branded emails for booking confirmations, payment links, invoices and statements; guest SMS through a shared bedsKey SMS account or your own provider; and daily summary emails for managers.

Yes. WhatsApp confirmations and reminders are available alongside branded email and SMS.