Checkout Loop

Hey Clayton,

I have completed some further debugging.

The Stripe scripts are all registered correctly. The following handles are present:

wc-stripe-gateways
wc-stripe-credit-card
wc-stripe-applepay-checkout
wc-stripe-googlepay-checkout
wc-stripe-local-payment-checkout

However, none of the Stripe handles have any inline scripts attached.

There is no output similar to:

var wcStripeSettings = {...};

The WordPress hooks are definitely firing:

• wp_footer
• wp_print_footer_scripts

WooCommerce also detects the Stripe gateways correctly:

ppcp, stripe_cc, stripe_applepay, stripe_googlepay, stripe_klarna

Could you confirm which script handle wcStripeSettings should be attached to, and which PHP class/function is responsible for registering it?

At this point it looks like the plugin is enqueueing the JS assets but not registering the configuration data.

Thanks.

Hi Clayton,

I have added logging around the enqueue_asset_data() method and can confirm that wp_print_footer_scripts is firing correctly.

The logs show:

• Stripe: enqueue_asset_data() called
• Stripe: has_data BEFORE action = YES
• Stripe: has_data AFTER action = YES
• Stripe: Printing wcStripeSettings

However, the browser error remains:

credit-card.js:
Uncaught TypeError: Cannot read properties of null (reading 'cardFormType')

While debugging in the browser I found something unexpected.

window.wcStripeSettings is undefined:

console.log(window.wcStripeSettings);
// undefined

However, the same data is available under:

console.log(window.wcCardSettings);

which returns the full settings object, including stripe_cc_data.

The plugin logs indicate that print_data( 'wcStripeSettings', ... ) is being called, but the rendered page ends up creating window.wcCardSettings instead of window.wcStripeSettings.

Since credit-card.js calls:

getSetting("stripe_cc_data")

and getSetting() reads from:

window.wcStripeSettings

it seems the script is looking for a global that doesn’t exist, even though the data itself has been generated.

The site is hosted on WP Engine. They have confirmed that the basket and checkout pages are not cached, and there are no caching plugins installed.

Does anything within the plugin intentionally rename wcStripeSettings to wcCardSettings, or is there another component that aliases or rewrites the settings object before credit-card.js executes?

Thanks.

Hey Clayton,

Sorry, you were right this was caused by another plugin:

Real-Time Find and Replace – A rule had been setup to replace “Stripe” with “Card”.

I have removed this and the issue is now fixed.

Many Thanks,
Devan