#brie_api
slim trenchBOT
đ 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/1346951424277479556
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
obsidian hedge
Hello there
south helm
Hello
obsidian hedge
The PaymentIntents/SetupIntents API are actually backwards compatible here and can use these Bank Account Tokens, see: https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges
south helm
Using the btok_ prefixed tokens?
Looking here https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges#retrieving-a-bankaccount-as-a-paymentmethod it seems like it is expecting a ba_ prefix
I just want to confirm this
obsidian hedge
Yeah you still attach that to a Customer via the source parameter and then you can use this with PaymentIntents. This parameter isn't being deprecated.
Only Source objects themselves are being deprecated.
south helm
So customer.getSources.create(PaymentSourceCollectionCreateParams.builder().setSource(sourceToken).build()) should continue to work?
obsidian hedge
Yes, assuming that sourceToken is the Bank Token?
south helm
Correct
obsidian hedge
Then yeah, that will continue to be supported.
obsidian hedge
Yep
The Source object (https://docs.stripe.com/api/sources/object) is what is being deprecated
But you aren't using that here.