sprobot

I have the same problem and came to the same conclusion. A fix would be appreciated. As it is now, I have to go into the database, find the updated token. and attach it to the subscription. It’s annoying. I’ve posted it here and emailed HPS directly. Their reply was basically that they might get around to it eventually…

Just wanted to add my voice to this. Since upgrading to reCaptcha v3 spam is way up. Please fix or revert back to v2.

Disabling Memcached solved the problem. Thank you for your help! Hopefully having Memcached disabled doesn’t impact site speed too much.

Thanks for the reply @hristo-sg!

Our cart, checkout, and user account pages are on the exclude list. The problem only appears to occur when the renewal action is triggered by a logged in administrator from the subscription management section in wp-admin. Apologies if I didn’t make that clear.

1.11.13 has fixed the problem. Thanks!

Thanks @markhagan!

This update gets us most of the way there. I can verify that the card is no longer charged and a token is created when the payment method is updated through the view subscription page. Unfortunately it does not save the new token to the subscription.

When payment fails and the customer follows the emailed “pay now” link to checkout, it does save a new card correctly, so that’s good! It’s just not saving it to the active subscription if done through the my account > view subscription page.

This still happens with all plugins off except Woocommerce, Woocommerce Subscriptions, and Woocommerce SecureSubmit Gateway.

Thanks for addressing this in he most recent update but it does not appear to have fully fixed the problem.

When a customer with an active subscription goes to My Account > Subscriptions > View Subscription > Change Payment Method, there is no longer an amount error when entering a new card or changing to a different saved card. However, it appears that when then new card is saved, it is charged for the subscription amount! This is a problem! The Change Payment Method page should only save a new token or switch tokens associated with the subscription, not charge it. The token will be charged the next time the subscription renews.

Thanks for addressing this so quickly! Problem solved.

@iv3rson76 Thanks! I’ll try that. I mainly use the staging site to make sure new and newly updated plugins don’t break anything. I don’t push it to live as I don’t want to overwrite customer data in the database. If I need to make non-database related changes to my live site I just manually upload them. So far using a subdomain with another installation of wordpress in a subfolder of my public_html folder has worked well enough for those times I need to check a plugin like this one where it needs the correct site url.

It has not. I had the same question. According to this it is in the works but there is no ETA:
https://www.ads-software.com/support/topic/feature-updates-2/#post-8649730

I had a similar problem with my host, Siteground. They use domain masking techniques to make it easier to push staging sites to the live site. Unfortunately these cause Braintree to see the staging site domain as the live domain. The only solution I found was to make a subdomain (eg. dev.mydomain.com) that doesn’t use the staging feature offered by Siteground and load a copy of my site on that. You’d have to contact your host for help on how best to do that.

Thanks! All good news.

Got this working on a subdomain with Siteground. Their staging environment uses domain masking techniques which break the account validation between Braintree and Woocommerce so I copied my staging site to a regular old subdomain that doesn’t use their staging environment.

Testing it out showed that, even if we were to convince all our customers to reenter their card data, there is no way for them to manage their cards within Woocommerce. Then I noticed this was reported a few months ago and marked as a bug/feature request but still hasn’t been implemented. (https://www.ads-software.com/support/topic/cant-add-payment-methods/)

It’s really disappointing we’re being forced away from the Skyverge plugin without an equally functional alternative, in addition to not having a customer data migration path.

Also at this time, even if customers re-enter their card data, this plugin does not provide a way for them to manage their cards through the Woocommerce My Account section. At least two months since this was added as a bug/feature request and still hasn’t been added.

See: https://www.ads-software.com/support/topic/cant-add-payment-methods/

Adding my voice to this.

Braintree has our customer data > Paypal owns Braintree > Paypal has our customer data. Migration is possible and should be part of this if U.S. customers are being forced away from the Skyverge extension.

• This reply was modified 8 years, 1 month ago by sprobot.