mjallday
commented
9 years ago It could be the same bank account (e.g. account and routing numbers) attached to another customer. This is a fraud prevention measure since you could otherwise create a million bank accounts verifications and send the account a non-trivial amount of money.
If that's not the case (and it sounds like you do not think it is from reading your question) then give us the fingerprint or ID of the bank account in question and we'll have a look at it.
I'm not sure how to describe the mapping to you, but if you can re-word that question we'll be happy to answer.
etipton
remear
We are occasionally getting unexpected errors of "There is already a verification pending for this bank account" despite not initiating a prior verification for this BankAccount from our system (or even a BankAccount with the same account number).
How does this system work? Is there any documentation on how exactly a "conflict" (aka a matching real-world bank account has already had verification amounts sent) is determined for the verification process?
In one case, even though we got a failure, the user did receive microdeposits with the description "RenterUp" (my company). But that was useless because there was no BankAccountVerification object in your system to try to confirm the amounts against (because the API call failed).
I'm happy to share specific details, but first thing's first... are you able to shed some light on how Balanced BankAccount objects are mapped to real-world bank accounts behind-the-scenes?
Thanks!
Eric