The plugin no longer allows users to enter account keys manually on live sites. While in WooCommerce Payment Settings and clicking “Finish set up” the same site offers two different buttons depending on if the URL is a localhost url or a live site url. The localhost version says “Enter account keys (advanced)” and the live version says “Create or connect an account”. This assumes that no live sites are being used for testing which is an incorrect assumption.
I have stopped using this plugin and have stopped recommending it to developers I teach because it makes it more difficult to add test keys to a WooCommerce site while building it and testing it.
Is there any plan to change the logic here and re-add the option to manually add keys regardless of the site URL?
This topic was modified 1 year, 2 months ago by Jonathon Leathers. Reason: Fixed a typo
While the plugin interface promotes easy onboarding with the “Create or connect an account” button for live sites, I wanted to emphasize that you do have the ability to enable Test Mode on live sites, which allows you to add the test keys and conduct necessary testing without processing real transactions.
To assist you better, could you please share screenshots showing the difference in the setup options between your live site and a localhost site? This information would help me in providing a more precise response.
This has nothing to do with anything on Stripe but has to do with the code written by the developers of this specific plugin. I only have one Stripe account that is permanently in test mode, that has never changed, but the code in this plugin has changed. You can see that below because the plugin offers different options depending on the URL.
Screenshot from a localhost site Clicking that link opens a pop-up modal to allow entering in live or test keys.
Screenshot from a live site Clicking that link takes you to https://connect.stripe.com/oauth/v2/authorize and forces you to fill out a lot of information that is irrelevant for a test store and there is no way to skip it or specify that you are just testing. Unless there is a way to get around this and use the interface from the screenshot above, this plugin is just unnecessarily more complicated for testing compared to the other WooCommerce Stripe plugins that exist.
I understand your concerns regarding the complexities of testing in the WooCommerce Stripe plugin. Indeed, the plugin has been designed to offer different options depending on the URL.
Please note that the reason you are redirected to https://connect.stripe.com/oauth/v2/authorize when clicking the link on a live site is to ensure the security of your transactions. This might seem a bit tedious, especially for a test store, but it’s essential for Stripe to verify the user’s identity. This also helps prevent having to go through the process again when one wishes to switch from test mode to live mode.
On the other hand, we also appreciate feedback from users and users can submit feature request directly from this link here.
As WooCommerce addon developers, we have some automated end-to-end tests to run with the Stripe payment gateway.
Since version 8.0.0, it’s not possible to setup account keys manually and we just disabled the tests.
Now we’re back on that as we would like to restore our tests, but it’s becoming a big headache…
First of all, (if I understand correctly, correct me if I am wrong) we need to create a real Stripe account with real information such as personal/company information, valid back account data, … and we cannot provide that for testing purpose only. We are not Stripe users, we just want to ensure Stripe is compatible with our addon.
Then, even if I hardly manage to create a real Stripe account (with random data), I see captcha when it comes to connect to Stripe from the “Connect or create an account” button. This is one more problem for our automated tests.
Could you re-evaluate the possibility to restore the advanced mode? (as it was in version 7.9.3)
Without that, I am afraid we will not manage to restore our automated tests on Stripe, which in the end could affect Stripe users…
Thanks
This reply was modified 11 months, 4 weeks ago by Pierre Sylvestre.
Thank you for reaching out and for sharing details on the issue. This is more of a development question rather than a support question. I’d suggest reaching out to our devs through a Feature Request here, or here.
You could also ask for insight related to that on either the WooCommerce Advanced Facebook group or the WooCommerce Community Slack. Many of our developers hang out there and will be able to offer insights into your question. You can also seek help from the following:
Hi @strategio and @jtleathers, I completely understand your concern and indeed this feature is preferred by some.
However, removing the ability to enter stripe keys manually is intentional and does not prevent store owners from connecting their Stripe accounts in test mode. In fact, it makes it easier and safer as you cannot connect a Stripe account that you are not logged into. Please note that security is important and should be prioritized in all cases.
Also, you can connect multiple sites to your Stripe account so having one website used for test purposes should not be a problem.
I hope this helps clarify things.
Viewing 8 replies - 1 through 8 (of 8 total)
The topic ‘Cannot manually enter account keys on live sites’ is closed to new replies.