Something wrong with "payment_methods" endpoint response?
See original GitHub issueGeneral 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.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Get Accepted Payment Methods ENDPOINT not working?
BigCommerce Developers — Andy Nguyen (Customer) asked a question. ... Get Accepted Payment Methods ENDPOINT not working? ... Any problem with the V3 ......
Read more >Problems in attaching a PaymentMethod to a Customer using ...
The above code gives the error: You cannot attach a PaymentMethod to a Customer during PaymentMethod creation. Please instead create the ...
Read more >Error codes and messages - Adyen Docs
14_005 - Invalid payment method details. Cause: One reason could be that the recurring contract on a token might be missing. For example,...
Read more >Stripe API reference – Errors – curl
If the error is specific to the type of payment method, the payment method type that had a problem. This field is only...
Read more >Error codes - Docs - Checkout.com
This page describes the possible error codes you might receive. View a list of the possible response codes. Payments endpoint.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think we’ve figured out the source of the problem. Will let you know when a fix is out.
Thank you so much!