#hilljh82
1 messages ยท Page 1 of 1 (latest)
Good question. Checking in to this. It is possible that in test mode we are replacing some data on the object behind the scenes and that is what is changing the fingerprint
Since i'm running in developer mode, I am more than happy to attach to fingerprints that I am receiving.
This is making it hard for me to implement some features.
Do you have the Stripe ID of these accounts (ba_12345)?
Let's me run a quick test and post the ba_1 values.
Here is what I am getting in development mode:
From the token:
btok_1Mb3RfIfWWmj7EziyMyg5LBh => ba_1Mb3RfIfWWmj7EziqxiWjld1 => kQmlIiWauZ0DsbQR
From the external account:
ba_1Mb3T6RIrMmNOLahIi74ebLY => mE2v5IWVkTcP31te
Yea, for some reason its switching the ba_ value.
Thank you for the IDs, will check in to them and get back to you with what I can find
Hey apologies, still having trouble finding info on this. Will ask colleagues and get back to you on what we can find.
So unfortunately it looks like bank account fingerprints are still unique across accounts. There is work on the roadmap to make these fingerprints consistent across a connected account and its platforms but unfortunately that is not the case yet
Thank you for looking into this. So, just to make sure I understand this, I can't use the fingerprint from a btok to check for uniqueness at this moment because it will not be for the same ba_ that is associated with the external account?
But, I could use the fingerprint from bank account retrieved using the btok for the time being. I just have to remember that the ba_ from the btok will not be the same ba_ from the external account.
Question: can I use the routing # and last 4 to determine uniqueness for the time being since the fingerprint functionality that i'm looking for does not exist?
just trying to see if I can use the routing # and last 4 of an account # to check for uniqueness of accounts across an entire platform for custom accounts
since the ba_ are different from the btok vs when set as the default external account for a custom account.
You could use the combination as a primitive factor but don't think it would be as reliable as a fingerprint. However, I also understand that it isn't an option at the moment.
Ok, that's what i was thinking.
Is this something that is part of the development road map? I would think so since you mention using the fingerprint to check for uniqueness in your docs.
It is but we don't have a timeline for this yet.
Ok, thanks for your time.
NP! ๐ Apologies for the delay again.
Good luck
Oh... 1 more question.
There is no way to get original btok_ used to set the default external account is there?
Just thinking of migration issues for existing custom accounts.
No, there isn't.
However, you might be able to set it as metadata if you need to reference it later
https://stripe.com/docs/api/external_account_bank_accounts/create#account_create_bank_account-metadata