Webstore security and fraud prevention
The Zenoti Webstore uses multiple security layers to protect guest data, prevent fraudulent transactions, and ensure secure payment processing.
Before you begin
- Security features are built into the Webstore and do not require configuration by guests.
- CAPTCHA provider selection (Cloudflare Turnstile or Google reCAPTCHA v2 invisible) is configured by your administrator at Configuration > Online booking > Online booking settings > Webstore V2.
CAPTCHA protection
The Webstore supports bot protection through CAPTCHA verification during checkout. Your organization can configure one of the following providers:
- Cloudflare Turnstile -- A privacy-focused CAPTCHA that verifies guests without traditional challenge puzzles. Turnstile is designed to be accessible without visual challenges.
- Google reCAPTCHA v2 (invisible) -- A CAPTCHA that runs silently in the background and only presents a visual challenge if Google detects suspicious activity. Includes a built-in audio challenge for accessibility.
The CAPTCHA provider is configured at the organization level through template settings. When enabled, CAPTCHA verification is required before payment processing to prevent automated abuse.
When CAPTCHA runs
When CAPTCHA is enabled, verification runs on every payment attempt. This includes payments with a new card, a saved card on file, and any other payment action during checkout. CAPTCHA is not triggered by specific suspicious behaviors or thresholds -- it runs on all payment submissions when the feature is active.
Supported payment processors
CAPTCHA verification is processor-independent. It runs before the payment request is sent to the processor, so it works with all supported payment processors: Zenoti Payments (Stripe), Adyen, EGHL, CloudPayments, Freedompay, Airpay, and BBVA.
What happens if verification fails
If a guest does not pass the CAPTCHA challenge, they can retry immediately. There is no lockout or cooldown period. Google reCAPTCHA v2 (invisible) handles retries internally by presenting a new challenge. The transaction is not blocked permanently -- guests can keep attempting until verification succeeds.
Accessibility
Google reCAPTCHA v2 (invisible) includes a built-in audio challenge alternative for guests who cannot complete visual challenges. Cloudflare Turnstile is designed to verify guests without traditional challenge puzzles and may be the preferred option for organizations prioritizing accessibility compliance (ADA, WCAG).
Checkout flow considerations
Enabling CAPTCHA adds a verification step to the checkout flow. In most cases the verification is invisible and completes automatically, but some guests may see a challenge popup that requires interaction. Consider this trade-off between fraud prevention and checkout speed when deciding whether to enable CAPTCHA for your webstore.
Payment security
All card data entered in the Webstore is tokenized directly by the payment processor. Zenoti does not store raw card numbers. When guests save a card on file for future payments, only a secure token reference is stored.
This approach ensures PCI compliance -- sensitive cardholder data never passes through Zenoti's servers.
Session management
The Webstore manages guest sessions with the following security measures:
- Session timeout -- Guests are automatically signed out after a period of inactivity.
- Token refresh -- Authentication tokens are refreshed automatically in the background, so guests do not need to re-authenticate during an active session.
- Slot reservation timeout -- Reserved time slots are automatically released after 5 minutes (default) if the guest does not complete checkout, preventing indefinite slot holds.