We’re using Mx to do IAV and do the token exchange to add verified payment sources.
We can add one bank just fine. But then I try to add another account from the same bank, and I get the following error:
“code”: “DuplicateResource”,
Jul 25 00:18:31 ip-172-31-50-206 web: “message”: “Bank already exists: id=8e926891-4768-457c-8191-c702f5b96f42”,
Yes, the bank already exists, I’m trying to add a different account from the same bank.
Hi @lucio,
Looks like this bank was added on 8/29/2023 10:27 AM CT. Perhaps, it’s the same bank you are attempting to add again? I DM’d you a masked Routing Number to help determine if it’s the one.
Yes, its the same bank. The user was using Mx IAV to add another account from the same bank. Surely we can add multiple accounts from the same bank? Each account is a different payment source.
Yes, the user should be able to add multiple accounts from the same bank! The error suggests that the same account within the bank was attempted to be added again. Would you be able to confirm in the direct message I sent you?
I confirmed the private message this morning. Did you get it?
Hi Lucio! I did. I have followed up with another message confirming the last two digits of the bank account number as well. Here are the other contents of that message:
I wonder if the issue lies somewhere else. Our duplicate bank logic goes off of the fingerprint that is generated for each Account/Routing number combination.
Is this the first time this issue is occurring in a scenario like this where you add multiple bank accounts from the same institution? Would you be able to confirm that the right “account_id” is being passed in the code for generating a processor token (referred to as an authorization code in MX docs)?
Thank you! This will help us narrow down the issue!
Looking into the MX token generation code today.
Sounds good. Let us know what you find!