#theddev_error
sly scaffoldBOT
👋 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/1364337368865308682
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
quasi sorrel
Hi, it looks like these requests used 2 different API keys. It is possible that one of the accounts is added to a functionality that the other one does not have. Further looking
flat tulip
oh okay.
yeah, the first one is from a production account where the update failed and the second one is a sandbox where the update succedeed
sly scaffoldBOT
quasi sorrel
I'm getting a teammate to take a look here as well. Thank you for your patience.
flat tulip
sure thanks
quasi sorrel
It looks like, the Sandbox account is using pm_ object while the second request is using ba_ object.
So these are different objects, and it's expected that they might work differently.
flat tulip
oh okay. let me try something then
but when do we get setup intent's payment_method with ba_ and pm_
midnight cosmos
Hi hi! I’m going to be taking over for my colleague here.
I'm not sure what you mean by that last question?
flat tulip
hello timebox
okay so, pgskc said that the one that failed to update has payment method id starting with ba_ and the one which succedeed has payment method id starting with pm_
and that could be the cause of the issue. So I wanted to know when does the payment method start with ba_ and when does it start with pm_ for ACH
midnight cosmos
It's quite likely the ba_ one, which was created in 2022 (so is past retention of logs), was done via a different mechanism than what you're currently using to create them (which produces pm_ objects).
flat tulip
oh okay.
so the ba_ ones cant be updated now?
midnight cosmos
You'd have to use the right API endpoint, which is https://docs.stripe.com/api/customer_bank_accounts/update
But it looked like you tried to add expiry details in that failed request; what exactly was that request attempting to do?