> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/settings/security/recaptcha-bot-protection.md).

# reCAPTCHA Bot Protection

Use Google reCAPTCHA v3 to stop bots that submit fake orders or test stolen cards in your checkout.

Bots can submit fake orders and test stolen cards in your checkout. Limio uses Google reCAPTCHA v3 to stop them.

Google gives each request a score from 0.0 to 1.0. A score near 0.0 is probably a bot. A score near 1.0 is probably a real customer. Limio refuses a request when its score is below your **Deny Threshold**. Limio checks the score when the shop asks for a payment form.

{% hint style="success" %}
**Recommended setting:** a **Deny Threshold** of `0.5`. This is the default that [Google recommends](https://developers.google.com/recaptcha/docs/v3) for reCAPTCHA v3.
{% endhint %}

## Step 1: Get the keys from Google

1. Go to the [Google reCAPTCHA admin console](https://www.google.com/recaptcha/admin).
2. Register your site, and select **Score based (v3)**. Limio supports reCAPTCHA v3 only.
3. Add each domain that serves your Limio shop.
4. Copy the **site key** and the **secret key**.

## Step 2: Turn on reCAPTCHA in Limio

1. In Limio, go to **General Settings > Site Security**.
2. In the **reCaptcha** section, enter the **Site Key** and the **Secret Key**.
3. Tick **enabled**.
4. Set **Deny Threshold** to `0.5`.
5. Click **Save**.

{% hint style="danger" %}
**Keys alone do not give protection.** If **enabled** is not ticked, Limio does not check the reCAPTCHA token, even with both keys saved. The shop still gets a token from Google, so the checkout looks correct and the Google console shows traffic. But a bot order passes.

A **Deny Threshold** of 0, or an empty threshold, makes Limio ignore the score. A request that Google scores as a bot can then pass.

After an incident, check these two values first.
{% endhint %}

## Step 3: Republish the pages that use reCAPTCHA

A page gets the site key when Limio builds it. After you add or change the keys, rebuild and publish each page that shows a payment form. These are usually your checkout pages and the My Account pages where customers manage their payment details. Until you republish a page, it keeps the old key.

If you ticked **Use reCaptcha for Landing Page actions**, also republish the landing and offer pages that start a checkout. This setup is less common.

To republish many pages at once, use [Mass Build and Publish](https://docs.limio.com/product/page-builder/how-to-publishunpublish-your-pages-online/mass-build-and-publish-pages.md) with a page label.

## Step 4: Test

1. Do a test checkout, and make sure that the payment form shows.
2. In the Google reCAPTCHA admin console, make sure that the requests from your shop show.

## Change the Deny Threshold

The threshold must be at least 0 and less than 1. Start at `0.5`.

* **A higher value** stops more bots, but it can also stop real customers.
* **A lower value** lets more real customers through, but it also lets more bots through.

Before you change the value, look at the score distribution in the Google reCAPTCHA admin console, and at the scores on your recent orders. See [See the score of an order](#see-the-score-of-an-order).

## Check landing page actions

By default, Limio checks the token at the payment step. To also check the token when a customer starts a checkout from a landing page, go to **General Settings > Site Security** and tick **Use reCaptcha for Landing Page actions (e.g. Initiate Checkout)**.

## See the score of an order

Limio saves the result of the reCAPTCHA check on the order event. Use it to examine a suspicious order, or to find the scores of real customers before you change the threshold.

1. In Limio, open the order.
2. In the **Events** section, open the order event, for example `order.new`.
3. Open the **Json** tab, and find `recaptchaPayload`.

| Value of `recaptchaPayload`           | Meaning                                                                                                                |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| `score`, `success: true`, `action`    | Google checked the token. The `score` is from 0.0 (probably a bot) to 1.0 (probably a real customer).                  |
| `success: false` and `limio-no-token` | The shop sent no token with the order.                                                                                 |
| `null`                                | Limio did not check reCAPTCHA for the order, or the check gave an error. This is normal when reCAPTCHA is not enabled. |

## Zuora Payment Pages 2.0

If your checkout uses Zuora Payment Pages 2.0 and reCAPTCHA is enabled in Limio, Limio checks the reCAPTCHA token before it asks Zuora for the payment page. A request that fails the check does not get a payment page.

Zuora also recommends Google reCAPTCHA Enterprise on the pages of your website that lead to the payment page. You set this up with your own Google Cloud account, not in Limio. See [Enable Google reCAPTCHA Enterprise on your website](https://docs.zuora.com/en/zuora-payments/process-payments/payment-pages-2.0/security-measures-for-payment-pages-2.0/enable-google-recaptcha-enterprise-on-your-website) in the Zuora documentation.

## Troubleshooting

* **Bot orders still pass:** In **General Settings > Site Security**, make sure that **enabled** is ticked and the **Deny Threshold** is above 0.
* **No requests show in the Google console:** Make sure that you rebuilt and published your pages after you saved the keys. Make sure that your shop domain is in the domain list of the key.
* **Real customers cannot pay:** Make sure that the **Site Key** and the **Secret Key** are from the same Google key. If they are correct, look at the score distribution in the Google console before you decrease the threshold.
* **Errors in the browser:** Open the developer console of the browser, and look for JavaScript errors.

If the problem continues, contact Limio Support.

## Related pages

* [Card Testing Protection](https://docs.limio.com/product/settings/security/card-testing.md): all the controls against card testing, and what to do during an attack.
* [Rate Limiting](https://docs.limio.com/product/settings/security/rate-limiting.md): limit how many payment requests one IP address can make.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/product/settings/security/recaptcha-bot-protection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
