#peppemu-connect webhooks

1 messages Β· Page 1 of 1 (latest)

amber scaffold
#

this should be handled in a Connect webhook endpoint

charred flare
#

thank you @amber scaffold

#

I am gonna have a look

amber scaffold
#

just make sure to have this checkbox checked when creating your endpoint

charred flare
#

could you elaborate a bit what the event account.updated refers to

#

?

#

not sure if you saw the thread I had yesterday here, maybe it helps

amber scaffold
#

account.updated is the event that Occurs whenever an account status or property has changed.

#

your connected accounts

charred flare
#

I see

#

where can I check an example of how the event looks like

#

or of the different account statuses that exist ?

#

I had a quick look and it looks like the event only indicates that an edit was done to an account

#

I'd like to then see if the account has a status = enabled

#

is this doable ?

amber scaffold
#

you're right, there is no status field on the account object

#

but some other fields might indicate the status of the account

charred flare
#

all right, I'll have a look at this one too

vivid zenithBOT
#

This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact

serene mulch
#

πŸ‘‹

charred flare
#

hey ynnoj

#

thanks for getting back to me

#

so I have a few steps lined up on my side and I am stuck at an important one

#

I setup the webhook listening to the event account.updated

#

this webhook will trigger an automation which needs to know the account that triggered that webhook

#

in other cases I include the account at the end of the webhook url by simply adding: ?accountId= "account id here"

#

how can I do this when setting a webhook from the dashboard

#

?

serene mulch
#

There'll be an account field in the payload

charred flare
#

ah yea, I did this

#

I dont think this is enough for what I need

#

you mean that the webhook url when it's triggered will take with it an output array containing all data of the event ?

serene mulch
#

Can you share the webhook ID or an account.updated event ID?

charred flare
#

I can share the webhook ID

#

we_1KqbITDqkOoCRFDgdZMk9lP2

serene mulch
#

Yep, that's a Connect webhook. Is the account field not present in the Event payloads sent to it?

charred flare
#

how can I test that ?

#

I must make another webhook in the test mode, right ?

serene mulch
#

Yep! I'd recommend using the CLI to trigger test events

charred flare
#

let me have a look at that

#

thanks

charred flare
#

hey @serene mulch it seems like it is not happening

serene mulch
#

What's not happening? Can you share an example Event ID?

charred flare
#

I am expecting something to show up here: we_1KqboYDqkOoCRFDgnKEE3pYq

serene mulch
#

Can you share the ID of the connected account?

charred flare
#

acct_1KqcHyRe4yhjAOZP

serene mulch
#

There's a confusing matrix about how/where events are sent depending on how the account was connected to the platform:

For Connect webhooks, it’s important to note that while only test webhooks will be sent to your development webhook URLs, both live and test webhooks will be sent to your production webhook URLs. This is due to the fact that you can perform both live and test transactions under a production application. For this reason, we recommend you check the livemode value when receiving an event webhook to know what action, if any, should be taken.
https://stripe.com/docs/connect/webhooks

Learn how to use webhooks with Connect to be notified of Stripe activity.

#

Taking a look

#

And I can see a successful delivery to the webhook endpoint you shared: we_1KqboYDqkOoCRFDgnKEE3pYq

#

So what exactly do you mean by 'nothing shows up'?

charred flare
#

oh that's cool

#

I see it also on "the other side" where the webhook triggers an automation

#

and it indeed has an output including the account object

#

πŸ’―

serene mulch
#

So, it's working as you need?

charred flare
#

yea

#

thanks @serene mulch and @amber scaffold

#

πŸ™ƒ πŸ‘πŸ½

#

I am gonna do a couple of tests more before goin live

#

but the skeleton is there

pure hemlock
#

Unarchived. Let's chat here

#

@charred flare

charred flare
#

hey

#

thanks

#

I need some help understanding when an account has actually:
charges_enabled = true
and
payouts_enabled = true

#

so in my process, when testing and adding all info required by the onboarding link, the test account does not have charges_enabled = true nor payouts_enabled - true

#

I thought that it would have been the case πŸ₯Ά

pure hemlock
#

In the connect page of your dashboard, you can see what else is required. Can you check that?

charred flare
pure hemlock
#

If you hover over restricted, it should say what fields are required

#

What does it say?

charred flare
#

l

#

owners address

#

so without that info, payments and payouts are not enabled, right ?

#

could you confirm ?

pure hemlock
#

That's correct

charred flare
#

all right, cool πŸ‘πŸ½

#

thanks @pure hemlock