#hendie_webhooks
finite ermineBOT
👋 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/1234901597478326313
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
quasi latch
Have you checked the requirements hash on that Account object to see what might be causing payouts to be disabled?
Err, actually, it looks like the event you posted was sent via webhook with a payload that includes "payouts_enabled": true,
desert aspen
hmm, we'll check again
quasi latch
It's likely that your webhook handler is just looking for it in the wrong place, so I'd recommend logging the full contents of the payload and manually checking to make sure your handler knows where to get it
desert aspen
could be, but I was pretty sure we didn't find it, lemme check again
your new workbench is giving me headaches, I can't seem to find that event in it
this is what we got:
we found charges_enabled, but not payouts_enabled
quasi latch
Ahhhhh, I think it's because your API version is ancient. Let me check the changelog real quick and see if I can confirm
Are you only using workbench? Or are you also able to create an API request on your own?
desert aspen
well, the webhook is on v 2020-08-27
should that not determine what content events have?
we got that event on a local machine using stripe cli
and feeding into our app (also runnig locally) which recorded what it received
or does the stripe cli webhook conform to our platform version unless specified?
ok, I see the default for stripe listen is our api version, using -l would probably solve it
quasi latch
I think the CLI conforms to the default on the account unless you pass the version either globally (https://docs.stripe.com/cli/flags#flags-version) or when you create the listener you can pass -l for latest API version (https://docs.stripe.com/cli/listen#listen-latest)
Ah! Yup, beat me to it
quasi latch
It does come in handy to have access to the latest. That's for sure
finite ermineBOT
desert aspen
one more question related to connect: is it sufficient to look at charges_enable: true && payouts_enabled: true to determine if a connected account is fully operational?
limpid ledge
Hello! I'm taking over and catching up...
desert aspen
sure
limpid ledge
That's sufficient in many cases, yes, but it depends on what you mean by "fully operational".
Both charges_enabled and payouts_enabled may be true, but that doesn't mean every capability on the account is active, for example: https://docs.stripe.com/api/accounts/object#account_object-capabilities
If your definition of "fully operational" includes, say, the us_bank_account_ach_payments capability, then you would also want to check for that as well, as an example.
desert aspen
ah, gotcha, so traverse the capabilities list and check that all are active?