#amirasol_api
sudden turretBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1344695546408992809
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- amirasol_docs, 6 days ago, 8 messages
vague cobalt
Hello there
No we won't block a saved card based on the expiry being expired.
Oftentimes issuers just translate that on their side to the newer card and everything is fine.
Yes sometimes the automatic card updater will run, but that is dependent on us getting the updated information from the issuer.
And sometimes the issuer will decline the card for it being expired.
In this case you should treat it like any other decline and reach out to your customer to collect a new payment method.
wispy plank
I see. If the automatic card updater runs, will the payment method with the expired card get "replaced" with a new payment method ID?
vague cobalt
No
A payment_method.automatically_updated will fire: https://docs.stripe.com/api/events/types#event_types-payment_method.automatically_updated
wispy plank
I see. So no need to handle any Stripe-side process that probably will generate a new payment method ID?
vague cobalt
Nope
We would never just change a PaymentMethod ID automatically
Really all object IDs don't change
They are immutable
A new object would be created if something like that were to happen, but that would not be the case here.
wispy plank
I see. Since I'm dealing with subscriptions, I know the payment method has to be attached to the customer in order for it to be reusable. If or when the card updater runs, will:
- the old payment method (with expired card) get detached from the customer?
- the new payment method get attached automatically to the customer?