#alexander-1966_api
inland canyonBOT
👋 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/1216767452386562079
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
dusk cave
Hi there 👋 I'm taking a closer look at the flow there to see if those Payment Methods are salvageable.
placid berry
I asked Stripe Support the same question and they told me
Within Stripe, there isn't a workaround that's why we don't have a guide we can provide you aside from the 2 documentations I sent earlier. But there are developers who can do complex codes from their backend using their own logic that overrides Stripe's process.
the goal is to (try to) re-verify the card from the backend (without any user session whatsoever)
dusk cave
In this case, that doesn't seem to be possible. The Payment Method that was created appears to not have been attached to the Customer, likely because the setup failed, and it was consumed so it cannot be reused. You would need to allow your customers to provide new payment method details, or at least direct them back to your form where they can provide those same details again.
placid berry
got it. Thanks for confirming.
dusk cave
👍 any time!
placid berry
have a great day