Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter paltmanfedmed

    (@paltmanfedmed)

    @venuslovedolls7

    We ultimately had to go with a different vendor for payment gateway.

    Thread Starter paltmanfedmed

    (@paltmanfedmed)

    Hey @carolm29

    Thanks for the reply. We have the same payment gateway using WooCommerce Authorize.Net Gateway By SkyVerge. However, the error does not even process through the gateway as it does not even get that far. There are no failed transactions. Just the generic error that stops them before even processing.

    While I am not sure if the customer is logged in first or not when placing the order I will say that we have asked a couple customers experiencing the issue to create new accounts and then try the order again it did go through without error. Although we have had one report from one that after they created a new account that the first order went through with no problem the second order displayed the error again. We are waiting to her back from others on a a second purchase attempt. So very strange that makes no sense.

    Thread Starter paltmanfedmed

    (@paltmanfedmed)

    Hey thanks for the follow up. I should have mentioned before that there are several customers that have had this same problem. They have tried different cards and received the same error. This only occurred after we updated to 8.7.0. It is strange that it only affects some but not all. I thought it was customer based error as well but when they have existing accounts and had no problems before the update I can only point to the update.

    I know it was major version update so wondering if something changed on how the accounts are handled. We are going to ask those that have that issue to try to create a new account and try the purchase again. Not sure if the update might have affected some accounts.

    Thread Starter paltmanfedmed

    (@paltmanfedmed)

    Hey thank you for the follow up. This problem is challenging because if it was a plugin or theme then it would affect all transactions or purchase attempts. However, It only affects a some as we are still seeing other purchases go through for customers without problems.
    At first we thought it was how the customer was entering in their information but we ruled that out with our own internal test purchase.

    Here is the status report – https://gist.github.com/fmwebdev/bfe4b0fe8384c9cfe888c56b124b0076

    I hope you can help.

    Having similar issue after updating to 8.7.0. Not everybody though as still seeing transactions go through but some customers are getting generic error – “an error occurred,  please try again or try an alternate form of payment.” Only started after update. Don’t want to revert back to 8.6.1 but might have to. I thought it was related to browser update compatibility but we ruled that out as well. Very strange why some but not others.

    I had a similar issue with Gmail users not receiving pw reset emails. This has to do with Gmail / Yahoo changing requirements to help fight spam abuse, etc. The fix will require you to update your DNS records, specifically including: SPF with IP, DMARC and DKIM TXT records. Your hosting provider support should be able to help you with that. After fixing gmail users were receiving website emails again. Hope this helps.

Viewing 6 replies - 1 through 6 (of 6 total)