ZenotiHelp

Security

ZTZenoti Docs Team Updated August 24, 2026 1 min readGuide

The Webstore uses multiple security layers to protect guest data and prevent fraud.

Before you begin

  • Security features are built into the Webstore and require no configuration by guests.
  • CAPTCHA provider selection (Google reCAPTCHA v2 invisible or Cloudflare Turnstile) is configured by your administrator at Configuration > Online booking > Online booking settings > Webstore V2.

CAPTCHA protection

The Webstore supports two CAPTCHA providers for bot protection during checkout:

  • Cloudflare Turnstile — A privacy-focused verification method that works without visual challenges.
  • Google reCAPTCHA v2 (invisible) — A background verification that presents a visual challenge only when Google detects suspicious activity.

The CAPTCHA provider is configured at the organization level through template settings. When enabled, CAPTCHA runs on every payment attempt, including new card entry and saved card on file payments. CAPTCHA is processor-independent and works with all supported payment processors.

Payment security

All card data is tokenized directly by the payment processor. Zenoti does not store raw card numbers. Saved cards on file use secure token references only. This approach ensures PCI compliance.

Session security

  • Authentication tokens refresh automatically.
  • Guests are signed out after inactivity timeout.
  • Reserved time slots are released after the reservation timeout (default 5 minutes).
Was this article helpful?
Your feedback helps us improve our documentation.