#beadle_docs
eternal mulchBOT
👋 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/1441181179087687691
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
delicate ingot
Hi there 👋 I'm not sure offhand what email you're referring to, are you able to share the full email?
eternal mulchBOT
static plume
Hi there! I'll be taking over for toby, who needed to step away
I think the doc you need is this one:
spice ridge
Ok, let me take a look
static plume
I can elaborate a bit if it is helpful?
Likely you have Customers with a legacy bank account set as a default_source
spice ridge
Yes. What is the most efficient way to find and update these bank accounts? Should we be able to do it from the API?
Also, in that link you sent there are different requirements for checkout session vs payment intents api. If we exclusivle use checkout sessions does that mean we dont' need an active mandate?
static plume
Yeah I think the difference is Checkout won't display legacy ACH accounts at all and the user can add their bank account as the newer ACH implementation if they wish
since they're always going to be there in the checkout flow, whereas many users that are on the PaymentIntents API are processing off-session payments
spice ridge
That is my hope as well. However, what about a legacy customer who is on a subscription with an ach debit payment method that doesn't have a proper mandate. Will those subscription payments stop working come May 6th?
static plume
If you want to find existing Customers that have a legacy ACH account attached, you'd need to List Customers via the api and then iterate over the list looking at default_source
Then you can create a list of Customers and List Subscriptions for those Customers
Yes, you need to act on Subscriptions that are using a legacy ACH bank account. here is the section where we cover that: https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges?integration-path=checkout#subscriptions
spice ridge
That all is simple enough. I guess my question is, how do I know when the default source needs to be updated? What do I look for that tells me this source here is no good anymore?
static plume
default_source is for legacy objects like Bank Accounts & Sources. The modern version is a Payment Method with type: 'us_bank_account and would be set on the Customer as invoice_settings.default_payment_method
see also this section in the migration guide that explains how the Bank Account can be retrieved as a Payment Method via the Payment Methods API
spice ridge
Ah, ok. That is helpful. Thank you so much!
I hope you have a great rest of your shift. Thank you for your time!
static plume
You're very welcome!