#Bencel
1 messages · Page 1 of 1 (latest)
Hello
Yes that is fine
We don't de-duplicate bank accounts by default
So you can add it twice, or charge it twice. Mostly up to you
But we have this kind of error in our app.
Basically, we have two different emails, one has already used the bank accounts we wanted to reuse. And the other is a newly added user/customer, then it returns that error message if we're trying to save one of those bank accounts I'm referring to.
Is it okay to post this picture here? I'll delete it if not.
req_6OjZgxTKChvNtS
And also, those bank accounts were still in "Pending Verification" status although it were added more than one week ago.
Thanks, looking
Okay sorry for the delay
So yeah when I stated "we don't de-duplicate" I meant that we wouldn't prevent you from tokenizing the bank account multiple times and then adding it to multiple Customers
However, you wouldn't add the same bank account twice to the same Customer
Okay. Got it. But we have two different customers as I mentioned. That's why we're confused with that error.
Different emails were considered different Customers, right?
But you are attaching to the same Customer object, no?
You need to create two Customer objects in this case
Then you can attach the same bank account, tokenized twice, to two different Customers
So, what we're doing is we have a new user account in our app that is trying to save that bank accounts that were already used by another existing user account.
Basically, that is creating a new Customer object with that bank account, right?
But still, we get that error response.
I'm sorry I don't really understand what you are trying to do. Let's back up.
Right now the request that you provided attempted to attach a bank account to the Customer.
That Customer already has that same bank account attached, so you see the error stating that.
So why do you want to attach this same bank account to a Customer that already has that bank account attached?
So, that request ID I've sent is using the same Customer. Okay, let me confirm this with our user. Maybe he got confused with his accounts.
Sounds good
Okay, so confirmed. He used the same account. Thanks for checking it.
The remaining issue is that, why those bank accounts were still in pending verification status?
Have they completed microdeposit veirfication?
How does this process works? Automatically?
Nope, since you are using our legacy ACH flow, then the customer should see microdeposits in their bank account and you would verify the bank account using that. See: https://stripe.com/docs/ach-deprecated
Okay, let me check this guide. Thanks, @onyx comet! Really appreciate it. 😄