DennisHermannsen Posted October 4, 2020 Share Posted October 4, 2020 (edited) It's not shocking that it's not fixed. It can be quite difficult to fix something that you don't have a lot of information about (like why it happens, how often it happens, for who it happens etc). I've been trying to compare our cases of this bug, and I have absolutely no idea why it happens - there's no common thread - and when I finally think I have found the common thread, there's a case that disproves my theory. What actually is shocking is that, despite this thread being very active, WHMCS hasn't dropped by to say anything for a long while. Bugs can be difficult to fix. Giving a written update about a specific bug isn't that difficult. Instead of gathering information through multiple tickets, maybe WHMCS should use this thread (or create a new thread) to gather all the info they could. Other users could then voice their own experiences. Edited October 4, 2020 by DennisHermannsen 0 Quote Link to comment Share on other sites More sharing options...
wsa Posted October 5, 2020 Share Posted October 5, 2020 13 hours ago, DennisHermannsen said: Bugs can be difficult to fix. Giving a written update about a specific bug isn't that difficult. Instead of gathering information through multiple tickets, maybe WHMCS should use this thread (or create a new thread) to gather all the info they could. Other users could then voice their own experiences. Well they check everything because I give all login information I spent hrs with them and they find where is the bug 0 Quote Link to comment Share on other sites More sharing options...
DennisHermannsen Posted October 5, 2020 Share Posted October 5, 2020 Just now, wsa said: Well they check everything because I give all login information I spent hrs with them and they find where is the bug But that doesn't mean that they know why the bug happens. They can't just fix something if they don't know why it happens. 0 Quote Link to comment Share on other sites More sharing options...
hkhost Posted October 6, 2020 Author Share Posted October 6, 2020 12 hours ago, DennisHermannsen said: But that doesn't mean that they know why the bug happens. They can't just fix something if they don't know why it happens. Thank you for your very useful comments. We will continue waiting for this issue to be fixed. I guess 1 year is not enough time. 0 Quote Link to comment Share on other sites More sharing options...
DennisHermannsen Posted October 6, 2020 Share Posted October 6, 2020 I don't think I asked to be misunderstood, but I guess people can't see beyond the tip of their own nose... Let me rephrase in bullet points: It's very annoying that this hasn't been fixed This issue should have gotten more focus WHMCS should have given a statement about this issue instead of handling everything through tickets however: You can't just magically fix an issue without knowing why it happens I tried comparing our cases, and there's no common thread for the issue 0 Quote Link to comment Share on other sites More sharing options...
wsa Posted October 6, 2020 Share Posted October 6, 2020 This what whmcs.com email me After some further, in depth and detailed analysis, I have found one point of failure during the checkout. It appears that the combination of having the TOS acceptance checkbox and the captcha, can cause the validation of the captcha to not be performed within the attempt to create the PaymentIntent over with Stripe. This happens when the user does not tick the TOS acceptance, then after it errors informing them of such, they do tick the TOS checkbox but don't complete the captcha challenge again (which has reloaded). Essentially, an uncaptured transaction could show in Stripe, as a PaymentIntent is incorrectly created after the captcha is not completed following the failure to accept the TOS in the checkout. I have reproduced that situation and opened up case MODULE-7478 with our development team to have this reviewed. Whilst I cannot provide an estimated time for completion for this, once we resolve cases and push features they are available at our change log, here: 0 Quote Link to comment Share on other sites More sharing options...
DennisHermannsen Posted October 25, 2020 Share Posted October 25, 2020 I've found something different. We started having a lot of uncaptured payments. All the uncaptured payments appeared twice in the Stripe Dashboard. It was not until yesterday where multiple new clients contacted us that I knew why.. Apparantly, the MaxMind Fraud module is marking random orders as fraud. The orders' fraud score is way below what we have configured the module to mark fraud orders by. Legit orders with a fraud score of 0.1 is being marked as fraud (when they should only be marked if the fraud score is 20+). All these orders is going to Uncaptured Payments in Stripe. Is anyone seeing the same as we do? 0 Quote Link to comment Share on other sites More sharing options...
wsa Posted October 26, 2020 Share Posted October 26, 2020 I get that one time but this uncaptured payments alot time and whmcs could take a year they fix this like they did with mailchimp module take a year. 0 Quote Link to comment Share on other sites More sharing options...
wsa Posted October 27, 2020 Share Posted October 27, 2020 new version is out but don't fix the more important bugs 0 Quote Link to comment Share on other sites More sharing options...
pjs32 Posted November 10, 2020 Share Posted November 10, 2020 We have found that if a order is set to fraud by maxmind - the payment is still done on Stripe- but is showing as uncaptured. Seems to be an issue with Maxmind module? 0 Quote Link to comment Share on other sites More sharing options...
wsa Posted November 10, 2020 Share Posted November 10, 2020 This what whmcs email me 0 Quote Link to comment Share on other sites More sharing options...
pjs32 Posted November 10, 2020 Share Posted November 10, 2020 6 minutes ago, wsa said: This what whmcs email me We have already turned off TOS acceptance checkbox and the captcha but still we get uncaptured payments . for us - it looks like the maxmind module causing the issues. 0 Quote Link to comment Share on other sites More sharing options...
hoya8 Posted January 28, 2021 Share Posted January 28, 2021 We are now at WHMCS8.1 and STILL have this uncaptured issue.... 0 Quote Link to comment Share on other sites More sharing options...
hoya8 Posted January 29, 2021 Share Posted January 29, 2021 btw we do not use maxmind let see how long will this take for WHMCS to fix.... 0 Quote Link to comment Share on other sites More sharing options...
zomex Posted February 26, 2021 Share Posted February 26, 2021 Using WHMCS V8.1.3 and would you believe it, the same error has not been resolved. Stripe payment un-captured, the gateway log for Stripe Webhooks shows the Result as "Client Not Found". This is for a new client and new payment. Had to login to Stripe, capture the payment then manually add the transaction in WHMCS. -------- Another issue was with a PayPal payment for a new client, not automatically marked as paid even though it went through with PayPal. Had to manually add the transaction. The result for PayPal showed as "Subscription Created: No invoice found". 0 Quote Link to comment Share on other sites More sharing options...
yogdigital Posted April 6, 2021 Share Posted April 6, 2021 I'm still getting this error on 8.1.3. Does anyone have a fix? I'm using stock themes and still getting this issue. Does anyone have a work around? Incredible frustrating to have to manually capture the payment in stripe and fulfil the order manually. 0 Quote Link to comment Share on other sites More sharing options...
wsa Posted April 7, 2021 Share Posted April 7, 2021 yes sometime I get also and they want more money of whmcs but they can not fix all this old bugs that peoples report a year ago 0 Quote Link to comment Share on other sites More sharing options...
D9Hosting Posted July 22, 2021 Share Posted July 22, 2021 Add us to the list of users seeing this issue in 8.13. Just had a PO'd client get in touch with us because he "paid" us for an order that we had no record of. 0 Quote Link to comment Share on other sites More sharing options...
UnwilfulExpenditure Posted July 22, 2021 Share Posted July 22, 2021 15 hours ago, D9Hosting said: Add us to the list of users seeing this issue in 8.13. Just had a PO'd client get in touch with us because he "paid" us for an order that we had no record of. Ouch - This is really awful! A billing software that cannot bill people! 😂 You would think staff would be all over this, Even with platitudes to make people think it's getting attention! 0 Quote Link to comment Share on other sites More sharing options...
D9Hosting Posted July 26, 2021 Share Posted July 26, 2021 We've got one client who is managing to trigger this error every time he orders something yet it looks to be fine for everyone else. The error he is getting is related to the capatcha on the checkout page (using invisible recapatcha) so for now I've just disabled the capatcha for that page. 0 Quote Link to comment Share on other sites More sharing options...
myautodj Posted July 30, 2021 Share Posted July 30, 2021 (edited) Yes same problem after a couple days of non-support form the WHMCS support department 😞 Has nothing to do with a custom template, nothing to do with Stripe, a guest should not be able to submit payment period. My "guests" made 8,000 + charge attempts in one week all with different emails and the Apache log matches the ip addresses and times in the Stripe log exactly Edited July 30, 2021 by myautodj 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted August 13, 2021 WHMCS Support Manager Share Posted August 13, 2021 Hi all, I can confirm there are no generalised issues with the Stripe module in v8.1.3 or 8.2.1. On 2/26/2021 at 6:21 PM, zomex said: Using WHMCS V8.1.3 and would you believe it, the same error has not been resolved. Stripe payment un-captured, the gateway log for Stripe Webhooks shows the Result as "Client Not Found". This is for a new client and new payment. Had to login to Stripe, capture the payment then manually add the transaction in WHMCS. @zomex, I couldn't locate a ticket in your account where our team assisted with this in the past 12 months. Please do share the Ticket ID with me. If you're currently experiencing and issue with the stock theme and order form template (twenty one and standard cart respectively), please do open a ticket so we can investigate. On 4/6/2021 at 7:47 PM, yogdigital said: I'm still getting this error on 8.1.3. Does anyone have a fix? I'm using stock themes and still getting this issue. Does anyone have a work around? Incredible frustrating to have to manually capture the payment in stripe and fulfil the order manually. @yogdigital, I wasn't able to locate an account or license using the details on your Community account. If you're experiencing an issue in either version, could you please share your Ticket ID so I may follow-up? On 7/22/2021 at 9:10 AM, D9Hosting said: Add us to the list of users seeing this issue in 8.13. Just had a PO'd client get in touch with us because he "paid" us for an order that we had no record of. @D9Hosting, 1. I see we last discussed Stripe issues about 5 months ago. If you're still experiencing the same error issues after the troubleshooting steps I provided, please do update the ticket with the information and access credentials requested, so we can investigate further. 2. A known cause of a "recpatcha verification failed: timeout-or-duplicate" error was resolved in v8.1.1 and above: MODULE-7569 - Correct reCAPTCHA error with Stripe https://docs.whmcs.com/Changelog:WHMCS_V8.1.1#Modules We've since made further improvements to recaptcha invisible (albeit it a different error - Please complete the captcha and try again) handling with Stripe in 8.2: MODULE-7600 - Correct Invisible reCAPTCHA error with Stripe https://docs.whmcs.com/Changelog:WHMCS_V8.2.0_Beta_1#Modules Please do apply the update, and don't hesitate to create a new ticket if you're still experiencing any captcha errors with Stripe. On 4/7/2021 at 1:20 PM, wsa said: yes sometime I get also and they want more money of whmcs but they can not fix all this old bugs that peoples report a year ago @wsa, The issue we discussed via ticket about 8 months ago was addressed in v8.1.0: MODULE-7478 - Prevent Stripe PaymentIntent creation when TOS and captcha validation fail https://docs.whmcs.com/Changelog:WHMCS_V8.1.0_RC_1#Modules Occasional uncaptured payments are to be expected under normal operation in the event that a client's card is declined due to a Radar rule on your Stripe account. If you're experiencing them in other circumstances, please don't hesitate to get back in touch via ticket. On 7/30/2021 at 11:51 AM, myautodj said: Yes same problem after a couple days of non-support form the WHMCS support department 😞 Has nothing to do with a custom template, nothing to do with Stripe, a guest should not be able to submit payment period. My "guests" made 8,000 + charge attempts in one week all with different emails and the Apache log matches the ip addresses and times in the Stripe log exactly @myautodj, This is a distinct issue, so have provided commentary in your thread. 0 Quote Link to comment Share on other sites More sharing options...
jds Posted March 22, 2022 Share Posted March 22, 2022 Is this still ongoing as I'm getting this in 2022 after setting up stripe as a gateway 😱 0 Quote Link to comment Share on other sites More sharing options...
sonuyos Posted January 2, 2023 Share Posted January 2, 2023 3yrs since reported. 2023 now. 8.6.1 version. Still not fixed. I have weekly 3-5 transaction going into uncaptured and ruining clients. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted January 10, 2023 WHMCS Support Manager Share Posted January 10, 2023 Hi @sonuyos, Can you please review the uncaptured pre-authorisations in your Stripe Dashboard on the Payments page, and confirm whether they were blocked by a Radar rule or a failed 3DSecure attempt? Occasional uncaptured payments are to be expected under normal operation in the event that a client's card is declined due to a Radar rule on your Stripe account. Such pre-authorizations will automatically expire after 7 days: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.