#doc_api
hallow harnessBOT
đ 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/1226901435329941665
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
red grottoBOT
slate sluice
Hello
The Bank Account object is our legacy object here
We recomend using the PaymentMethods API
However the Bank Accounts API is still supported if you really want to go that route. You would need to create your own form to collect the bank account details and then you would use https://docs.stripe.com/js/tokens/create_token?type=bank_account to create the object client-side.
There is no Stripe Element here that collects these details
gaunt lance
Ok, it would need to be a custom form. It's legacy but not deprecated?
slate sluice
Correct, legacy but still supported.
gaunt lance
Is it related at all to the Sources API? I only ask because the endpoint the 3rd party seems to be hitting in the request I listed point to them using that. "GET /v1/customers/cus_PjRdFwTESF7Aka/sources/"
slate sluice
Yeah when you attach a Bank Account object to a Customer you attach it as a Source: https://docs.stripe.com/api/customers/object#customer_object-sources
gaunt lance
The Sources api IS deprecated, is it not?
slate sluice
The Sources API itself is, yes. But you still attach a Bank Account object as a "source" on the Customer
Confusing I know
gaunt lance
Ah, it's just a property then, not a reference to a Sources obejct. My mistake. I think that answers my questions. Thank you for your time and swift replies.
slate sluice
Correct