Works with your stack
Cookie consent for WooCommerce PayPal Payments
fraud check comes along
WooCommerce PayPal Payments builds the PayPal script from its own code on pages with PayPal buttons: product, cart and checkout after setup. It also loads PayPal’s fraud script on those pages, with no setting to turn it off and no consent setting.
By WooCommerce, Inc. · woocommerce.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
WooCommerce PayPal Payments
WordPress plugin
- Tested version
- 4.2.0
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 4.2.0 tested
- Active installs
- 800,000+
What WooCommerce PayPal Payments adds to your visitors’ browser
No trackers In our test of WooCommerce PayPal Payments 4.2.0 on 7 November 2026, the plugin itself added no tracker and no cookie. What you place in your pages with it, such as a video or a map, still counts.
What matters for consent with WooCommerce PayPal Payments
Built by script
The PayPal script is not printed as a tag: a file from your site creates it. Look at the page in use, not at its source.
Pages with buttons
Buttons show on product, cart and checkout pages, so the PayPal script loads there. Pay Later messages and mini-cart buttons can add it to more pages, up to every page. Keep only the locations you need.
A fraud script
PayPal’s fraud script loads at checkout and where buttons are, always. Optional reCAPTCHA protection adds Google’s script where buttons are.
What our tests found on WooCommerce PayPal Payments
Good to know · WooCommerce PayPal PaymentsWhat WooCommerce PayPal Payments stores in visitors' browsers
WooCommerce PayPal Payments: 2 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for axoEnvlocalStorage Necessary Keeps the PayPal fast checkout (Fastlane) going axoOriginalCheckoutFieldslocalStorage Necessary Keeps the PayPal fast checkout (Fastlane) going Read in its code, 2 November 2026, WooCommerce PayPal Payments.
Full detail
WooCommerce PayPal Payments can store these in a visitor's browser: axoEnv (localStorage, necessary: Keeps the PayPal fast checkout (Fastlane) going); axoOriginalCheckoutFields (localStorage, necessary: Keeps the PayPal fast checkout (Fastlane) going). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Set before the choice · WooCommerce PayPal PaymentsPayPal Payments always loads PayPal's FraudNet script where its buttons are
In 4.1.3 a site script creates c.paypal.com/da/r/fb.js at checkout and on product, cart and pay pages with buttons. Optional reCAPTCHA (off by default) loads Google there. No consent setting.
Read in its code, 16 October 2026, WooCommerce PayPal Payments 4.1.3.
Full detail
PayPal Payments always loads FraudNet in version 4.1.3 (the enabled check returns true): fraudnet.js, served by the site, creates a JSON config tag and <script src="https://c.paypal.com/da/r/fb.js"> at the page load event, at checkout whenever a PayPal method is active and on product, cart and pay pages where buttons are; its session ID is kept in the WooCommerce session. Its optional reCAPTCHA protection (off by default) loads www.google.com/recaptcha/api.js where buttons are. It has no consent setting and does not read WP Consent API.
Set before the choice · WooCommerce PayPal PaymentsPayPal Payments loads the PayPal SDK by script on product, cart and checkout
setting “Button and Pay Later locations” · by default: product, cart, checkout
The SDK is not a tag in the HTML. Pay Later messages load it in 8 countries, and on home and shop pages only if turned on. Mini-cart buttons (off by default) load it on every page.
Read in its code, 16 October 2026, WooCommerce PayPal Payments 4.1.3.
Full detail
WooCommerce PayPal Payments does not print the PayPal SDK as a tag: its own button.js (served by the site) creates www.paypal.com/sdk/js from an address in its localized data. After setup, buttons are on product, cart and checkout pages, so the SDK loads there; Pay Later messages load it on product, cart and checkout pages in 8 countries (US, DE, GB, FR, AU, IT, ES, CA), and on home and shop pages only if turned on. Mini-cart buttons (off by default) load it on every page.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- WooCommerce PayPal Payments 4.2.0, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Settings of the test: Default settings after activation.
- Last run: WooCommerce PayPal Payments 4.2.0 on 7 November 2026, with WordPress 7.1.3.
Online shops
Other plugins of the same kind.
Questions
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For PayPal users
PayPal buttons, on the pages that need them.
fewer buttons, fewer pages
Every feature of the complete plugin for 30 days, no card. PayPal Payments keeps working as it does today.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.