Hi @ylkyrg,
Currently, there is an issue with the “early access” payment methods and creating accounts at checkout. That sounds similar to what you’re describing. Try disabling the early access payment methods and see if that fixes the issue for you.
You can do that by going to WooCommerce > Settings > Payments > Stripe. In the “Payments accepted on checkout” section, click on the three dots and select “disable.” Then save your settings.
Let us know if you still have trouble.
Hi @ylkyrg
That is a bit strange! It should be showing here:
Link to image: https://snipboard.io/U6s0ht.jpg
Please try deactivating the new checkout experience by following the steps below:
1. Go to: WooCommerce > Settings > Payments > Stripe.
2. Select the Settings tab.
3. Scroll down to the bottom and click on Advanced settings to display the settings.
4. Tick the checkbox for New checkout experience and click on Save changes.
Link to image: https://woocommerce.com/wp-content/uploads/2021/12/enable-new-checkout-experience-1.png
Let us know if that helps.
Thanks @margaretwporg,
I see. In that case I already had that disabled, as @3sonsdevelopment suggested.
Plugin Support
con
(@conschneider)
Engineer
Hi again,
I see. In that case I already had that disabled, as 3sonsdevelopment suggested.
Thanks for the confirmation. Since that did not make any difference, I suggest we try a conflict check next.
**Before you do that, please do make a full backup!** – one can never have too many ;).
You can use https://wordpress.org/plugins/check-conflicts/ to activate a standard theme and only WooCommerce Payments for your IP address.
Does that change anything?
Kind regards,
Thanks @conschneider, but this is not a conflict issue, it is the behaviour of the plugin.
With guest checkout disabled, if payment fails, the user account is created but the page does not refresh.
There is no indication that the account has been created and that the user is now signed in. If you user does not refresh the page any subsequent payment attempts fail because the checkout form is for logged out users and will try to create an account when submitted.
With guest checkout disabled, if the payment fails, the user account should not be created.
Hi @ylkyrg
Thanks for the update.
this is not a conflict issue, it is the behaviour of the plugin
You can post this over at our idea board and add your vote(s) to it. The more popular an idea becomes, the more of a priority it is for our developers to review it. This board is where our community can share their feedback or requests for change to any of our plugins or services: https://ideas.woocommerce.com/forums/133476-woocommerce
Cheers
Hey @ylkyrg,
I’m just noting that I can’t reproduce this on my test site. Here’s what I tested.
1. In WooCommerce > Settings > Accounts & Privacy, I have disabled guest checkout and enabled the options to automatically assign usernames and passwords.
2. In a private browser window, I attempted to purchase using a Stripe test card that’s set to decline.
3. Once the payment declines, the new user is logged into WordPress automatically. If I navigate to the account page, it’ll show me as logged in. I can then check out using a valid card without running into any error messages.
This was tested using WooCommerce, Stripe, and the Storefront theme.
If this was something we can reproduce with only these active, then absolutely we want to open up a bug report about it. At a minimum, we’d want the messaging to be clear so the customer knows what to do. As it is now, we haven’t been able to reproduce this.
Take care,
