Payment gateway connectors

Payment scripts can load before checkout

A payment gateway plugin can load a vendor script on product and cart pages, not only at checkout. Stripe documents including Stripe.js on every page of a site so it can detect unusual browsing. Other gateways load their own scripts on shop pages when wallets or express buttons are on. This table describes the setups below; your settings can change where requests go.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group gateway plugins

We compare where the named plugins can load payment scripts in a visitor's browser. Product pages, cart pages, mini-carts, and checkout can use different settings. Consent timing and vendor data retention have not been tested.

Where payment scripts can load

Product, cart, or mini-cart pages

Some gateway plugins load Stripe.js, PayPal JS, Square.js, or similar vendor scripts on product and cart pages so wallets and express buttons can work. One Stripe plugin also loads Stripe.js from the mini-cart on other pages. Stripe documents that extra page coverage helps detect unusual browsing. The visitor browser then contacts those payment services before anyone reaches checkout.

At checkout

Payment scripts can also load at checkout. This table does not verify a checkout-only setup for each plugin. Card details entered in hosted payment fields are outside this comparison.

Before consent

Consent timing is not tested here. The Before consent column is not a scan finding. The site scan linked below checks for third-party requests on your pages; it does not access your WordPress database.

Payment gateway connectors

No paid placement. Vendor payment scripts first, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorDocumented outside hostsHow long data is keptBefore consentLinksSource
Mollie Payments for WooCommerce

Mollie can load its payment script at checkout when card components are enabled and available. Apple Pay and PayPal buttons use separate scripts and can appear on product or cart pages when enabled. This row's js.mollie.com host applies to card components. Consent timing is not tested.

Vendor payment script in the visitor browserjs.mollie.comNot assessedNot tested
  • None
Payment Plugins for Stripe WooCommerce

This row covers Payment Plugins for Stripe WooCommerce when a Stripe mini-cart button is enabled. The plugin then loads Stripe.js on pages that are not cart or checkout. Cart and checkout still load Stripe.js for payment. Consent timing is not tested here.

Vendor payment script in the visitor browserjs.stripe.comNot assessedNot tested
WooCommerce PayPal Payments

This row covers WooCommerce PayPal Payments when Smart Buttons are enabled for a location. The visitor page then loads PayPal JS from www.paypal.com. Locations include product, cart, mini-cart, and checkout, depending on settings. Consent timing is not tested here.

Vendor payment script in the visitor browserwww.paypal.comNot assessedNot tested
WooCommerce Square

This row covers WooCommerce Square. The payment form loads Square.js on checkout. When digital wallets are on (the default), Square.js also loads on product and cart pages. Consent timing is not tested here.

Vendor payment script in the visitor browserweb.squarecdn.comNot assessedNot tested
  • None
WooCommerce Stripe Payment Gateway

This row covers WooCommerce Stripe Payment Gateway when it loads Stripe.js on product, cart, and checkout pages (the default). Filters can skip product and cart pages. Stripe documents device characteristics and browsing activity as fraud signals. Consent timing is not tested here.

Vendor payment script in the visitor browserjs.stripe.comNot assessedNot tested
WooPayments

This row covers WooPayments checkout, which registers Stripe.js from js.stripe.com. Express checkout buttons can also load on product, cart, and checkout pages. WooPayments is a Stripe-powered WooCommerce payment plugin. Consent timing is not tested here.

Vendor payment script in the visitor browserjs.stripe.comNot assessedNot tested

What this table does and does not prove

This table describes the named gateway connector setups. It does not show what loads on your site. Where an outside payment script host is documented, that applies only to the setup described. Other page requests are not covered. A server request to a payment API is not the same as a visitor browser request for a payment script. Card details in hosted fields are outside this table. Plugins marked Not reviewed have not been assessed. We have not tested consent timing, and we have not assessed how long vendor logs are kept. The site scan linked below checks for third-party requests; it does not access your WordPress database.

Documentation snapshot: Oct 6, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-payment-gateway-privacy