#RyanLuttrell-Subscription
past tide
Hi, let me take a look here
My assumption was that even with CAU, it default source would work. Can you share the request id for the source creation? Or any request id that would have this customer object so I can further review this? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
past tide
On this specific request, I think you're mixing up the legacy source and the new PaymentMethod API.
For this reason, you're seeing this error: resource_missing on that request
compact plume
Interesting, ok I'll take that back to my team. May I reach back out here if that doesn't work on Monday?
past tide
Yes, absolutely!
kind slate
@compact plume re-opened your thread. I will catch up and help
Do you have a new question/info since we closed the thread?
compact plume
Man, your team is incredible at responding, thanks so much!
Yes, I have an updated request ID that better demonstrates the issue
req_OuHwdaEadAIjvK
kind slate
Thanks for the info. Server is a but busy so I may be another minute, reading through now...
compact plume
No problem at all, thanks for your support!
kind slate
Can you try retrieving this card again but with our retrieve source API call? https://stripe.com/docs/api/sources/retrieve
I thought you should be able to retrieve it with the payment method API but it looks like this call is similar to the last one where my colleague implied that you couldn't
compact plume
Looking into it now
This is an example of us hitting the api you requested: req_xUcbeFtxjd7dae
compact plume
Can you confirm that the same issue is happening on this one as well?
kind slate
Whoops apologies, I had to step away but didn't quite hand off this question properly. Looking in to this again
compact plume
No worries, thank you!
kind slate
And one more API request to try while I am looking in to this. Can you try the version of this method that takes the customer and card ID?
And to be clear, before CAU, you can look up these cards properly with that first retrieve payment method call that you sent the request ID for?
compact plume
Yes, before CAU we were not having any issues retrieving payment method
kind slate
Okay I see where I was misunderstanding this. I can see where these cards are associated in our backend to where we are automatically charging the right card but I am not sure why you can't look up the new ID that we set during the update.
I have a feeling I will need to file something to address this, we shouldn't give you an ID that is valid but you can't look up.
While I'm looking in to this, is there something that this is currently breaking in your system? I look in to if there is a good workaround or recommended way of handling this
compact plume
Thanks so much, yes all of that is correct
Yes, this is breaking our our system for users where this occurs so if there is a good workaround while the bug gets fixed, that would be greatly appreciated as it is impacting a high number of customers
Just to clarify:
We fetch the subscription which returns referencing the old credit card id (the one we can't find), we need to be able to identify the id of the new CC that substituted the old one to be able to update the subscription. We can't use the 'default payment method', especially if the customer is using multiple credit cards for multiple subscriptions.
kind slate
Gotcha, thank you. Getting the original ID somehow would probably be the workaround, when these cards are automatically updated like this, the original ID is still the one to use, but I am not sure how you can properly do this when you have multiple cards on a customer.
Can you try retrieving this customer, cus_9Co0vOtJy2uoBn and use expansion on the default_source field? I am wondering if you can get more info on these cards from there. https://stripe.com/docs/api/expanding_objects
Because if so you may be able to at least match up new ID to old ID by last4. I am going to file something with our engineering team for this to fix it and am still checking if there is some easier way for you to work with this in the meantime
Can you DM me your email? I will grab the ticket from your support interaction and can keep you updated on the progress of the fix
compact plume
Done!
Unfortunately we have tried that but we don’t know which was the original last four digits
kind slate
Whoops, I didn't realize that last 4 could change when a card is updated like this.
Okay I found your ticket with the email addresses that you sent me. I will raise this issue with the engineering team and see what workarounds may be feasible in the mean time
It might be a bit before I can get back to you, so I think it would be best to table this thread for now and I can get back to you via email. Does that sound okay to you?
compact plume
That sounds great, thank you so much for your support, it has been greatly appreciated. One other quick question, are there any events that we could listen for when CAU occurs?
Even if it’s just something like:
customer.source.updated
payment_method.attached
payment_method.automatically_updated
payment_method.updated
so we could listen to find that the old CC does not exist and update the subscription ourselves.
kind slate
From my understanding, payment_method.automatically_updated should be the one to listen to here