#bmizerany
1 messages · Page 1 of 1 (latest)
Hi, taking a look at the request id now.
Thank you!
Can you share a request if where it worked?
Sure one sec
I've never seen it work with subscription schedules if that is what you're asking. I can create a request that works for customers' default_payment if that is what you're asking.
I'm just trying to compare the two if you had an example. I can also test this on my end
Here the card works with /v1/customers: req_i2CMN0BstylNwf
Yeah, it does not appear that we support this in test mode. I'm replicating this on my end and will flag this to the team.
Oh interesting. Thank you. Do you think you'll hear back from them soon?
Is it that test cards are not supported on subscriptions in test mode, or that setting cards on subscriptions in general is not supported?
I'm testing around on my end
ty
I was able to test on end for both Subscription and Subscription Schedules. I can confirm that it's expected behavior that it does not work.
Adding more details..
On Subscription and Subscription Schedules, you'd need to add this to the customer as the default payment method first and can use it on Subscriptions.
Okay, but I don't want to use default payment methods in production. What's a way to ensure my code is working correctly without being able to write unit tests to confirm it works as expected?
You can test this on your client side, you can pass the card number: https://stripe.com/docs/testing?testing-method=card-numbers#americas instead and look at the resulting subscription object
right but card numbers do not work when using SDKs though, right?
When writing test code, we don’t recommend using a card number. Instead, use the corresponding PaymentMethod, such as pm_card_visa.
We don’t recommend using card numbers directly in API calls or server-side code, even in test mode
Not on the server side, but on the client side on your integration.
you mean in a browser?
Does that mean that only manual testing using a browser to collect fake card numbers and manually check the subscription ?
That is correct
😦
Does the team have plans to enable test cards with subscriptions so that integration developers can test their code?
Our customers would prefer to choose cards on a subscription-by-subscription basis, and we want to ensure we have our logic right and well-tested around that.
I'll share this feedback with the team for future product reiterations.
Thank you.