Kanorio

Form and Checkout Protection

About 9 minBeginner

Your customer list is valuable because the people on it have actually visited your website. Online forms and checkout pages are the two primary entry points where visitors leave contact information, making them prime targets for spam bots. Some bots don't even load the page; they simply blast forms with data or leave fake email addresses at checkout.

Kanorio has built-in multi-layered checks for both entry points. This guide explains how these checks work, what you and your visitors will see, and what you may still need to handle yourself.

How a submission passes through the gates

Think of these as security checkpoints before a visitor can enter. Each one works automatically as soon as your site is published—no setup required.

Gate 1: Network Edge. All Kanorio websites are served via the global Cloudflare network. Requests identified as clear bot traffic rather than human browsers are required to pass a challenge before they ever reach your site. This layer also handles DDoS protection and firewalls; see Connection and Edge Protection for details.

Gate 2: On-page checkpoints. Forms and checkout pages contain several checkpoints that a human filling out the form naturally would never trigger. Bots that don't render the page and simply fill in fields are likely to trip these, and those submissions are discarded immediately.

Gate 3: One-time passes. When a visitor opens a page, the system issues a unique pass for that specific submission. It is valid only for that form or checkout session, expires after one use, and has a time limit. Copying the pass to another form or submitting the same one twice will be rejected.

Gate 4: Rate limiting. There are limits on how many submissions a single source can make in a short period, as well as daily caps for each form. Even if a bot bypasses the earlier gates, it cannot flood your site.

Online forms and customer login have an extra gate compared to checkout: Before submitting, the visitor's device must complete a short computation. This is the brief CAPTCHA on the form. For a human, it takes less than a second. For a bot trying to send thousands of submissions, the cumulative computational cost makes it unprofitable. If you switch to a service like Cloudflare Turnstile (see Switching to other CAPTCHA services), that service handles this gate while the others remain active.

Only submissions that pass all gates will create a contact and send you a notification. Submissions that fail are discarded without leaving any data.

What visitors see

Entry PointVisitor Experience
Checkout PageNothing is visible. The check runs in the background with no extra steps or verification screens.
Online FormBefore submitting, users see an "I'm not a robot" checkbox that completes in under a second. It matches your website's brand colors and border radius, and displays text based on your site's language. Other services would show their own specific verification screens.
Customer LoginVerification is usually invisible and runs in the background; the checkbox only appears if the background check fails. If using reCAPTCHA v2 or hCaptcha, users must check the box before requesting a verification code.

We do not use CAPTCHA on checkout because adding an extra step to the checkout process often leads to cart abandonment. Forms, however, are where visitors intentionally provide contact details, making a brief confirmation step acceptable.

Why we designed it this way

No third-party scripts by default. Many website forms embed services like Google reCAPTCHA. While effective, it means that every time a visitor fills out a form, their data is sent to a third party, potentially introducing tracking cookies. Kanorio's default checks are handled entirely by our own servers, ensuring visitor data isn't sent elsewhere. This aligns with our Visitor Privacy and Data Processing principles. If you already use Turnstile, reCAPTCHA, or hCaptcha on other sites and want to standardize, you can switch.

Our on-page CAPTCHA uses the open-source ALTCHA (MIT licensed, code is public and auditable, and used by German, French, and UK government sites as well as the SEC). It works on a "Proof of Work" principle: the visitor's device performs a small calculation to prove it isn't a bot. The entire process happens on the device; the challenge is generated by Kanorio's server, and the answer is returned only to Kanorio. It connects to no external services, sets no cookies, and does no fingerprinting. You won't see third-party logos or links on your forms, and you don't need to add extra language to your privacy policy.

Custom domains are treated equally. Protection is not tied to the URL. Whether a visitor arrives via yourbrand.kanorio.com or a custom domain, the protection is identical. You don't need to apply for or configure anything extra for each domain.

No keys, quotas, or billing to manage. Built-in protection is included in all plans—no API keys required. If you switch to a third-party service, you manage the keys, usage, and billing through that service's account.

Blocked content simply doesn't exist. It isn't stuffed into a "spam folder" for you to clean up, nor does it count against your form's submission limits.

The platform learns from all sites. A device identified as a bot source on any Kanorio site will have its submissions to other sites automatically classified as spam for a short time. This judgment comes only from Kanorio's own network, is not shared with third parties, and does not permanently remember anyone. It clears automatically after a while, or when you unmark a submission as spam.

Switching to other CAPTCHA services

