-
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
Use the customer ID saved in the subscription to process renewal payments #9065
Use the customer ID saved in the subscription to process renewal payments #9065
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.28 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works as described. 👍
Hi team, Thank you for fixing this issue. Just to double-confirm, has this fix been released for the latest version of WooPayments? |
[Release of WooPayments 8.0.0]
I found this, but I am just double-confirming here. |
That is correct, the fix is available now in version 8 |
…ents (#9065) Co-authored-by: Brett Shumaker <[email protected]>
Fixes #8892
Changes proposed in this Pull Request
When processing renewals using WooCommerce subscriptions, WooPayments will try to retrieve the Customer ID from the user meta. In most scenarios this is acceptable; however, we have received reports that after performing a migration, the Customer ID in the User meta may get lost, when this happens, a new Customer ID will be created, but this will cause an error since the Payment details stored in the subscription won't match the new Customer ID.
This PR will use the Customer ID saved in the subscription to make sure there are no mismatches between it and the payment details during renewals.
Testing instructions
Before
cus_INVALID
After
npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge