#tofutiger
raven robin
warm kraken
sure, thanks for helping! It's sub_1MYmfDLWEC1vqbW5KhZ0pLzj
lusty hazel
depending on how the payment details are created you will get a default_source or a default_payment_method
warm kraken
here's an example of our live subscription that has the default_payment_method sub_1JanIEDLh2JRoEHWAeH3lJbh
lusty hazel
in the creation request of this subscription https://dashboard.stripe.com/test/logs/req_YgWuhFiEiaysmP you specified the default_source
warm kraken
ah, interesting, I did this through the dashboard
is there a way to know when the default_source vs the default_payment_method would be set? would appreciate further reading material on this
lusty hazel
I did this through the dashboard
exactly why it was created as a Source not as a Payment Method
if you don't use the Tokens/Sources API you don't have to worry about default_source
but since you used the dashboard to create the subscription/payment details, the dashboard is still using the Sources API why it resulted in a card_xxx instead of a pm_xxx
warm kraken
ah I see, thanks for explaining that. How can I add the payment method to this subscription? Sorry, I did not originally create this webhook, only adding a feature to it.
lusty hazel
using the dashboard you mean?
warm kraken
either that or another method. I'm reading this (https://stripe.com/docs/api/payment_methods/attach) but it seems like it would attach to the customer not the subscription? Also not sure if it'd work for a customer created in the test clock
lusty hazel
Also not sure if it'd work for a customer created in the test clock
not really related
don't you have a workflow in your app that handles creating subscriptions and collecting payment methods?
warm kraken
yes. does the test clock affect those objects though?
lusty hazel
yes you just need to have it on the customer object
warm kraken
sorry, I don't think I'm following
lusty hazel
if you have the test clock on your customer object
the subscriptions will be tied to that test clock
the payment methods are not really affected by test clocks
please read through this doc to learn more about test clocks
warm kraken
but that customer wasn't created through our app, is it possible to link it to a user in our app?
lusty hazel
I'm not sure how would I be able to know what's going on in your app
warm kraken
I see, but you mean that the test clock objects do exist? then I can figure out how to link it. I thought it was just a simulation that had no relation to the rest of the stripe environment
lusty hazel
you can't link it to existing objects
you can create a new customer with a given test clock
but you can't add a test clock to an existing customer
once the test clock is attached to that customer you can create up to 3 subscriptions for that customers that are bound to this test clock
warm kraken
gotcha, thanks, that makes sense
I believe I have changed the payment method now through our app's flow, but I appear to still get the same error? is there a way through the dashboard to look at the subscription object?
lusty hazel
I have changed the payment method
for the customer? or for the subscription?
warm kraken
for the subscription
lusty hazel
is it this request https://dashboard.stripe.com/test/logs/req_IYcENO7X0AUlK9 ?
warm kraken
yea, that was my second attempt, there was also this req_HNbXNJZOleKwYG