Skip to content
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

Closed
antonisprovidakis opened this issue Apr 26, 2021 · 10 comments
Closed

Something wrong with "payment_methods" endpoint response? #566

antonisprovidakis opened this issue Apr 26, 2021 · 10 comments

Comments

@antonisprovidakis
Copy link

General information

  • SDK version: 3.73.1
  • Environment: Sandbox
  • Browser and OS: Chrome 90.0.4430.85 (64-bit) on MacOS 10.15.7

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 be true when that payment method was "tied" to a subscription. That's not the case any more, though.

@crookedneighbor
Copy link
Contributor

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)

@antonisprovidakis
Copy link
Author

antonisprovidakis commented Apr 27, 2021

It happens for cards, for sure. I don't know about other types as I'm not using them.

@crookedneighbor
Copy link
Contributor

Did some testing, and it looks like this is just affecting cards. PayPal accounts are reporting correctly for subscriptions. Very strange.

@antonisprovidakis
Copy link
Author

Hey @crookedneighbor 👋, any updates on this?

@crookedneighbor
Copy link
Contributor

The team that owns this API is still investigating. I'll give them another ping about it.

@crookedneighbor
Copy link
Contributor

Just an update that I'll be working with the team that is responsible for this tomorrow morning to help with their investigation.

@antonisprovidakis
Copy link
Author

Thanks for the update 🙇

@crookedneighbor
Copy link
Contributor

I think we've figured out the source of the problem. Will let you know when a fix is out.

@crookedneighbor
Copy link
Contributor

This is fixed in sandbox and should be going to prod this week. I'll update here when it's fixed in production.

@antonisprovidakis
Copy link
Author

Thank you so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants