#Att89-connect-webhook-cli

1 messages · Page 1 of 1 (latest)

crisp cobalt
#

Hey! can you share a Stripe account ID?

#

Preferably of the platform

#

Att89-connect-webhook-cli

uneven crystal
#

Hi there, yes, the stripe account ID of the platform is: acct_1JNcllFHLvSMgLRW

crisp cobalt
#

Taking a look!

#

Sorry, and the ID of the connected account?

uneven crystal
crisp cobalt
#

Got it, thanks

#

Do you have an event ID that isn't being forwarded as you expect?

#

And are you authorised in the CLI as the platform account?

uneven crystal
crisp cobalt
#

Right, but there'll still be events created on the Stripe account

#

Let me check

#

Ah, I think the --stripe-account flag needs a =

#

So --stripe-account=acct_xxx

uneven crystal
#

I can see the payment_intent.succeeded event even if it is for a specific connect-account. I thought i should catch this event over the connect-webhook, because the payment intent was created for a connect account.

crisp cobalt
#

But it isn't being created on the connected account (check the logs of the account and you'll see)

uneven crystal
#

Yes, i see. I think i misunderstood this point. The payment intent is created for the connect account (with the account_id in the request options), but it is created on the platform account, so events for it won't be triggered on the connect webhook. Am i right?

crisp cobalt
#

Exactly. Without that --stripe-account= flag you're trigger the event (and associated objects) on the account you're authenticated with in the CLI (the platform)

#

So they won't be triggered on the connect webhook, but your regular webhook on the paltform

uneven crystal
#

I understand! Many thanks for your quick help!