Shravan Bhaskaravajjula
Forum Replies Created
-
Hello @xpconversions,
We sincerely apologize for any inconvenience caused earlier. We want to inform you that we have addressed the issue and already released the fix.If you’re still facing any difficulties or have any questions, please don’t hesitate to reach out—we’re here to help! Your satisfaction is important to us, and we strive to make your experience with the plugin as smooth as possible.
If the issue has been resolved to your satisfaction, we would greatly appreciate it if you could reconsider your rating and update it to reflect the improvements. As a free plugin helping users integrate Stripe payments seamlessly, positive ratings help us continue supporting the community and improve the plugin for everyone.
Thank you again for your understanding and support!
Hello @alv212,
We sincerely apologize for any inconvenience caused earlier. We want to inform you that we have addressed the issue and already released the fix.If you’re still facing any difficulties or have any questions, please don’t hesitate to reach out—we’re here to help! Your satisfaction is important to us, and we strive to make your experience with the plugin as smooth as possible.
If the issue has been resolved to your satisfaction, we would greatly appreciate it if you could reconsider your rating and update it to reflect the improvements. As a free plugin helping users integrate Stripe payments seamlessly, positive ratings help us continue supporting the community and improve the plugin for everyone.
Thank you again for your understanding and support!
Hello @abossola,
To troubleshoot the issue with the webhook endpoint associated with your Stripe account, you can follow these steps:
- Verify the webhook endpoint URL: Make sure the URL is correct and free of typos. Confirm that the URL is publicly accessible on the internet and can be resolved to the expected IP address using a DNS tool like?
nslookup
?or?dig
. - Check SSL/TLS certificate and configuration: If you are receiving a “TLS error,” it indicates an SSL/TLS issue. Use a tool like SSL Labs’ SSL Server Test to check for any issues with your TLS certificate or configuration. Resolve any reported issues, such as incomplete certificate chains or security errors.
- Confirm firewall and network configuration: Ensure that connections from Stripe are not blocked by a firewall or network configuration. You may need to work with your hosting provider to confirm that the IP addresses Stripe uses for webhooks can access your webhook endpoint’s URL.
If you continue to experience trouble after performing these steps, you may want to reach out to Stripe support for further assistance.
For more information about troubleshooting webhook issues and verifying webhook events, refer to the webhooks troubleshooting guide.Or else they can try delete webhook and create new
Let us know if we could be of any further assistance.?
Hello @josssv,
The card data is encrypted by Stripe, and they do not provide the user’s card details, nor do they allow us to store it. So, there is no way to access or know which card the user has used.
Hope this helps.
Hello @deyanch,
Thank you so much for your wonderful review and ratings.
Reviews like these encourage us to put in more effort to serve you.
Please feel free to get in touch if you need help with anything.
Thank you & Have a great day ahead!
Forum: Reviews
In reply to: [WooCommerce Cart Abandonment Recovery] Great PluginHello @laser558,
Thank you so much for your wonderful review and ratings.
Reviews like these encourage us to put in more effort to serve you.
Please feel free to get in touch if you need help with anything.
Thank you & Have a great day ahead!
Hello @xpconversions,
Thank you for sharing the error information with us. Our developers have already addressed the “Invalid order! The nonce security check didn’t pass” issue, and the fix will be released soon.
Thanks for your patience and cooperation.
Hello @xpconversions,
I’m truly sorry to hear about the experience you’re having, and I completely understand how challenging it must be to manage pending orders manually.
I want to assure you that we’re looking into this and help resolve this issue as quickly as possible.
To better understand the problem, could you please provide a bit more information? Specifically:
Product Type: What type of product are you selling? This will help us pinpoint whether the issue might be related to specific product settings or the checkout flow.
Page Details: Is the issue occurring only on the checkout page, or is it happening on both the checkout and upsell pages? Knowing this can help us replicate the issue on our end and find a solution.
Version Details: You mentioned that the issue started with version 1.9.2. Are you using any other plugins that might have been updated around the same time? Sometimes, conflicts between plugins can cause issues like this.
We know how critical it is for your business that your orders process smoothly and automatically. If you can provide these details, it will greatly assist our team in replicating the issue so we can work on a fix.
We’re committed to making this right for you. Once we have more information, we’ll do everything we can to address the issue promptly.
Thank you for your patience and understanding.
Hello @abossola,
If you disable the plugin but keep the webhook endpoint active, it’s possible that existing subscriptions will continue to be billed, but you might encounter errors or incomplete notifications, as the plugin responsible for processing those webhooks is inactive.
Please review the Stripe webhook logs by logging in to your Stripe account and check the webhook logs. This will show you the exact error messages being returned. You can share these details with us, so we can assist you further.
Hello @anonymized-23115161,
The email form field is not editable if you use the modern checkout templates, please refer to this screenshot: https://bsf.d.pr/i/52OULP.
Let me know if you have any questions or concerns left unanswered as I would be more than happy to assist you further.
Forum: Plugins
In reply to: [WooCommerce Cart Abandonment Recovery] False cart recovery measurementHello @ekumbangsila,
Apologies for the delayed response. I have tried multiple times, but I could not replicate the scenario you mentioned. Could you please share a screen recording so that we can better understand the issue?
Looking forward to hearing from you.
Hello @hudsontek,
We haven’t received a response from you for some time now. Based on the elapsed time and considering that you may have found a solution by now, I’m going to mark this thread as resolved.
However, please feel free to start a new thread if you have any further questions or require additional assistance in the future.
We’re here to help whenever you’re ready to continue.
Thank you for your understanding and cooperation.
Hello @michell26,
We haven’t received a response from you for some time now. Based on the elapsed time and considering that you may have found a solution by now, I’m going to mark this thread as resolved.
However, please feel free to start a new thread if you have any further questions or require additional assistance in the future.
We’re here to help whenever you’re ready to continue.
Thank you for your understanding and cooperation.
Hello @gagan123kumar,
As per my colleague’s suggestion to contact on our support, I will mark this thread as closed.
However, please feel free to start a new thread if you have any further questions or need additional assistance in the future.
Thank you for your understanding and cooperation.
Forum: Plugins
In reply to: [WooCommerce Cart Abandonment Recovery] Conversion Not TrackedHello @vegitoss3,
We haven’t received a response from you for some time now. Based on the elapsed time and considering that you may have found a solution by now, I’m going to mark this thread as resolved.
However, please feel free to start a new thread if you have any further questions or require additional assistance in the future.
We’re here to help whenever you’re ready to continue.
Thank you for your understanding and cooperation.
- Verify the webhook endpoint URL: Make sure the URL is correct and free of typos. Confirm that the URL is publicly accessible on the internet and can be resolved to the expected IP address using a DNS tool like?