#Santa-connect
dry horizon
hi! I don't think you can do that for Express accounts, you don't get that level of control. You can't stop them adding bank accounts
floral ferry
No but I can reject the account after the bank account gets added
Edited my message to clarify
dry horizon
interesting
you should get all the webhook events I would think. To be clear, do you use OAuth for Express, or create accounts with the API?
dry horizon
it is yes
then yeah as far as I know you should get all the events. I'd need a specific example to work with where you say you didn't get the event
floral ferry
Ok thanks
I found something else, should I make a new thread or continue here?
Also I would need to share screenshots with fingerprints, last 4 digits, and bank account stripe ID
Is that ok here or do you have a process for this?
dry horizon
well this is a public channel, if you need to share something sensitive you would speak to our support team at https://support.stripe.com/email
but things like acct_xxx account IDs or evt_xxx event IDs are not sensitive and you can share them here so I can look at specific examples if it helps!
floral ferry
Ok great thanks
I see different fingerprints for the same bank account added to a connect express account, do you have an explanation?
as seen in the connect express account VS in the webhook event payload
dry horizon
yes that's expected
floral ferry
notice how ids are the same but not fingerprints
dry horizon
when you as the platform view a fingerprint(by making an API call on their behalf, or getting a webhook event to your Connect endpoint), you see one version of it, and it will be same if you look at a different Stripe account's bank account with the same details so you can see duplicates across all your connected accounts
when just the connected account itself looks at the object, it sees a different fingerprint unique to it
floral ferry
Ok so when I receive the event it is as if I look as the connected account?
dry horizon
no it should be the platform version of it
floral ferry
Ok
Weird
because in the dashboard (first screen) I see it as the platform too
And I can search that fingerprint and find other accounts thanks to it
What I observe here is that I have a different/unique fingerprint in the event only
dry horizon
yeah the dashboard might do things weirdly/wrongly here, but I focus on the API
floral ferry
Ok let me try something
dry horizon
What I observe here is that I have a different/unique fingerprint in the event o...
yep, as I said
when you as the platform view a fingerprint(by making an API call on their behalf(https://stripe.com/docs/connect/authentication#stripe-account-header), or getting a webhook event to your Connect endpoint https://stripe.com/docs/connect/webhooks#connect-webhooks ), you see one version of it
it's quite possible the dashboard makes this confusing, I agree
floral ferry
Ok just tested to just stripe.Account.retrieve("acct_XXX") this one and got same fingerprint from the webhook event
stripe.Account.retrieve_external_account("acct_XXX", "ba_XXX") too
Sorry I don't understand where the dashboard fingerprint comes from then
and how am I able to find multiple connected accounts thanks to it (still on the dashboard)
If I could find a way to map those dashboard fingerprints to the api ones that would be best
dry horizon
yep as I said I suspect the dashboard does something wrong here or has a bug, I've heard similar feedback before
either way the API is the source of truth and it's what you'd use in your integration for actually identifying duplicates
but I agree the dashboard behaviour is confusing
floral ferry
Agreed, I will base myself on the API