Creating Custom Booking Journey

The basic flow of an online booking process is as follows:

• Call get booking setup information to get all the basic details required. For example MinOnlinePartySize, OnlinePartySizeDefault, MaxOnlinePartySize, AcceptBookingsDaysInAdvance.

• Call search a date range to populate the calendar with available dates.

• Call search a single day to get the actual availability options for a specific date and time.

• Call create booking after the collection of diner details to create a booking.

  • If a Payment is required you will be returned a status of PaymentRequired and the response will contain PaymentAmount, StripePublishableKey, and FormattedPaymentAmount (which should be displayed to the user).

  • If a Credit Card is required you will be returned a status of CreditCardRequired.

• Use one of the Stripe Payment Collection Methods to process the credit card details with Stripe. Then pass either the returned Stripe Token or the PaymentMethod ID into the same endpoint as before together with the rest of the Booking details.

• You should check the Status to see what the outcome of the call was. If it is Success, you should inform the user and display the Reference from the response. If it is Requires Action then 3DS2 authentication must be performed, and the returned PaymentIntent ID and PaymentMethod ID must be passed into the same endpoint as before together with the rest of the Booking details.

Interactive Widget Examples

• ResDiary.com

• ResDiary Widget

Note: The Venue used in the above Widgets is a good example as it has all payment and promotion scenarios setup.

Booking Process Video Tutorials

• Available vs. Required Promotions

• Variable Price Promotions

• Leave time Confirmed with Guest

• Deposits & Credit Cards Required