Booking.com channel
apiSource = "bookingcom" (apiSourceId=19). Booking.com handles the
payment collection on their side and pays the host through Stripe.
Detection
dispatchChannelFor("bookingcom") returns "ota_message" — guest
messages route via Beds24 thread (which routes to Booking.com chat).
Paid flag on new booking
runBookingComPaidFlag in src/workflows/channel-specific.ts fires
on workflow spawn:
- Skips if
PAID=yesinfo code already set - Sets booking flag color
aaaaff+ text “Paid” - Sets
PAID=yesinfo code (idempotency)
Bill uses BA’s calendar UI heavily; the visible “Paid” flag means he can see at a glance which Booking.com bookings have settled.
Ports BA AA 291352.
Pre-arrival messaging
Same as Airbnb — both email (if real address) AND Beds24 thread. Booking.com sometimes shows the real guest email in the booking; sometimes a relay. We send to whatever’s there.
Payments
Booking.com handles guest payments. Bill receives funds from Booking.com via their normal payout (separate from our Stripe). Our worker doesn’t touch Booking.com payments — BA’s pending-payment rules are not applicable.
BA AA mapping (Booking.com-specific)
| BA AA | Status |
|---|---|
| 291352 (booking.com paid flag) | Covered by runBookingComPaidFlag |