#drewbie__doobie
gloomy meadow
lapis ermine
Hello! Yes, it would.
harsh sun
Ok, and conversely if I am trying to update this standard account, and it gives me a permission error would that dictate any difference?
lapis ermine
Not sure I understand your question, can you provide more details?
harsh sun
Yeah, so I was trying to update the metadata for this connected standard account and I receive an You cannot perform this request as you do not have Platform Controls for Standard on the account. (Stripe::PermissionError). My issue is that I'm trying to test a process which is only triggered within production. This standard account is not seemingly dispatching these webhooks upon update. And I do not have permission to update it from my current scope.
This is all to kick off the account.updated webhook to update a few things within our application.
Testing flow.. etc
lapis ermine
Can you provide more specific details? For example, can you give me the request ID showing the error you mentioned? Can you also provide an example Event ID (evt_) showing the kind of Event you want to trigger? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
lapis ermine
Thanks!
That request is an attempt to update metadata on a Standard connected account, which failed for the reason stated in the error; you don't have permission to do that on this connected account.
harsh sun
Makes sense. But that wouldn't inhibit our ability to receive the account updated webhooks? I guess that's what I was asking on my second question way above.
lapis ermine
The Event you provided is pretty old, but it's an account.updated Event showing some capability changes.
As far as I can tell nothing would inhibit you from being able to receive account.updated Events. Can you give me the ID of a recent account.updated Event on a connected account that you expected to receive but didn't?
harsh sun
I don't have any. It was a theory I was wondering about. So, effectively since I don't have permission there's nothing I can do to kick off an account.updated webhook in it's current state?
lapis ermine
To clarify, why do you want to trigger an account.updated Event? What exactly are you trying to test?
harsh sun
We have some automated jobs that run upon a connected account having their charges enabled. We flip a few switches and statuses on our application. This is the only account currently stuck in a frozen state.
Those two old events have charges enabled but we didn't have these features. I am retroactively trying to test this particular account.
lapis ermine
You can test this in test mode with test connected accounts. If you want it to have it in live mode you need to make the actual changes to trigger the Event in question.
harsh sun
Ok, that's what I figured. I had already tested this in our test environment / test mode. Was hoping to kick this on production. But you have clarified and I will try and find an approach through the merchant if I can. Thank you for all your help.
lapis ermine
So this is to backfill?
If you only need the current state of the account you should be able to retrieve it from the API: https://stripe.com/docs/api/accounts/retrieve
That would give you basically the same info as the Event would.
harsh sun
Yes, I absolutely can do that but this process uses webhooks to automate. Which is my issue.
Seems I am stuck between a rock and a hard place 😁
lapis ermine
You probably need to make a one-off manual change, or add the ability to retrieve an Account's status from the API on demand and update based on it if needed (I recommend the latter).