rnash - stripe listen connect events | Stripe Developers | Page 1

lyric raptorBOT Nov 15, 2022, 11:35 PM

#

proven hearth Nov 15, 2022, 11:35 PM

#

Can you describe the problem in a little more detail?

queen slate Nov 15, 2022, 11:35 PM

#

I am trying to wire up a webhook for events occurring for my connect accounts

#

to test them locally, I am using stripe listen --forward-connect-to https://localhost...

#

then I'm triggering an event with the CLI using stripe trigger --stripe-account acct_####### <event-name>

#

and nothing is firing

#

I see no event in the CLI log

#

and my breakpoints in my code don't get hit

#

but if I take out the connect params

#

and use stripe listen --forward-to https://localhost/...

#

and stripe trigger <event-name>

#

it works as expected

proven hearth Nov 15, 2022, 11:39 PM

#

stripe listen will forward connect webhooks to the same URL by default. What happens if you use the --stripe-account parameter when calling stripe trigger alone?

queen slate Nov 15, 2022, 11:39 PM

#

alone?

#

what do you mean?

proven hearth Nov 15, 2022, 11:40 PM

#

Just use stripe listen --forward-to but include the --stripe-account parameter when calling stripe trigger

queen slate Nov 15, 2022, 11:40 PM

#

ah

#

ok one second

#

it doesn't call the webhook

#

and no event shows up in the log in the CLI

#

stripe trigger --stripe-account acct_######## payment_intent.created

#

..is the trigger I'm trying

proven hearth Nov 15, 2022, 11:43 PM

#

And the connect account belongs to you?

queen slate Nov 15, 2022, 11:44 PM

#

yes

#

I've double checked that several times

proven hearth Nov 15, 2022, 11:46 PM

#

And when you run the stripe trigger command, do you see the following output?

Setting up fixture for: payment_intent
Running fixture for: payment_intent
Trigger succeeded! Check dashboard for event details.

queen slate Nov 15, 2022, 11:47 PM

#

yes

#

Setting up fixture for: payment_intent
Running fixture for: payment_intent
Trigger succeeded! Check dashboard for event details.

#

if I log into my connect account's dashboard (via the connect tab) I see the payment intent there

#

this is a real problem for us as we need to track when things like payouts happen and this was our path forward with that

#

are you still there?

proven hearth Nov 15, 2022, 11:56 PM

#

Hi , yes there are multiple people asking questions. Sorry for the delay

queen slate Nov 15, 2022, 11:56 PM

#

no problem

proven hearth Nov 15, 2022, 11:56 PM

#

And you don't see

 --> connect payment_intent.created

In your stripe listen log

queen slate Nov 15, 2022, 11:56 PM

#

no

proven hearth Nov 15, 2022, 11:58 PM

#

and what happens if you run stripe login?

queen slate Nov 15, 2022, 11:58 PM

#

it opens a browser window

#

I select the platform account I'm interested in and then click allow access

proven hearth Nov 16, 2022, 12:04 AM

#

Okay and then you still aren't seeing any Connect events? Can you tell me which version of the CLI you are using?

queen slate Nov 16, 2022, 12:05 AM

#

no

#

1.7.9

proven hearth Nov 16, 2022, 12:08 AM

#

A fix for forwarding Connect events was pushed out on version 1.7.13. I think. you should try upgrading your CLI version: https://github.com/stripe/stripe-cli/releases/tag/v1.7.13

queen slate Nov 16, 2022, 12:08 AM

#

ok

#

on it

#

thanks

#

I'll have to reach back out tomorrow if that doesnt work

#

thanks

#

well...

#

I went ahead and tried

#

and that didn't work

#

i upgraded via brew

#

so it went from 1.7.9 -> 1.13.4

#

but it's unfortunately still not working

proven hearth Nov 16, 2022, 12:29 AM

#

So now are you using stripe listen --forward-connect-to or just stripe listen?

proven hearth Nov 16, 2022, 12:54 AM

#

rnash - stripe listen connect events

queen slate Nov 16, 2022, 1:15 AM

#

i tried both

velvet plover Nov 16, 2022, 1:16 AM

#

👋 Taking over this thread, catching up now

queen slate Nov 16, 2022, 1:22 AM

#

hi

velvet plover Nov 16, 2022, 1:23 AM

#

Which combinations of commands did you try that didn't work?

queen slate Nov 16, 2022, 1:23 AM

#

all of them

#

one sec and i'll be specific

#

stripe listen --forward-connect-to https://localhost/webhooks

#

and then

#

stripe trigger --stripe-account acct_##### payment_intent.created

#

also:
stripe listen --forward-to https://localhost:

#

along with:
stripe trigger --stripe-account act_###### payment_intent.created

#

i get a payment intent created

#

i see:
Setting up fixture for: payment_intent
Running fixture for: payment_intent
Trigger succeeded! Check dashboard for event details.

#

and when I look into the dashboard, it's there

#

but I don't have anything in the CLI log

#

and my code does not get hit

velvet plover Nov 16, 2022, 1:35 AM

#

When you use below set, does your CLI show webhook event logs without using connect?

stripe listen --forward-to https://localhost...
stripe trigger payment_intent.created

#

For example, seeing something like this:

2022-11-16 09:39:29   --> payment_intent.created [evt_xxx]
2022-11-16 09:39:29  <--  [200] POST http://localhost:3000/webhook [evt_xxx]

queen slate Nov 16, 2022, 2:06 AM

#

yes

#

sorry for the delat

#

delay*

velvet plover Nov 16, 2022, 2:17 AM

#

If you use following set:

stripe listen --forward-to https://localhost/...
stripe trigger -stripe-account acct_xxx payment_intent.created

Do you see this?

2022-11-16 09:39:29   --> payment_intent.created [evt_xxx]
2022-11-16 09:39:29  <--  [200] POST http://localhost:3000/webhook [evt_xxx]

queen slate Nov 16, 2022, 2:29 AM

#

no

velvet plover Nov 16, 2022, 2:32 AM

#

I tried on my CLI with v1.13.0, it's working fine. Can you share your connected account ID (acct_xxx)?

#rnash - stripe listen connect events