Screen Simpro booking form spam with reCAPTCHA or Turnstile
Captcha checks each submission with Google reCAPTCHA v3 or Cloudflare Turnstile before Formpiece takes the booking. A submission that fails the check is refused, so nothing is created in Simpro. The page has no plan restriction.
Before you start
Save your keys as a credential under Integration Credentials, using reCAPTCHA v3 or Turnstile. Each needs a site key and a secret key. Only credentials of those two kinds appear in the list.
Step by step
- Open your form from Forms. On the Settings tab, open Captcha under Form display.
- Turn on Allow captcha.
- Pick your credential from Choose Integration credentials. Each is listed with its provider in brackets, "(reCAPTCHA v3)" or "(Cloudflare Turnstile)".
- Click Save. The page says "Captcha settings updated." and the change is published.
Save stays disabled while Allow captcha is on and no credential is chosen. With Allow captcha off, Save is available so you can turn it off.
The form uses whichever provider the credential belongs to. To change provider, pick a different credential. If a credential holds the keys for both providers, reCAPTCHA v3 is used.
The customer does not tick anything. reCAPTCHA v3 runs without showing a challenge. Turnstile can show the customer a challenge to complete before the booking goes through.
What is checked
When the customer submits, the form asks the provider for a token and sends it with the booking. Formpiece checks the token with the provider using the secret key. It does this for a booking that goes straight through and for one held while the customer pays.
A reCAPTCHA v3 submission needs a score of 0.5 or more. The cut-off cannot be changed. Turnstile has no score.
When it goes wrong
The booking is refused with "Captcha verification failed."
Formpiece refused the submission. Nothing is created in Simpro, no booking appears on the Bookings tab, and the refused submission is logged on the form's Attempts tab. The cause is one of these:
- The credential was deleted, or holds no secret key. Pick a credential again and save.
- Google or Cloudflare rejected the token. Check the site key and secret key come from the same setup.
- reCAPTCHA scored the submission below 0.5.
- The booking arrived without a captcha token. This usually means the form has not been republished since you turned Allow captcha on. Saving this page publishes it, so check the form on your site is loading the latest version.
- Google or Cloudflare did not answer within five seconds. Formpiece refuses a submission it could not check.
Captcha is on but no site key reaches the form
The form needs the site key from the credential. A credential that holds a secret key but no site key leaves the form unable to get a token, so every booking is refused.