#mursk_api
deft deltaBOT
👋 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/1241041233460068467
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
spiral blade
Hi there 👋 the approaches you described are the ones that came to mind for possibly working around this behavior. If those don't work, I may not have any other ideas. I'll look for a bit to see if I can find anything, but I think this is something I'll have to likely file as feedback to our teams for them to consider improving in the future.
gentle kiln
@spiral blade thank you!
Not sure if this is helpful, but worth mentioning in the Test environment I was also able to cancel a SetupIntent through the API and then verify it with a microdeposit in the dashboard, which I believe shouldn’t be possible.
It was Stripe Test Bank though.
spiral blade
I see what you're saying about the PM showing up in the dashboard but not being attached to the Customer according to the API. I'm not readily spotting a way to do anything about that, I'll be sure to file feedback with our teams for them to consider improving this experience.
Being able to verify microdeposits for a canceled intent does sound a bit unexpected, can you share the ID of the Setup Intent where you were able to do that? (seti_)
