> 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/rate-limiting.md).

# Rate Limiting

How Limio limits the rate of requests to your shop, with the firewall that Limio manages and the limits that you set.

Limio limits requests at two levels:

* **The Limio firewall.** Limio manages it. You do not configure it.
* **Site Security limits.** You set these in **General Settings > Site Security**. They control payment and order requests for your tenant.

## The Limio firewall

Limio puts a web application firewall (AWS WAF) in front of Limio shops and the Limio admin app. The firewall counts the requests from each IP address, and it blocks a client that sends too many. The limits are tighter on the endpoints that bots attack most:

* Sign-in
* The start of a checkout
* Requests for a payment form or a payment token

On the payment endpoints, the firewall also counts requests per browser session. A bot that changes its IP address to test stolen cards still gets blocked.

A blocked client gets the HTTP status `403 Forbidden` until its request rate goes down. The limits are far above the traffic of a real customer. Limio changes them when attack patterns change, so Limio does not publish the values. Some tenants have a dedicated firewall configuration with different rules. To get the limits that apply to your shops, contact Limio Support.

{% hint style="warning" %}
**Contact Limio Support before you:**

* Call the Limio API from your own servers at high volume
* Put a proxy or a CDN in front of your shop
* Do a load test

In these cases, many requests come from a small number of IP addresses, and the firewall can block them. Limio Support can add your IP addresses to an allowlist.
{% endhint %}

## Site Security limits

To set these limits, go to **General Settings > Site Security**. If a field is empty, Limio uses the default value.

| Setting                         | What it limits                                                                                |
| ------------------------------- | --------------------------------------------------------------------------------------------- |
| **Payment Rate Limits**         | Requests for a payment form or a payment token from one IP address, in the **Request Period** |
| **Payment Rate Limits- Basket** | Requests for a Zuora payment page for one basket, in the **Request Period**                   |
| **Order Rate Limits**           | Orders that Limio processes at the same time for your tenant                                  |

When a client goes above a payment limit, Limio refuses its next payment requests until the period ends.

Limio does not publish the limit values, so that they do not help an attacker. A checkout page can ask for more than one payment token, for example one for cards and one for PayPal, so set a payment limit above the number of payment requests that one customer makes. For the recommended values for your shops, contact Limio Support.

{% hint style="warning" %}
**Before you set a payment limit, check how your customers get to your shop.** If your shop is behind a reverse proxy, or if agents in a call centre order for customers, many customers share one IP address. A per-IP limit can then block real customers. Contact Limio Support before you set the limit.
{% endhint %}

**Order Rate Limits** is a capacity limit, not a fraud control. When more orders arrive than the **Concurrent Limit**, the extra orders wait until earlier orders are complete. A lower value does not stop card testing, and it can slow down real orders at peak times.

## 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.
* [reCAPTCHA Bot Protection](https://docs.limio.com/product/settings/security/recaptcha-bot-protection.md): stop bots before they get a payment form.


---

# 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/rate-limiting.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.
