WebBeds Integration: Sell WebBeds Hotels on Your Own Website
Works with DOTW Connect accounts, whichever way WebBeds has set yours up to settle.
The first question with WebBeds is how your account pays for bookings, and many agencies only find out when a test booking fails. An account with a credit limit books in two steps. A credit-card customer account needs a card and a pre-authorisation in the middle. We built all three routes, so the choice follows your contract.
WebBeds also blocks unknown servers on its live gateway. Your agency's live connection needs WebBeds to allow the server's IP address, so that request goes on the setup list early.
Key features
Live DOTW Connect search
Searches run by city against your account with your login, company code and password, then prices are converted to the visitor's currency.
Three settlement modes
Deposit or credit limit, corporate card, or WebBeds taking the guest's card itself. You pick the mode in the admin panel.
Card token only
In corporate card mode the card is tokenised in your browser with WebBeds' own script. We store the token, the masked number and the billing address.
Self-service cancellation
Guests can see the cancellation terms and cancel from My Bookings, and the refund follows the WebBeds penalty.
A connection test with real errors
The test button in the admin panel calls the WebBeds gateway directly and shows the actual error if your login or server is refused.
Choosing a settlement mode
Deposit or credit limit is the simplest route. The guest pays you through your gateway, your markup stays with you, and the booking is drawn from your WebBeds balance. This is the mode for most agencies whose contract allows it.
Corporate card suits an account with no credit line. The guest pays you, and after that payment the server pays WebBeds with your stored card. WebBeds supports single-room bookings only on this route, so the checkout blocks multi-room stays before the guest pays. If WebBeds demands 3D Secure on your card at that moment, the booking stops and the guest is refunded, which means you need a card that does not trigger it.
With WebBeds as merchant of record, the guest's card goes straight to WebBeds. No markup is added on this route, so it suits an agency that earns in some other way.
The manual option for Makkah and Madinah
A separate, optional connection sells WebBeds hotels in Makkah and Madinah beside your partner hotels, from a catalogue you can edit and curate. It shows live quotes and takes payment, then sends your team an alert. A person places the reservation with WebBeds by hand, so nothing is booked automatically on this route. It is a separate per-site setting with its own credentials.
What to expect in setup
We test the connection on the WebBeds development gateway first. Live credentials do not work there, and the live gateway only answers from an allowed IP, so going live takes a short exchange with your WebBeds contact. Allow a few days for that exchange if your contact is slow to reply.
This integration covers hotels only. It does not merge a WebBeds rate with the same hotel from another supplier. If you run several suppliers, customers see each rate and can pick the cheaper one.
The three WebBeds settlement modes
| Deposit or credit limit | Corporate card | WebBeds as merchant | |
|---|---|---|---|
| Who charges the guest | Your gateway | Your gateway | WebBeds |
| Who pays WebBeds | Your balance | Your stored card | The guest, directly |
| Your markup | Kept | Kept | None added |
| Rooms per booking | Several | One | Set by WebBeds |
| Needs from you | A funded account or credit | A card without a 3D Secure challenge | WebBeds enabling this mode |
Frequently Asked Questions
Is this for DOTW or WebBeds?
Both names point to the same system here. The integration uses DOTW Connect, the API WebBeds issues to its clients, and it needs your login ID, company code and password.
Why does my live login fail on the test gateway?
Live accounts do not exist on the WebBeds development gateway. Test credentials work there, and live credentials only work on the live gateway from an IP address WebBeds has allowed.
Is Travora Hub affiliated with WebBeds?
No. Travora Hub is independent. The account, the contract and the supplier relationship are yours.
Which payment gateways work with WebBeds bookings?
Stripe, MyFatoorah and Safepay all work with the deposit and corporate card routes. See the payment gateways page for what each one covers.
Can sub-agents book WebBeds hotels?
Yes. On plans with the B2B portal, agents book these hotels at the commission you set for WebBeds, and each booking is tracked to the agent.
Guides to read next
Explore more: Hotel Booking Engine · Hotelbeds Integration · Hajj & Umrah Software · All Integrations · B2B Agent Portal