Founding offerThe first 10 online stores pay $9 a month instead of $15, for as long as they stay.Founding offer: $9 a month instead of $15 for the first 10 stores.Claim yours
Ropeline Try Pro free

PayPal card testing on WooCommerce: turn on the CAPTCHA, and limit the tries

A guide for store owners who take payments with WooCommerce PayPal Payments. Updated November 15, 2026.

If your store takes cards or PayPal through the WooCommerce PayPal Payments plugin, card-testing bots can use its payment buttons and card form to try stolen cards. WooCommerce's PayPal Payments fraud prevention page says bots can flood your checkout this way, and that stores using the plugin must turn on its bot protection right away. This guide shows how, and what your order list will and won't show you. Everything about PayPal Payments here comes from that page and the plugin's code, read on November 15, 2026, and from running the plugin on our own test store.

Turn on PayPal Payments' reCAPTCHA (free)

It needs PayPal Payments 3.3.0 or newer, and a Google account to make the reCAPTCHA keys.

  1. Go to WooCommerce, Settings, Integration, WooCommerce PayPal Payments reCAPTCHA.
  2. Tick Enable reCAPTCHA protection.
  3. In Google's reCAPTCHA admin console, make a set of v3 keys and a set of v2 keys, and paste each Site Key and Secret Key into its field. The protection only works once both sets are in.
  4. Leave the score threshold at 0.5 to start, as WooCommerce suggests. Shoppers who score below it get a v2 challenge instead of being turned away.
  5. Save.

It covers PayPal Payments' own payment endpoints, including its card form (Advanced Card Processing) and the PayPal buttons, on the classic checkout and the checkout block. It doesn't cover other payment methods on your store.

What your order list will and won't show

When PayPal declines the final charge on an order, PayPal Payments' code usually marks the WooCommerce order as Failed, so those declines show up like any other provider's. Three kinds of tries don't:

So a quiet failed-orders list doesn't prove PayPal isn't being used for card testing. That's why the CAPTCHA matters. What else helps:

  1. Watch your PayPal account, not only your WooCommerce orders, for a run of declined card payments.
  2. Limit tries per shopper. Counting those clicks per connection and per email address slows a bot down even when no order is ever placed.
  3. WooCommerce's own checkout limit (free): Rate limit Checkout in WooCommerce, Settings, Advanced, Features. It's off by default; turned on, it allows 3 checkout tries a minute from each shopper. It slows a bot down; it doesn't stop one that switches addresses.

Being card-tested right now? Start with the free steps in the failed orders guide, and tell PayPal.

How Ropeline Pro handles PayPal Payments

Ropeline Pro is a WordPress plugin that watches your WooCommerce checkout. With PayPal Payments:

We tested the tries limit, pauses and attack mode against the real PayPal Payments plugin (version 4.2.0) on our own test store. We didn't run real PayPal declines, because that needs a PayPal sandbox account.

Taking cards with Stripe as well? See Stripe card testing on WooCommerce.

Store plan: a free week, no card, then $15 a month for stores with up to 500 orders a month ($39 up to 3,000, $99 for any size).

Install in a few minutes: download, upload to WordPress, paste your key. Cancel anytime and your site keeps the free plugin.

Start a free week, no card Check my store free

Or 14 days free with a card

Questions

Will the reCAPTCHA stop real customers?

Most shoppers never see it: reCAPTCHA v3 scores them in the background. Those who score low get a v2 challenge they can solve. If real customers do get stuck, WooCommerce's page explains how to change the threshold.

I use the older PayPal Standard. Does this apply?

No. This guide is about the WooCommerce PayPal Payments plugin and its own settings.

Will Ropeline Pro block my real customers?

It's built not to. A pause only follows repeated declines from the same connection or email. During attack mode, shoppers who go through your checkout page, as almost everyone does, can still pay. Logged-in customers who have paid before skip the checkout-tries limit and attack mode.