#akzent_subscription-invoice
burnt hemlockBOT
👋 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/1263538655260053565
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
placid spire
Also note that we're using stripe test clocks to fast forward our annual test subscriptions +1 year
outer crest
@placid spire unfortunately this is a bad corner case of the API that we haven't been able to fix yet I'm sorry. I think you need to update the PaymentIntent before you use it in that flow
placid spire
ah, specifically the renewal invoices being generated without setup_future_usage set?
outer crest
yes 😦
it's such a bad pit of failure and I've raised it a few times internally but it is a really hard one to fix unfortunately
akzent_subscription-invoice
placid spire
oooof, it happens, thanks for the context! luckily we have some time before the customer will try to pay the failed renewal invoice.
outer crest
yeah the problem is that once you set setup_future_usage you lose the ability to accept certain payment methods which some people prefer after one failed payment.
But if the customer pays with a new card that one you want to save.
placid spire
ok so if we're just using cards right now it's no problem, but when we start allowing other payment methods the customers will be faced with the ability to only pay failed invoice with card
after i make the change to update PI with setup_future_usage: off session
placid spire
thank you!