-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with Woo Stripe Gateway - "Your payment information is incomplete." error on /order-pay/ checkout flow #7824
Comments
While addressing the bug here may be necessary, I would recommend we take a bigger picture look at this to consider if we could better educate the merchant about potentially conflicting payment gateways being enabled alongside each other. |
This issue impacts Checkout UI, so assigning to Heisenberg (based on team responsibilities Pc2DNy-3z-p2) @FangedParakeet. Assigning as part of Gamma Triage process PcreKM-yM-p2. |
Hey @Brianmitchtay! Thanks for including detailed reproduction steps in your report. Do you recall the WooPayments and Woo Stripe versions used in your tests? I haven't been able to reproduce the on the latest versions of both plugins. It's possible that it's been fixed with some recent changes to either plugin, but I'd like to try reproducing with versions matching your tests. |
Trying further to reproduce the problem here, I tested using Woo Stripe 7.7.0 and WooPayments 6.8.0, WooCommerce 8.3.1, while using a block based theme(Twenty Twenty-Three). First I've ensured that Woo Stripe is active but disabled. I've then created a guest order with no address details then proceeded to the customer payment page, both logged in and logged out. So far, all test payments have processed successfully and the error described here hasn't shown up. I'll close this for now, but if you're still able to reproduce it, please re-open and we can pin down the exact conditions. |
Hi @mdmoore thanks for following up. I can still replicate. The user was running:
Like you had in your tests. However I just tested again and can still replicate with the following (latest) versions on my testing site. WooCommerce Stripe Gateway: by WooCommerce – 7.9.0 I fully acknowledge that this testing site has been used for a lot. So I'll also set up a clean Jurassic Ninja site to confirm. SSR enclosed `
### WordPress Environment ###
WordPress address (URL): https://woolivetesttesttest.mystagingwebsite.com Server EnvironmentServer Info: nginx SUHOSIN Installed: – DatabaseWC Database Version: 8.5.2 Post Type Countsaddify_whp: 1 SecuritySecure connection (HTTPS): ✔ Active Plugins (3)WooCommerce Stripe Gateway: by WooCommerce – 7.9.0 Inactive Plugins (79)Akismet Anti-spam: Spam Protection: by Automattic - Anti-spam Team – 5.3.1 Dropin Plugins (2)advanced-cache.php: advanced-cache.php SettingsAPI Enabled: ✔ Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog) Connected to Woo.com: ✔ WC PagesShop base: #5 - /shop/ ThemeName: Storefront TemplatesOverrides: – WooPaymentsVersion: 7.1.0 AdminEnabled Features: activity-panels Disabled Features: customize-store Daily Cron: ✔ Next scheduled: 2024-01-29 18:57:50 -09:00 Action SchedulerComplete: 24,180,603 Pending: 16 In-progress: 1 Failed: 14,423 Status report informationGenerated at: 2024-01-28 14:28:35 -09:00 |
A few updates here. This must be some kind of deeper conflict on the site I was using to test.
I'll close this issue back up now. If anything it seems it likely would need to be re-opened in the Stripe repo if we're able to determine the deeper cause of the conflict |
Thanks for taking the time to test so thoroughly @Brianmitchtay! Feel free to re-open here as well if WooPayments is involved. |
Describe the bug
When the WooCommerce Stripe payment gateway is enabled and
To Reproduce
Actual behavior
While the Stripe payment gateway plugin is active on the site, the
/order-pay/
flow does not function and throws an error.Screenshots
Expected behavior
Ideally, payment processes should function whether or not a merchant has the Stripe gateway installed and active on the site as well
Desktop (please complete the following information):
Additional context
This was brought to our attention in 7399911-zd-a8c
The text was updated successfully, but these errors were encountered: