Works with your stack
Cookie consent for WooPayments
more than the checkout
WooPayments loads Stripe’s payment script at checkout, and on product and cart pages where its express buttons or pay-later messages show. Its checkout code also computes a device ID for fraud checks and keeps a few items in the browser.
By WooCommerce, Inc. · woocommerce.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
WooPayments
WordPress plugin
- Tested version
- 11.2.1
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 11.2.1 tested
- Active installs
- 800,000+
What WooPayments adds to your visitors’ browser
No trackers In our test of WooPayments 11.2.1 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 WooPayments
Where the payment script runs
With default settings, express buttons show on product, cart and checkout pages, so Stripe’s script loads there too. Not on the home page or posts. Fewer button locations means fewer pages with it.
Fraud checks
At checkout, a device ID is computed for fraud checks and sent with the payment. When the account uses an outside fraud tool, the checkout code adds its script itself.
Kept in the browser
Display settings, a saved card brand with its last digits on the block checkout, and currency data are kept in the browser.
Server events
For some stores, WooPayments sends shopper events to WordPress.com from the server. No banner can hold a call from the server.
What our tests found on WooPayments
Good to know · WooPaymentsWhat WooPayments stores in visitors' browsers
WooPayments: 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 wcpay_express_checkout_redirect_urlcookie Necessary Keeps an express payment going skip_woopaycookie Necessary Keeps an express payment going Read in its code, 2 November 2026, WooPayments.
Full detail
WooPayments can store these in a visitor's browser: wcpay_express_checkout_redirect_url (cookie, necessary: Keeps an express payment going); skip_woopay (cookie, necessary: Keeps an express payment 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.
Good to know · WooPaymentsWooPayments checkout computes a device ID and uses cookies and browser storage
- A FingerprintJS device ID is sent with the payment for fraud checks.
- Sets skip_woopay (1 day) and keeps wcpay_appearance_<context> in local storage.
- With Sift in the fraud setup, it creates cdn.sift.com/s.js itself, outside the page HTML.
- Block checkout keeps woopay_preferred_card (card brand, last 4 digits) in local storage.
Read in its code, 16 October 2026, WooPayments 11.2.0.
Full detail
WooPayments' checkout bundle (served by the site) computes a FingerprintJS device ID sent with the payment for fraud checks, with monitoring off (no call to openfpcdn.io); it sets and deletes a cookietest cookie, keeps wcpay_appearance_<context> in localStorage and reads or sets skip_woopay (1 day). When the account's fraud configuration includes Sift, the same bundle creates <script src="https://cdn.sift.com/s.js"> itself, so it is not in the page HTML. The block checkout also stores woopay_preferred_card (card brand and last 4 digits) in localStorage; multi-currency keeps wcpay_mc_async_config in sessionStorage for 5 minutes. It does not read WP Consent API.
Sent from your server · WooPaymentsWooPayments sends shopper events from the server for US stores
setting “wcpay_shopper_tracking_enabled (filter) ; WooCommerce usage tracking” · by default: off
Only with WooCommerce usage tracking allowed, mostly when WooPay is on. The anonymous ID is a tk_ai session cookie set by the server. No banner can hold a server-side call.
Read in its code, 16 October 2026, WooPayments 11.2.0.
Full detail
WooPayments sends shopper Tracks events from the server to pixel.wp.com (wp_remote_get), only for stores in the United States with WooCommerce usage tracking allowed, mostly when WooPay is on; it respects a tk_opt-out cookie. The anonymous ID is a tk_ai session cookie set in PHP. No banner can hold a server-side call.
Set before the choice · WooPaymentsWooPayments loads Stripe.js on product, cart and checkout pages by default
setting “Express checkout locations” · by default: product, cart, checkout
Its default Apple Pay, Google Pay, WooPay and Amazon Pay buttons show on those pages, so Stripe.js runs there, but not on the home page or posts.
Read in its code, 16 October 2026, WooPayments 11.2.0.
Full detail
WooPayments loads Stripe.js (js.stripe.com/v3) at checkout and pay-for-order, and on product and cart pages when express buttons or pay-later messages (Affirm, Afterpay, Klarna) are shown there. Its defaults offer Apple Pay and Google Pay, WooPay and Amazon Pay buttons on product, cart and checkout pages, so Stripe.js runs on those pages; not on the home page or posts. It uses the same script handle as the Stripe extension to avoid loading it twice.
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.
- WooPayments 11.2.1, 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: WooPayments 11.2.1 on 7 November 2026, with WordPress 7.1.3.
Online shops
Other plugins of the same kind.
Questions
Is the payment script a tracker?
At checkout it is part of paying. On product and cart pages it loads before the visitor buys anything, for the express buttons.
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 WooPayments users
Payments that work, whatever the choice.
fewer pages, fewer scripts
Every feature of the complete plugin for 30 days, no card. WooPayments 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.