@wix/auto_sdk_bookings_bookings 1.0.60 → 1.0.61

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -4004,12 +4004,18 @@ interface BulkConfirmOrDeclineBookingOptions {
4004
4004
  * We recommend following [this sample flow](https://dev.wix.com/docs/rest/business-solutions/bookings/end-to-end-booking-flows#book-a-course)
4005
4005
  * to minimize failed calls due to unavailability.
4006
4006
  *
4007
+ * ### Booking status
4008
+ *
4009
+ * Create Booking defaults to `status=CREATED`. Such bookings aren't visible in the [Booking Calendar](https://support.wix.com/en/article/wix-bookings-about-the-wix-booking-calendar).
4010
+ *
4011
+ * Only [identities](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities) with `Manage Bookings` permissions can set `status=CONFIRMED`.
4012
+ *
4007
4013
  * ### Related resources
4008
4014
  *
4009
- * Specifying a `resource` triggers an availability check, resulting in a failed
4010
- * call if the resource is unavailable. Omitting a resource allows Wix Bookings
4011
- * to assign a resource belonging to the relevant type randomly when the merchant
4012
- * confirms the booking.
4015
+ * Specifying a `resource` triggers an availability check, and the Create Booking call fails if the resource is unavailable.
4016
+ *
4017
+ * If you omit `resource`, resource assignment and availability validation occur during booking confirmation.
4018
+ * If no resources are available, the behavior depends on the confirmation method used and payment status.
4013
4019
  *
4014
4020
  * ### Participant information
4015
4021
  *
@@ -4027,32 +4033,17 @@ interface BulkConfirmOrDeclineBookingOptions {
4027
4033
  * If you specify `{"sendSmsReminder": true}`, the customer receives an SMS 24 hours
4028
4034
  * before the session starts. The phone number is taken from `contactDetails.phone`.
4029
4035
  *
4030
- * ### Booking status
4031
- *
4032
- * Bookings default to the `CREATED` status, not affecting the business calendar
4033
- * or resource availability. You can specify a different status when the calling
4034
- * [identity](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities)
4035
- * has `Manage Bookings` permissions.
4036
- *
4037
4036
  * ### Payment options
4038
4037
  *
4039
- * The specified `selectedPaymentOption` indicates how the customer intends to
4040
- * pay, allowing for later changes to a different method supported by the service.
4038
+ * The specified `selectedPaymentOption` indicates how the customer intends to pay, allowing for later changes to a different method supported by the service.
4041
4039
  *
4042
4040
  * ### Payment status
4043
4041
  *
4044
- * A booking is initially created with `{"paymentStatus": "UNDEFINED"}` regardless
4045
- * of the payment status specified in Create Booking. If a customer uses an
4046
- * _eCommerce checkout_
4047
- * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/orders/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/checkout/introduction)),
4048
- * Wix Bookings automatically syncs the booking's payment status from
4049
- * the corresponding eCommerce order
4050
- * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/setup) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction)).
4042
+ * All bookings are created with `paymentStatus=UNDEFINED`, ignoring the payment status you specify.
4051
4043
  *
4052
- * If a booking doesn't have a corresponding eCommerce order, for example, since
4053
- * the customer didn't use the eCommerce checkout, you can update the booking's
4054
- * payment status with Confirm Or Decline Booking
4055
- * ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings/confirm-or-decline-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-or-decline-booking)).
4044
+ * For customers paying with a Wix eCommerce checkout ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/checkout/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/purchase-flow/checkout/checkout/introduction)), Wix Bookings automatically syncs the booking's payment status from the corresponding eCommerce order ([SDK](https://dev.wix.com/docs/sdk/backend-modules/ecom/orders/introduction) | [REST](https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/introduction)).
4045
+ *
4046
+ * For customers using a custom checkout, call Confirm or Decline Booking ([SDK](https://dev.wix.com/docs/sdk/backend-modules/bookings/bookings/confirm-or-decline-booking) | [REST](https://dev.wix.com/docs/rest/business-solutions/bookings/bookings/bookings-writer-v2/confirm-or-decline-booking)) to update booking's payment status manually.
4056
4047
  *
4057
4048
  * ### Booking form data
4058
4049
  *