#cmos
wary kernelBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- cmos-log-errors, 3 days ago, 9 messages
spare scaffold
There's not a way to email that link via the api
You'd have to use your own email service to email them a link
raven siren
Is there anywhere to generate that link? I see where to create payment links, and I see where to update payment methods, but not how to generate a payment method update link.
spare scaffold
Let me ask a colleague
raven siren
Thanks, it looks like some sort of hash is what gets generated like this . Not sure if that helps https://billing.stripe.com/p/subscription/update_payment_method_link/MASSIVE_HASH_HERE
spare scaffold
Ok so looks like this is a dashboard-only feature unfortunately. We do have this flow using the customer portal: https://stripe.com/docs/customer-management/portal-deep-links which allows you to update a default payment at the customer level. This won't help if the default payment method is already set at the subscription level, since this takes precedence: https://stripe.com/docs/api/subscriptions/object#subscription_object-default_payment_method.
raven siren
Dang, so in my instance what is happening is essentially bad postal codes, so a user has an active subscription and they get charged and it fails postal code check... So if I am understanding correctly I could make a portal deep link let them update it, then separately from that figure out a way to delete / remove the default payment method from the subscription and apply the customer level default. I could maybe do this with webhooks? payment_method.attached would presumably fire if they update in the customer portal?
spare scaffold
It would, yes
Then you could update the subscription with an empty string for default_payment_method
raven siren
So in the past I have gotten errors for a resource_missing when the payment method is not set to default. I had assumed it was for the subscription but after talking with you I assume this is instead referring to the customer. So I think all in all that will work...just a lot more complicated than I wanted lol. Any chance on an ETA on when that might be added to the api and not dashboard only?
Okay