no payment possible via Stripe

Hi @natsshop

That doesn’t necessarily mean there is an issue. If a customer is redirected to Klarna, but decides not to continue with the purchase, then you will encounter the exact scenario you have described where there is no payment method associated with the payment intent.

The notice you’re referring to in the console is harmless and is not caused by the plugin. It’s related to how Stripe’s internal SDK communicates across browsers. It’s not a notice that will affect your payments.

What I recommend you do is set Klarna to authorize payments in the plugin settings, then perform a test payment yourself. You can then confirm if it’s working correctly. After your test, you can void the authorization which avoids incurring any processing fees.

Kind Regards

Hi @natsshop

This plugin is actually designed to be fast and scale for very high volume websites. Slow page speeds as a result of this plugin is not a complaint we see often.

It takes 20 seconds for the plug-in to load the payment options.

Can you share screenshots or additional information so we can analyze how you’re coming to that conclusion?

What you’re seeing in the network tab of your browser console is likely the requests the Stripe SDK is making. That volume of queries and page speed are not mutually inclusive. Those requests are out of our control since that’s part of the js.stripe.com script which is required by Stripe.

Kind Regards

By activating Stripe’s own plugin, I learned, that the migrating off of the Sources API, an old integration method that will be shoutting down

That’s actually not Stripe’s own plugin. That plugin is developed by WooCommerce and always has been.

The reason you are experiencing that hanging is because that JS error is interfering with how the redirect to Klarna works. The server responds to the place order button click with a base64 encoded hash like this:

{
    "result": "success",
    "redirect": "#response=eyJwbSI6bnVsbCwidHlwZSI6InBheW1lbnRfaW50ZW50IiwiY2xpZW.....",
    "order_id": 126512
}

That triggers a hashchange event that the plugin listens for and then redirects to the Klarna payment page. That JS error is interfering with that process.

Why does your plugin with Astra Pro have problems here? Could you please fix this?

I do not know, but I don’t believe it’s caused by an issue in our plugin. There are no references to Astra in our plugin’s code. JS errors within the Astra code would be their responsibility.

If you’re using any kind of cache, try clearing that as part of your tests. I you’re using a cookie plugin, there may be a configuration you need to add that ensures the Astra script that defines astra is loaded. That is a common issue with cookie plugins.

Kind Regards