Is there anything DEV3 Slotwise does not do?

Good to know

• The widget on another website needs your Slotwise site on HTTPS: browsers only send the session cookie inside a third-party frame when it is SameSite=None; Secure, which Slotwise sets automatically over HTTPS. Over plain HTTP the widget works only on the same site.
• The Stripe, PayPal and Razorpay drivers follow the providers' documented APIs but were not tested against live accounts, so test with sandbox or test-mode keys first. Subscription renewals on those gateways depend on the gateway's webhook marking the invoice paid; only the simulated gateway charges renewals by itself.
• Plan changes are not prorated: an upgrade starts a new full billing period.
• Every appointment is one customer with one staff member. Group classes with several places and prepaid packages or memberships are not included.
• The calendar feeds are one-way ICS subscriptions. There is no two-way sync with external calendars, so events added in a phone calendar don't block time in Slotwise.
• The REST API is read-only: it lists services, free slots and a business's bookings, but doesn't create bookings.

The How it's built section below covers the engineering behind Slotwise.