> 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/card-testing.md).

# Card Testing Protection

What card testing is, what it costs you, what Limio does to stop it, and the controls that you can add.

Card testing is a type of fraud. A bot submits many stolen or guessed card numbers through a checkout to find the cards that work. The attacker then uses the valid cards or sells them. Other names for card testing are carding, BIN attacks and enumeration attacks.

Card-testing attacks on online checkouts have increased across the industry, and Limio sees them on Limio shops too. Many attacks now come from residential proxies: home internet connections that the attackers rent or hijack. This traffic looks like real customers, so one control, for example an IP address block, does not stop it. Use the controls on this page together.

## What card testing costs you

Each attempt that gets through goes to your payment gateway as a real authorisation. Some of the effects continue after the attack stops:

* **Fees.** Some processors charge a fee for each authorisation, also when the card is declined. The card networks add a small fee for each attempt. An attack of tens of thousands of attempts can cost thousands.
* **More declines for real customers.** A high decline rate makes your business look risky to card issuers. The issuers can then decline more payments from your real customers.
* **A flag on your merchant account.** Your acquirer or a card network can put your account into a monitoring programme, add fees or close the account.
* **Disputes.** Some test payments succeed. The cardholder sees the charge and disputes it, and you pay the dispute fee.
* **Bad data.** Test attempts can create payment methods, customer records or orders in your billing system. These records make your reports less accurate, and someone must remove them.

## How to see an attack

Look for these signs in your payment gateway:

* A sudden increase in declined payments, often for small amounts
* Many payment attempts in a short time, from many IP addresses or from countries that you do not usually sell to
* Customer names and email addresses that look random