Forms and customer login use Kanorio's built-in protection by default. You can switch to Cloudflare Turnstile, Google reCAPTCHA (v2 checkbox or v3 score), or hCaptcha using your own API keys.

  1. Create a widget (Google calls this a "site") in your chosen service and add all domains listed on your Site Settings › CAPTCHA page to the allowlist. If a domain is missing, visitors won't see the CAPTCHA and won't be able to submit the form.
  2. Return to "Site Settings › CAPTCHA", select the service, and paste your Site Key and Secret Key. For reCAPTCHA, select the version you chose when creating the keys.
  3. Click "Save". The system will verify the keys with the service before saving; if the keys are invalid, it will notify you immediately and prevent incorrect settings.

Once saved, forms and customer login will use the new service. Submissions already in progress on open pages will still be accepted for one hour, so visitors won't be blocked just because you updated your settings.

Adjust by purpose. Forms and customer login share the same keys by default. If you want to view traffic separately in the service's dashboard or adjust difficulty levels, you can set up a separate key for each under "Adjust by purpose". For reCAPTCHA v3, you can set a minimum score: requests below the threshold are blocked. Higher numbers are stricter; the default is 0.5.

Cannot be disabled, and does not affect checkout. You can change the service, but you cannot turn it off. Checkout always uses Kanorio's built-in protection; the payment page loads no third-party scripts.

Privacy note. When using third-party services, visitor browsing info is sent to that service; reCAPTCHA also sets cookies. Please update your website's privacy policy accordingly, and include cookie consent for reCAPTCHA.

Changing services or keys requires re-authentication because it involves adding third-party scripts to your site. You must have permission to manage site integrations.

What if the service is temporarily unreachable? If the service doesn't respond, the system will allow the submission to pass, relying on other gates to keep it secure. Visitors won't be blocked. If keys become invalid (e.g., you deleted them in the service's dashboard), the settings page will show the number of times verification was skipped in the last 24 hours. Please re-paste your keys.

What this protection doesn't block

It blocks bot submissions, not everything you don't want to receive. The following may still get through:

  • Real people manually opening the page and typing in spam or nonsense.
  • Automated tools that use a real browser to simulate human behavior and are willing to pay the cost for each submission. These tools are limited by rate-limiting, but the number of submissions won't be zero.

For this type of content, forms include an extra Content Check: submissions using disposable email addresses, messages filled with links, or the same text appearing repeatedly across multiple sites in a short time are automatically moved to the form's "Spam" category. They will not create a contact, notify you, or send any messages to the sender.

For details on checking spam, unmarking false positives, manually marking as spam, or using "Pause submissions," "Submission limits," or "Limit to one per person," see Online Forms.

Checkout pages contain no free text and only perform a disposable email check: checkout data using disposable emails is not recorded.

You won't see "Blocked counts" in your dashboard

Submissions that fail checks leave no data, and we intentionally do not store them. The effectiveness of this protection is reflected in the fact that your list is free of fake contacts, not in a number.

Frequently Asked Questions

No. Protection for forms, customer login, and checkout is built-in. There are no extra steps at checkout; when filling out an online form, a brief CAPTCHA appears before submission. If you want to switch to Turnstile, reCAPTCHA, or hCaptcha, see Switching to other CAPTCHA services.

No, but you can switch to a different service. It is a critical gate for blocking mass bot submissions. Turning it off significantly reduces the effectiveness of other gates, and login verification emails could be triggered by anyone. The built-in verification takes less than a second for humans.

When using built-in verification, it sends data to no one. It uses open-source ALTCHA technology; calculations happen on the visitor's device, and the challenge/answer only travels between your site and Kanorio. No third parties are involved, and no cookies are set. If you switch to Turnstile, reCAPTCHA, or hCaptcha, visitor browsing info is sent to your chosen service.

No. Checkout always uses Kanorio's built-in verification. The payment page loads no third-party scripts and adds no extra verification steps.

Adding an extra step to checkout often leads to cart abandonment, so checkout checks happen in the background. Forms are where visitors intentionally leave contact info, making a brief confirmation a reasonable trade-off. Both are handled by the platform; no setup is required.

Yes. Checks are not tied to the URL. Protection for custom domains is identical to Kanorio domains; no extra application or setup is needed.

Go to "Marketing › Online Forms," open the responses page for that form, and filter the status by "Spam." Most spam will already be there and won't bother you. For submissions in the normal list, click "Mark as Spam." If the volume is high, enable "Pause submissions" or set "Submission limits." If you suspect bot activity that isn't being blocked, please contact us via Security Troubleshooting and include a few examples.

Content checks are rule-based. Messages with many links or using disposable emails might be misidentified. Simply click "Unmark as Spam" to create the contact. If the user had opted into your newsletter, their consent will be restored as well.