@wix/auto_sdk_bookings_bookings 1.0.60 → 1.0.62

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.
@@ -98,12 +98,18 @@ interface CreateBookingSignature {
98
98
  * We recommend following [this sample flow](https://dev.wix.com/docs/rest/business-solutions/bookings/end-to-end-booking-flows#book-a-course)
99
99
  * to minimize failed calls due to unavailability.
100
100
  *
101
+ * ### Booking status
102
+ *
103
+ * 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).
104
+ *
105
+ * Only [identities](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities) with `Manage Bookings` permissions can set `status=CONFIRMED`.
106
+ *
101
107
  * ### Related resources
102
108
  *
103
- * Specifying a `resource` triggers an availability check, resulting in a failed
104
- * call if the resource is unavailable. Omitting a resource allows Wix Bookings
105
- * to assign a resource belonging to the relevant type randomly when the merchant
106
- * confirms the booking.
109
+ * Specifying a `resource` triggers an availability check, and the Create Booking call fails if the resource is unavailable.
110
+ *
111
+ * If you omit `resource`, resource assignment and availability validation occur during booking confirmation.
112
+ * If no resources are available, the behavior depends on the confirmation method used and payment status.
107
113
  *
108
114
  * ### Participant information
109
115
  *
@@ -121,32 +127,17 @@ interface CreateBookingSignature {
121
127
  * If you specify `{"sendSmsReminder": true}`, the customer receives an SMS 24 hours
122
128
  * before the session starts. The phone number is taken from `contactDetails.phone`.
123
129
  *
124
- * ### Booking status
125
- *
126
- * Bookings default to the `CREATED` status, not affecting the business calendar
127
- * or resource availability. You can specify a different status when the calling
128
- * [identity](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities)
129
- * has `Manage Bookings` permissions.
130
- *
131
130
  * ### Payment options
132
131
  *
133
- * The specified `selectedPaymentOption` indicates how the customer intends to
134
- * pay, allowing for later changes to a different method supported by the service.
132
+ * The specified `selectedPaymentOption` indicates how the customer intends to pay, allowing for later changes to a different method supported by the service.
135
133
  *
136
134
  * ### Payment status
137
135
  *
138
- * A booking is initially created with `{"paymentStatus": "UNDEFINED"}` regardless
139
- * of the payment status specified in Create Booking. If a customer uses an
140
- * _eCommerce checkout_
141
- * ([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)),
142
- * Wix Bookings automatically syncs the booking's payment status from
143
- * the corresponding eCommerce order
144
- * ([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)).
136
+ * All bookings are created with `paymentStatus=UNDEFINED`, ignoring the payment status you specify.
145
137
  *
146
- * If a booking doesn't have a corresponding eCommerce order, for example, since
147
- * the customer didn't use the eCommerce checkout, you can update the booking's
148
- * payment status with Confirm Or Decline Booking
149
- * ([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)).
138
+ * 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)).
139
+ *
140
+ * 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.
150
141
  *
151
142
  * ### Booking form data
152
143
  *