In Limio, the order event of each order shows its reCAPTCHA score. A low score on many orders is another sign of an attack. See [See the score of an order](https://docs.limio.com/product/settings/security/recaptcha-bot-protection.md#see-the-score-of-an-order).

Limio does not see the alerts in your payment gateway or billing system. Tell your payments and finance teams that your Limio checkout sends payments to them. If they see a spike in declined or small payments, ask them to send the time window and some example transaction IDs to <support@limio.com>. Limio can then find and block the source.

## What Limio does

Limio puts a firewall in front of Limio checkouts. You do not need to do anything to get this protection.

* The firewall detects and blocks automated traffic before it gets to your payment gateway.
* It limits how many payment requests one visitor can make, and it blocks networks that attacks often come from. See [Rate Limiting](https://docs.limio.com/product/settings/security/rate-limiting.md).
* The Limio team monitors checkout traffic, and changes these protections when attack patterns change.

If you think that a protection blocked a real customer or one of your own systems, contact Limio Support.

## What you can do

### Turn on reCAPTCHA

In **General Settings > Site Security**, tick **enabled** and set the **Deny Threshold** to `0.5`. The keys alone give no protection. See [reCAPTCHA Bot Protection](https://docs.limio.com/product/settings/security/recaptcha-bot-protection.md).

### Ask customers to sign in before they pay

A guest checkout is the easiest target for a bot. Where your customer journey allows it, require authentication on the checkout page, so that customers sign in before they get a payment form. An attacker must then create or take over an account first, which makes each attempt slower and easier to trace. A sign-in step can decrease conversion, so test the effect before you apply it to all pages.

See [Authentication per Page](https://docs.limio.com/product/authentication/authentication-provider-per-page.md) and [Set up Authentication for Customers](https://docs.limio.com/product/authentication/sso-your-authentication.md).

### Set the Site Security rate limits

The Limio firewall applies limits for all shops. The Site Security limits add a limit for your tenant on the number of payment requests from one IP address and for one basket. See [Rate Limiting](https://docs.limio.com/product/settings/security/rate-limiting.md#site-security-limits), and contact Limio Support for the recommended values for your shops.

### Use the fraud tools of your payment gateway

Turn on the card-testing protection of your payment gateway, and set an alert for a spike in declined payments. If you use a separate anti-fraud tool, or plan to add one, contact Limio Support so that Limio can make sure that your checkout works with it.

| Provider                     | What to check                                                                  | Guide                                                                                                                                                                                                                                                                    |
| ---------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Zuora (Payment Pages 2.0)    | reCAPTCHA Enterprise, IP and card rate limits, submission limit                | [Security measures for Payment Pages 2.0](https://docs.zuora.com/en/zuora-payments/process-payments/payment-pages-2.0/security-measures-for-payment-pages-2.0/secure-your-payment-pages-2.0-integration-with-zuora-security-measures)                                    |
| Zuora (Payment Form)         | IP, card and tenant submission rate limits, 3D Secure                          | [Security measures for the Payment Form](https://docs.zuora.com/en/zuora-payments/process-payments/payment-forms-and-payment-links/payment-form/security-measures-for-the-payment-form)                                                                                  |
| Zuora (all)                  | Bot attack alerts                                                              | [HPM Threat Detection dashboard](https://docs.zuora.com/en/zuora-platform/system-management/zuora-system-health/payment/hpm-threat-detection-dashboard)                                                                                                                  |
| Stripe                       | Radar rules, CAPTCHA, rate limits, key security                                | [Protect yourself from card testing](https://docs.stripe.com/disputes/prevention/card-testing)                                                                                                                                                                           |
| Adyen                        | Bot attack risk rule, velocity rules, BIN block lists                          | [How can I prevent BIN attacks?](https://help.adyen.com/knowledge/risk/fraud-management/how-can-i-prevent-bin-attacks)                                                                                                                                                   |
| Cybersource                  | Velocity rules and negative lists in Fraud Management Essentials               | [Card testing solution guide (PDF)](https://www.cybersource.com/content/dam/documents/en/card-testing-solution-guide.pdf)                                                                                                                                                |
| PayPal and Braintree         | Risk threshold rules, AVS and CVV checks                                       | [Protect your business against carding attacks](https://www.paypal.com/us/brc/article/protect-your-business-against-carding-attacks) and [Braintree risk threshold rules](https://developer.paypal.com/braintree/articles/guides/fraud-tools/basic/risk-threshold-rules) |
| Chase (J.P. Morgan Payments) | Safetech fraud scoring, velocity limits, AVS and CVV checks                    | [Six ways to help prevent card testing attacks](https://www.jpmorgan.com/merchant-services/insights/card-testing-prevention)                                                                                                                                             |
| Worldpay                     | FraudSight, AVS and CVV checks, velocity monitoring. Ask your account manager. | [Card payment fraud guide](https://www.worldpay.com/en/insights/guides/card-payment-fraud)                                                                                                                                                                               |
| Nexi                         | No public guide. Contact Nexi support.                                         | —                                                                                                                                                                                                                                                                        |

### If you use Zuora for payments

When reCAPTCHA is enabled in Limio, Limio checks the reCAPTCHA token before it opens the Zuora payment page. After the page opens, the card details go directly to Zuora, so the Zuora settings add a further layer. In Zuora:

1. Make sure that Google reCAPTCHA Enterprise is on for your payment page.
2. Set a low submission limit for each IP address. If customers share an IP address, for example in a call centre, add that address to the Zuora IP allowlist.
3. Subscribe to the HPM Threat Report. Zuora sends it when it detects a possible bot attack.

Before you apply a change in production, test it in your Zuora sandbox through your Limio checkout.

## During an attack

1. Contact Limio Support at <support@limio.com>. Give the time window in UTC, the number of failed attempts and some example transaction IDs.
2. Ask your payment gateway to add temporary blocks, for example by country or by card BIN.
3. Refund the test payments that succeeded, before the cardholders dispute them.
4. Do not retry payments on the accounts that the attack created. A retry repeats the attack for the card issuer.


---

# 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/card-testing.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.
