#Rook2022-connect-saved-payment-methods
unique heron
Hi 👋 it is expected that the Platform is unable to use the payment methods that are saved to the Connected Accounts.
Are you going to need both the platform and the connected account to be able to access those payment methods, or just one of them?
dim shadow
Just the platform account as of right now. We have to have the platform account eat the fees and then invoice them
unique heron
Gotcha. If the platform is going to need to be able to charge the payment method, then it will need to be saved directly on the platform (and if it's going to be charged multiple times then it will also need to be attached to a Customer object on that platform).
dim shadow
Thank you so much toby, it's awesome how fast you are to help!
unique heron
If in the future you find that the Connected Accounts also need to charge that Payment Method, then you can look into leveraging this approach that allows you to copy Payment Methods from the Platform account to the Connected accounts.
https://stripe.com/docs/connect/cloning-customers-across-accounts
dim shadow
We looked at the copy option but that doesn't copy over bank saved payment methods
unique heron
Aahh
dim shadow
so we may have to stick with them staying at the platform level for this customer but future customers we hopefully wont have to eat the stripe fees
Is there a way to bulk delete saved customers thats at the platform level if our member leaves us? We wouldn't want to save the saved customers
could we put some identifier at the customer level to achieve this?
unique heron
There isn't a way to do bulk deletes from the API-side, but that functionality is available via the Stripe dashboard, but I'm not seeing a way to filter by a field like metadata there.
You can delete them individually via the API, and have a script that either iterates through all Customers looking for any that have some sort of indicator (metadata would be a good approach for that)
https://stripe.com/docs/api/customers/list
https://stripe.com/docs/api/metadata
Or you could look into leveraging our newer search functionality to only return customers that meet your criteria:
https://stripe.com/docs/api/customers/search
dim shadow
Excellent
One more question for you Toby.
We are allowing a customer to save their bank account outside of the payment form for autopay purposes. Currently the only way I see to do this is to use the stripe API with a custom form that we build. We then tokenize the bank information and attach it to a saved customer thats in stripe.
Is this the only way to achieve this for a saved payment method outside of a payment form? And second question, is the only verification method for this the 2 micro deposits?
gray gull
Hi @dim shadow 👋 taking over for Toby. Give me just a minute to get up to speed here
dim shadow
Absolutely!
gray gull
We are allowing a customer to save their bank account outside of the payment form for autopay purposes. Currently the only way I see to do this is to use the stripe API with a custom form that we build. We then tokenize the bank information and attach it to a saved customer thats in stripe.
Is this the only way to achieve this for a saved payment method outside of a payment form?
Autopay on bank accounts is definitely supported via the Payment Methods API, so you can save them for later without any issue. Not sure if that answers your question though.
And second question, is the only verification method for this the 2 micro deposits?
There's only one other option for bank verification that I know of. I'd start here: https://support.stripe.com/questions/instant-verification-of-ach-direct-debit-bank-information
dim shadow
I guess my question was about the method in which we are saving it.
we are saving it outside of a payment form because the user may not be paying an invoice but they want to setup autopay
so we built our own form and use the createToken for 'bank_account'
Think of our site like a utility payment site (like paying electric bill). You sign up and then go to save payment methods to setup autopay. This is done outside of a payment form.
https://www.youtube.com/watch?v=_1EX-DrikoA This video explains exactly how we are doing it
I just want to make sure that way is still the preferred method for custom forms
without doing it via a payment form
gray gull
So you're creating a single-use bank account token (via this: ), but you want to change it to be recurring? I would not recommend this approach. I would recommend integrating Payment Methods instead. Otherwise you will have to recreate the bank account token each time you want to charge the customer.
It's doable, but it's messy (hence why it's legacy)
dim shadow
No, it's not a single use. It's saving it to a customer's saved payment method
they verify it via the two micro-deposits
the token is created to safely transmit the bank account information to stripe
gray gull
What API are you calling to send the bank account information to Stripe?
dim shadow
Let me grab it real quick
notice the source
thats tokenized data
in that string
we call stripe.createToken('bank_account', and pass the data that was entered in our web form and in return we get a token
and then on our server side logic we call that API and pass the token to a customer as a saved payment method
and that's a saved payment method for a test user using test bank account info
gray gull
Ah, okay. Can you rephrase your question? I'm unsure of what you're asking, because your last question was "is this the only method for saving bank accounts?"
dim shadow
My question is, is this the correct way to save bank accounts to customers outside of payment forms. The YouTube video we watched says "Legacy" in the title as if there's a newer way but if there is i've not been able to find out how to do it and the docs don't say this method has been deprecated.