#avjamethyst_api
vestal jasperBOT
👋 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/1501661986017247243
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
wraith swallow
Hey there -- I'm not sure why the Dashboard tool isn't loading for you, but no it is not necessary to re-collect bank account information
See the guidance here: https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges
At the core, you really need to do 2 things for the existing bank accounts:
1/ Establish a mandate for the recurring payments on the bank account: https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges?integration-path=payment-intent#mandate-acknowledgement
If you already have consent from your customer for this you can pass the details about that via the API to set up the mandate immediately
2/ Set the bank account as the customer invoice_settings[default_payment_method] or subscription default_payment_method
https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges?integration-path=payment-intent#subscriptions
atomic maple
The doc says this: If you previously collected customer payment details with Stripe using the Tokens API, you can continue using the saved BankAccount as a PaymentMethod.
Does that mean we don't actually have to do anything?
wraith swallow
It means they are usable, but you still need to set up the mandate
atomic maple
so if they're already the default, is it just the mandate then?
wraith swallow
Can you share an example customer ID (cus_123) i can look at?
I suspect these might be using the legacy default_source and you'll have to update the customer to set invoice_settings[default_payment_method]
wraith swallow
Ok, yes, its as i thought
Currently that customer is using default_source
You need to use the SetupIntent API like in the example you create a mandate and then set the customer invoice_settings[default_payment_method] with the bank account
atomic maple
we've got customers using cards through default_source, do those need to be updated too?
vestal jasperBOT
brazen pier
Hi there
sorry for the delay here
Yes, you can re-use the card objects that are set as default_source and copy it to invoice_settings.default_payment_method
atomic maple
That wasn't exactly the question. So it was stated that we need to copy default_source down to the invoice settings for these bank accounts that we have to add mandates for. Do we have to do the same thing for cards that we're not converting in any way, or can it just continue to use default_source like it does now?
brazen pier
How exactly are you charging these customers? If it's through Subscriptions/Invoices, then the answer is yes.
If you're charging them through PaymentIntents API then you don't need to unset the default_source but would need to pass the card ID to payment_method parameter
atomic maple
this is just for subscription invoices
it's been using default_source forever, we just got the notification about ach being retired, so we were only going to move bank accounts over
brazen pier
IMO if I was in your shoes, I'd move off of the old/legacy parameter in one go rather than one payment method type at a time
Like having card stay as default_source won't break your integration but it wouldn't add any value either.
atomic maple
are there plans to retire default_source? if so, what's the timeline for that?
brazen pier
At the moment, there are no such plans.
atomic maple
so for both cards and bank accounts, if we leave it as default_source it will work just fine?
brazen pier
when you say "work", are you referring to Subscriptions being able to charge them as sources? If so, no
atomic maple
when will that stop working?
brazen pier
Support for bank accounts (ACH) would end on May 15th as per the email
For cards, it should still continue to work as far as I know given the objects are backwards compatible.
atomic maple
right, so we need to add mandates for bank accounts and that should make them valid again, right? Then the move from default_source seems like a separate thing that either we have to do for every type of payment with it's own timeline, or not at all and it'll continue to charge everyone as is?
brazen pier
When you collect a mandate, it should create a new Payment Method object (pm_xxx). You can't set that as default_source .
You can either set it directly on the Subscription's default_payment_method parameter or set it under customer.invoice_settings.default_payment_method.
When you set the payment method as default, that tells Stripe to charge that payment method for the sub
vestal jasperBOT
atomic maple
ok, so that makes sense for the bank accounts. For the pros with cards that we're not touching though, will their subscriptions continue to charge if we don't move their default from "default_source"? Some definitely have old "card_" style sources
sorry about the weird discord formatting
last sphinx
taking over for hanzo, gimme just a bit to catch up on context
and no worries 🙂
do you have an example subscription?
based on how you're describing it i think it should be fine but it would be nice to double check
last sphinx
ok confirmed that this for now yes
atomic maple
that's a little concerning, how long is for now?
last sphinx
gooooood question, i don't think we have a deprecation planned for it yet
and it's technically possible that we might do it eventually, so i would say it might be easier if you just include migrating card_*** + default_source while you're in the process of migrating ACH + default source
atomic maple
do the cards need a migration to pm like the bank accounts?
last sphinx
cards are backwards compatible in default_payment_method and i'm not aware of plans to change that
atomic maple
ok, I think that covers everything I need then