#max_account-update
verbal kernelBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1242502976241664132
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
pure goblet
Hi 👋 no, it is not possible to suppress the creation of Events.
You can look at the request field in the Event to see if it was generated from a request though:
https://docs.stripe.com/api/events/object#event_object-request
as opposed to one of our automatic processes.
My general suggestion would be to focus more on what changed on the Account, so you can prompt your user accordingly, rather than focusing on where the change came from.
If new requirements are surfaced, for instance, I don't think it matters too much whether they were added by us or your request.
neon vessel
Hello!
Thank you for the answer.
Well yeah but in our case we want to know if the EIN/SSN were changed and there is no 100% indication in the webhook that it was changed
pure goblet
Ah, yeah, that's fair, since that's a more sensitive field.
verbal kernelBOT
crystal patrol
max_account-update
@neon vessel there isn't a way to know if that specific information changed unfortunately, we don't surface anything to know that exactly. Maybe try looking at pending_verification and see if the EIN/SSN property is in there which indicates we are verifying it
neon vessel
Hello koopajah,
Yeah thats what I though doing, wondered if there is a better way.
so for SSN look at this?
pending_verification": [
"verification.document"
]
crystal patrol
it wouldn't be yeah that or verification.*.id_number (depends on which Person is associated with the account).
neon vessel
Hmmm, didn't see that on the webhooks only the verification.document
crystal patrol
it's possible that we verify against the document if you have already uploaded one. Sorry I don't know much about this behaviour
neon vessel
ah ok got it, it explains why yesterdsay I saw it and today I didn't.
So I will check for both of them. thank you!
crystal patrol
sure!