Skip to content

How do I stop card testing through PayPal on my WooCommerce store?

By the Brickmoat team · Last checked

Short answer

Bots call PayPal Payments’ own create-order request, /?wc-ajax=ppc-create-order, to try stolen cards through PayPal’s card fields, and that request skips the checkout checks many plugins rely on. Guard the request itself before PayPal Payments handles it, count declines per address, network and device, and lock down when declines spike. Turning off PayPal’s card fields also works, but card buyers then pay in PayPal’s pop-up.

Why PayPal checkouts get hit

PayPal Payments can show card fields on your checkout, a feature PayPal calls Advanced Card Processing. When a shopper pays, the button first asks your store to create the PayPal order at /?wc-ajax=ppc-create-order. Card-testing bots call that address directly, over and over, with a different card each time.

Merchants on the WordPress.org support forum found that WooCommerce’s usual checkout validation hooks are not called on that request, so plugins that only guard the normal checkout never see it. Documentation on WooCommerce.com describes attacks of hundreds or thousands of fake transactions within minutes on stores running PayPal Payments 3.1.2 and newer.

PayPal settings that help

WooCommerce.com’s guidance for these attacks suggests, among other things:

  • During an attack, switch off “Enable Advanced Card Processing” under WooCommerce → Settings → Payments → PayPal. Shoppers can still pay by card in PayPal’s own pop-up.
  • If attacks continue, ask PayPal support to review your API credentials. An attacker who calls PayPal’s systems directly never touches your site, so nothing on your site can stop that.
  • Keep PayPal Payments up to date.

Guarding the request itself

Because the attack never goes through the normal checkout, the check has to sit on the create-order request, run before PayPal Payments handles it, and refuse the request when it looks like a script. Counting declines across that request and the normal checkout together means a bot cannot switch between them to reset the count.

Steps with Brickmoat

  1. Install the free plugin

    Brickmoat checks the ppc-create-order request before PayPal Payments handles it, the same way it checks the normal checkout. On a test store with PayPal Payments 4.2.2, a scripted create-order request was refused by Brickmoat and never reached PayPal Payments.

  2. Let it count declines

    Declines from PayPal and from the normal checkout are counted together per IP address, network, email and device, and repeat offenders are blocked.

  3. Lockdown during an attack

    When declines spike, every check tightens until the store has been quiet for 60 minutes, and failed-order emails are paused.

  4. Clean up

    Move the attack’s failed and unpaid orders to Trash from the Cleanup screen, with undo.

  5. Optional: a report for PayPal

    Pro ($19 per month, or $149 a year) builds a report of each attack, as a web page and PDF, to send PayPal when they ask about the declines.

The plugin is free, with nothing to set up. Read the plugin guide or see what Pro adds.

Limits to know about

  • Only requests that reach your store can be checked. Attempts made against PayPal directly with your credentials are PayPal’s to stop.
  • The check was tested against PayPal Payments 4.2.2 on a test store. A future PayPal Payments release that renames the request would need a Brickmoat update.
  • Other payment plugins’ own requests are not guarded by default. A developer can add them with the brickmoat_gateway_ajax_actions filter.

Related questions

Does reCAPTCHA stop PayPal card testing?

Not on its own. Merchants on the WordPress.org forum found reCAPTCHA was not checked on PayPal Payments’ create-order request. Whatever check you use has to run on that request itself.

Should I switch off PayPal card payments?

Switching off Advanced Card Processing during an attack is a reasonable stop-gap: shoppers can still pay by card in PayPal’s pop-up. Guarding the request lets you keep the card fields on.

What should I tell PayPal after an attack?

When it started and ended, how many attempts there were, and what you changed to stop it. Brickmoat Pro builds that report for you.

Sources

More on this

Protect your checkout today

Install the free plugin and your checkout is protected straight away. There is nothing to set up and no account to create.

Version 1.0.0, a ZIP you upload in WordPress. Free, no account needed. How to install