Twice, in as many days.

First ever payment after launch, Bancontact crashes Woo, then I get reports of Chrome not displaying the Stripe modal, endless spinner. The 2 things we wanted the most; Bancontact, because we’re a Belgian store, and Adaptive pricing, because we sell to other non-Euro countries too, are now off or the site breaks. Days of painful trouble shooting, turns it both problems are 100% squarely on this plugin. I am not amused. Edit: Bumped the stars to 3, because they are very willing to help fix. Still, it was/is very embarrassing when you can’t offer the payment methods you planned to offer. Last time I checked, there are about 15 million Bancontact cards in circulation, so offering that as a Belgian store should be a no-brainer. Same goes for currencies when you ultimately have a worldwide customer base. This topic was modified 14 hours, 8 minutes ago by Sean . This topic was modified 14 hours, 6 minutes ago by Sean . This topic was modified 4 minutes ago by Sean . Reason: Updated stars This topic was modified 1 minute ago by Sean . Reason: context Hi Sean, I’m sorry to hear that launching a store and hitting two checkout failures back to back has made for such a rough week. The fatal error in WC_Payment_Token_SEPA::set_fingerprint() needs a closer look at your site’s setup to confirm exactly what happened. A System Status Report and a peek at the order/log details would help us narrow it down quickly. stripe.initCheckout() removed error. As my colleague mentioned in your support thread, our plugin pins the older “clover” Stripe.js build where that method still exists. The “has been removed” error comes from a newer “dahlia” build of Stripe.js running on your checkout page, almost certainly loaded by another plugin or integration. Confirming which js.stripe.com/... URLs actually load on checkout, and which other plugins touch Stripe, is the fastest way to pin down the conflict. To get to the bottom of both without you having to share sensitive site information publicly, would you mind opening a ticket with us at woocommerce.com/my-account/contact-support ? We can take a closer look at your site setup, the active plugins, and the Stripe.js loads on checkout, and keep you updated from there. Thanks again for the detail and for sticking with us through a rough launch week. Almost certainly loaded by another plugin…the only other plugin that could be doing this is Woo itself. There was a newer Woo version that got pulled not too long ago. I have no other Stripe related plugins. In short, I’m on Siteground, but even with ALL speed features off; Memcached, NGINX, CDN, Dynamic cache, everything their Optimiser plugin offers, all of it…problem persists. I even fully disabled my custom plugin that makes external API calls and custom endpoints, all of it, off, everything flushed, problem persists in Chrome, only one of the most popular browsers, until I disable Adaptive Pricing. Hi @sean-h , Thanks for getting back so quickly. Since you have ruled out the plugin and server cache, it’s quite puzzling indeed that the dahlia JS is still being loaded. We’d like to take a closer look at this issue. Please contact us via the WooCommerce.com website ( here’s the link to contact us if you want to skip live chat and create a ticket directly) so we can debug it further. Regarding the Bancontact issue, I was able to replicate it and filed a bug report with our developers. We’ll keep you posted in your forum thread . Again, apologies that these issues occurred right after your launch. We’re committed to getting them resolved for your store. Couldn’t seem to find the ticket option, so I started a live chat, with the AI. But, I don’t really do live chats. I’m kinda in the middle of a store launch. My store only offers email support. This reply was modified 18 minutes ago by Sean .