VRBO channel
apiSource = "vrbo" (apiSourceId=30). VRBO is the one channel
where payment processing stays in BA.
Detection
dispatchChannelFor("vrbo") returns "email" — VRBO doesn’t have a
dedicated thread routing like Airbnb/Booking.com. We send to the
guest email directly.
Payments — stay in BA
VRBO bookings use BA’s pending-payment infrastructure:
- 287723 — VRBO first payment (50% at booking time)
- 287724 — VRBO final payment (50% on schedule)
- 287721 — VRBO security deposit ($1200, DISABLED in BA)
BA uses the Stripe card it collected at booking time + scheduled charge rules. We don’t have access to that card, and reimplementing the schedule duplicates working BA functionality.
Bill’s decision: leave VRBO payments in BA permanently. Don’t disable AAs 287721 / 287723 / 287724 when cutting other AAs over.
See BA cutover checklist for the do-NOT-disable list.
Other VRBO behavior
Everything else (pre-arrival messages, form bridges, cleaning, etc.) works identically to Direct bookings — VRBO is just another email-only channel in our worker.