#zombiewa
1 messages · Page 1 of 1 (latest)
Hi there
We tried and we can update the account holder name with the client name, but that may not match the account holder name on the ach account
Any idea how I can use these older already verified bank accounts for our connected stripe account payments?
So the issue is on clone, correct?
Can I see a request ID for the specific error?
I do think updating to include the client name is going to be the best path forward here
It's a test mode request
req_okN4AENVn1dfcx
Going forward we can collect the account holder name, but my concern is around pre-existing linked accounts
We have more than 6k bank accounts linked that we are using for auto payments as well
So having all those users come in and add a account holder name would not be feasible
Req_zotAkeXVsAoaKr is the correct one
Thanks
Hello! I'm taking over and catching up...
Thanks. Also at this point what I am trying to decide is if for these legacy use cases we should continue using the older charge API or if there is a workaround for us to be able to use the paymentintent API for this purpose as well
I've been researching a bit, and as far as I can tell you're going to need to provide the name for these bank accounts.
As far using Payment Intents, yes, you should be able to do that. You should be able to use existing legacy Bank Account objects as Payment Methods with the Payment Intents API. Let me see if we have a guide specific to this or not...
Well we can use them with payment intent but I guess not for the connect accounts due to the error?
We checked and in test morde atleast payment intent works fine for these older payment methods. It's only the connect case where it complains about not being able to link the payment method thereby preventing the payment to proceed
Yeah, that's where you're going to have to add the names.