Smart Widget: pre-payment booking reference, social login and ECPay deposits

API General
1

Hello SimplyBook.me developers. Live chat support referred us here for product capability confirmation (not implementation services).

We operate an embedded booking flow on an Asia-region account using ECPay deposit payments. We need to associate an opaque first-party reference with a booking BEFORE payment, preserve that association through Google/Facebook/email client login, and verify actual payment server-side even if the customer closes the payment return page. We are not asking to bypass consent requirements or to change our live account.

Could you please confirm these three points, with supported documentation or a clear ‘not supported’?

  1. Does Smart Widget currently support both Google and Facebook client login, as well as email login? If a custom Public REST integration is required, what is the supported social client authentication flow (token exchange, redirects/origins)? We found email login and login-by-hash operations, but not a documented Google/Facebook OAuth contract.

  2. Does Smart Widget support ECPay deposit payments for Asia accounts? For a custom API flow, what is the supported sequence from booking creation to deposit invoice creation and payment redirect? How can we obtain and persist the booking/deposit invoice relationship before redirecting, without manually marking an invoice paid? Is there an isolated test company/payment sandbox for validating this without changing the production widget?

  3. Can the existing iframe or Smart Widget accept and persist a per-booking opaque reference (for example in an additional field), or emit an officially supported booking-ID event to the parent page BEFORE payment? Please specify the parameter/event name, timing, supported origins and whether it survives social login redirects. If neither is supported, is a custom API booking flow the recommended alternative?

We have reviewed the developer API page, API explorer, API documentation, user API guide, and the public/admin Swagger schemas. Our remaining question is the supported end-to-end contract and compatibility, not how to fetch existing bookings. A backend payment lookup alone cannot bind a browser reference to the booking that created it.

No customer data, credentials or real booking identifiers are included here. Thank you.

3

Hi,

  1. Smart Widget does not support Google and Facebook client login at the moment.

  2. It supports all payment processors, that are available in SB

  3. You can try predefined values for intake forms.

4

Thank you for confirming the Smart Widget social-login limitation. We will keep the existing iframe while evaluating supported options.

Could you please clarify these related capability questions (no account changes requested)?

  1. Is there an officially supported custom JavaScript field/feature separate from Google Tag Manager and Custom CSS? If so, what is the exact admin path, plan requirement/cost, and does it run inside the existing /v2/ embedded booking iframe as well as the standalone booking site?
  2. Your Analytics tools integration guide says GTM verification requires cookie acceptance or disabling the widget banner. For the existing iframe, is gtm.js intentionally withheld until consent? How do standalone and embedded consent states differ, and is there a supported consent-respecting way to run only a necessary opaque booking-reference bridge without enabling marketing tags? We are not asking to bypass consent or disable the banner.
  3. For predefined intake-form values, please provide the exact supported parameter/schema for the existing iframe and Smart Widget, and clarify whether the value persists through Google/Facebook login, becomes associated with the booking before payment, and can be read through the Admin API afterward.

We can see a GTM script element in an existing Chrome session, but that alone does not establish execution or first-visit/consent behavior. Please link the supported contract or explicitly confirm when a capability is unavailable. No customer data or credentials are included.