-
Notifications
You must be signed in to change notification settings - Fork 134
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
Something wrong with "payment_methods" endpoint response? #566
Comments
Nothing has changed to my knowledge, but I'll check with the team that owns this API. Is it happening for all payment methods? Or only particular types? (cards, paypal accounts, etc) |
It happens for cards, for sure. I don't know about other types as I'm not using them. |
Did some testing, and it looks like this is just affecting cards. PayPal accounts are reporting correctly for subscriptions. Very strange. |
Hey @crookedneighbor 👋, any updates on this? |
The team that owns this API is still investigating. I'll give them another ping about it. |
Just an update that I'll be working with the team that is responsible for this tomorrow morning to help with their investigation. |
Thanks for the update 🙇 |
I think we've figured out the source of the problem. Will let you know when a fix is out. |
This is fixed in sandbox and should be going to prod this week. I'll update here when it's fixed in production. |
Thank you so much! |
General information
Issue description
Hello,
I'd like to know If there are any recent changes to the
/payment_methods
endpoint?Specifically to the
hasSubscription
property of each payment method.Up to ~3 weeks ago, the
hasSubscription
prop of a payment method would betrue
when that payment method was "tied" to a subscription. That's not the case any more, though.The text was updated successfully, but these errors were encountered: