dishant_cli-connect-events | Stripe Developers | Page 1

zinc iceBOT Sep 9, 2024, 11:55 AM

#

👋 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/1282670648984076483

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

outer quail Sep 9, 2024, 11:55 AM

#

Hi

daring berry Sep 9, 2024, 11:56 AM

#

hi! can you say more? what exact command are you running, what sort of events are you expecting?

outer quail Sep 9, 2024, 11:57 AM

#

In cmd I am using stripe listen --forard-to 'locally created enpoint url'
I am expecting

charge.succeeded
charge.updated
charge.failed
payment_intent.succeeded, etc..
Whatever event stripe is throwing to the webhook end point.
Later using code I will filter the events

daring berry Sep 9, 2024, 11:59 AM

#

do you have an example of a ch_xxx Charge ID that you expect to be seeing? How do you create the test events?

outer quail Sep 9, 2024, 12:00 PM

#

I place the payment to stripe and using separate project which is listening to webhook events I am testing the events

daring berry Sep 9, 2024, 12:01 PM

#

maybe your "separate project" is using the API keys of a different Stripe account than the one stripe-cli is using?

outer quail Sep 9, 2024, 12:01 PM

#

pi_3Px65TBYB6ebuc8B1l80aIcc
this is the payment which I placed just 5 min ago

daring berry Sep 9, 2024, 12:02 PM

#

ah this is a Connect payment, right? you're using Connect with Direct Charges?

outer quail Sep 9, 2024, 12:02 PM

#

Yes

#

Earlier this is working fine in local host

#

but now it is only throwing application_fee.created event

daring berry Sep 9, 2024, 12:03 PM

#

you need to use --forward-connect-to <url>
https://docs.stripe.com/cli/listen#listen-forward-connect-to
https://docs.stripe.com/connect/webhooks#:~:text=Note-,For Connect webhooks,-%2C use –forward-connect

outer quail Sep 9, 2024, 12:04 PM

#

ohhkk
When this update came?

daring berry Sep 9, 2024, 12:06 PM

#

not sure what you mean, there's no update or anything new here

outer quail Sep 9, 2024, 12:07 PM

#

this --forward-connect-to is not working for me, I think because my webhook end point is created into platform account

#

--forward-to should be working as earlier

daring berry Sep 9, 2024, 12:09 PM

#

the way you do this normally is you use stripe login to connect stripe-cli to your platform account, and then you can use --forward-connect-to to listen to events that happen on your connected accounts(like events relating to payments processed as Direct Charges)

outer quail Sep 9, 2024, 12:11 PM

#

but that --forward-connect-to is actually not working for me

#

I used** stripe login --api-key 'key'**
then** stripe listen --forward-to 'endpoint url'**

#

Is that okay?

daring berry Sep 9, 2024, 12:15 PM

#

when you say "not working" what does that mean?

outer quail Sep 9, 2024, 12:16 PM

#

It means it is not calling my webhook endpoint which was working with --forward-to

#

As I told you I created one separated azure function code which is handling my webhook events

daring berry Sep 9, 2024, 12:20 PM

#

I mean it really depends what "key" is , is it your platform key, the key of a connected account , something else...

#

I told you the supported/recommended way of doing this : you use stripe login to connect stripe-cli to your platform account, and then you can use --forward-connect-to to listen to events that happen on your connected accounts(like events relating to payments processed as Direct Charges)

outer quail Sep 9, 2024, 12:26 PM

#

this way also I am getting only one event same as earlier

#

What could be the cause of this only one event trigger when payment made to stripe?

daring berry Sep 9, 2024, 12:29 PM

#

if you're only getting application_fee.created it's because you're running on the platform account and only listening to events that happen on the platform account(--forward-to), which is why you need to listen to Connect events via --forward-connect-to

outer quail Sep 9, 2024, 12:37 PM

#

It is actually listening to connect

#

Is that correct?

daring berry Sep 9, 2024, 12:39 PM

#

not sure, I've never created a restricted key this way to use with stripe-cli. Can't you just use stripe login , copy the link, open the link in your browser where you're logged into your platform account, and accept? I'd recommend that.

outer quail Sep 9, 2024, 12:39 PM

#

I did the same
And that created this key

#

I used stripe login
the authorized from the link then did the stripe listen

daring berry Sep 9, 2024, 12:41 PM

#

cool

#

so now if you run stripe listen --forward-connect-to=<url> , leave that Terminal window open; then go do some test payments on a connected account, what happens?

#

also if you do stripe config --list what is the value of account_id

zinc iceBOT Sep 9, 2024, 12:44 PM

#

dishant_cli-connect-events

outer quail Sep 9, 2024, 12:47 PM

#

the platform's account id I am getting

daring berry Sep 9, 2024, 12:47 PM

#

and what ID acct_xxx is that exactly?

outer quail Sep 9, 2024, 12:49 PM

#

acct_19WmAUFe0vn1lMmX

daring berry Sep 9, 2024, 12:50 PM

#

sounds good. So now if you run stripe listen --forward-connect-to=<url> , leave that Terminal window open; then go do some test payments on a connected account, what happens?

#

and share the ID pi_xxx of the test payment you create

outer quail Sep 9, 2024, 12:51 PM

#

I tried and it is not hitting the separate code I created to listen webhook events which is azure function code

wintry ridge Sep 9, 2024, 12:51 PM

#

Hi there 👋 jumping in as my teammate needs to step away soon. Can you elaborate on what that means? Do you see the additional events being received in the CLI's output, and they just aren't being sent where you're hoping they will be?

outer quail Sep 9, 2024, 12:53 PM

#

Hi @wintry ridge

#

So the issue is I am running CLI in local machine and it is only hitting for application_fee.created event

#

no other events like charge.succeeded, charge.updated, etc..
which is working fine earlier with the same code which I have right now

wintry ridge Sep 9, 2024, 12:55 PM

#

To break this down a bit more, Events that are important for a Platform appear in one of two places. Either directly on the Platform account, or they are generated on a related Connected Account.

forward-to only forwards events for your account (the platform) you have to also use forward-connect-to in order to forward the Events from your Connected Accounts as well.
https://docs.stripe.com/cli/listen#listen-forward-connect-to

Stripe CLI Reference

outer quail Sep 9, 2024, 12:55 PM

#

I only got this

wintry ridge Sep 9, 2024, 12:55 PM

#

What is the exact command you're using to start stripe listen?

#

That's because you aren't using forward-connect-to as well as forward-to

outer quail Sep 9, 2024, 12:56 PM

#

When I use the forward-connect-to
it is actully not hitting my local host endpoint

wintry ridge Sep 9, 2024, 12:57 PM

#

Can you show me that? Run stripe listen --forward-to [your_endpoint] --forward-connect-to [your_endpoint] and then make a test payment

outer quail Sep 9, 2024, 12:59 PM

#

Sure above screen shot is with --forward-to [endpoint]

#

here is with -connect

#

and as you can see it does not have the [200] ok result because it does not hit the endpoint which I created

wintry ridge Sep 9, 2024, 1:02 PM

#

Can you try again with both options as I suggested above? Can you also share the ID of the Payment Intent when you try that

outer quail Sep 9, 2024, 1:03 PM

#

pi_3Px6vKBYB6ebuc8B1sKzagE8
with --forward-to

pi_3Px7BDBYB6ebuc8B1yIkRbJv
with --forward-connect-to

wintry ridge Sep 9, 2024, 1:04 PM

#

I don't understand why you're pairing them with only one option. Are you running stripe listen with both forward-to and forward-connect-to options?

outer quail Sep 9, 2024, 1:05 PM

#

Yes

#

Am I doing something wrong here?

#

If yes then what is the correct way pls tell me

wintry ridge Sep 9, 2024, 1:06 PM

#

So far all of the screenshots you've shared show you only using one option (only forward-to or only forward-connect-to) when running stripe listen. You should use both of them simultaneously. Like this:
stripe listen --forward-to [your_endpoint] --forward-connect-to [your_endpoint]

outer quail Sep 9, 2024, 1:07 PM

#

With that also I am getting only one event in my code

wintry ridge Sep 9, 2024, 1:08 PM

#

Now I need the Payment Intent ID from that test ^

outer quail Sep 9, 2024, 1:08 PM

#

pi_3Px7IzBYB6ebuc8B0o1OBXqw

wintry ridge Sep 9, 2024, 1:10 PM

#

Thank you, let me take a look there.

outer quail Sep 9, 2024, 1:11 PM

#

yes please

wintry ridge Sep 9, 2024, 1:16 PM

#

And triple checking, you ran listen before making the confirmation request?

outer quail Sep 9, 2024, 1:18 PM

#

I didn't get it

#

can you tell me what should I do to resolve this?

wintry ridge Sep 9, 2024, 1:20 PM

#

I'm asking you more questions about what you're doing so I can try to spot what is going on. Part of your flow is to confirm a Payment Intent, like you did in this request:
https://dashboard.stripe.com/test/logs/req_u54YWRKZ46VpOw
I'm making sure that you had run stripe listen in your terminal before you made that confirmation request?

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

daring berry Sep 9, 2024, 1:21 PM

#

it's because the account is only connected in live mode, not test, so test mode events don't get delivered. We'd recommend testing with fully test-mode accounts, not making test mode requests on live accounts.

#

you can technically also connect the account in test mode as well (by doing https://docs.stripe.com/connect/oauth-standard-accounts using your test mode ca_xxx client ID) but it's quite tricky and you'd need the owner of the connected account to agree.
It's easier to just use a regular test account you create.

wintry ridge Sep 9, 2024, 1:22 PM

#

Great spot!

outer quail Sep 9, 2024, 1:23 PM

#

Okay that means I have to try the account which is integrated into test as well as live mode
Is that correct?

wintry ridge Sep 9, 2024, 1:24 PM

#

Yup

outer quail Sep 9, 2024, 1:36 PM

#

I can try this and let you know

#

Thank you for your help @daring berry & @wintry ridge

#

Is there anyway that I can convert live to test acocunt?

wintry ridge Sep 9, 2024, 1:50 PM

#

No. An account that can operate in livemode can also operate in testmode, there isn't a conversion that needs to happen.

outer quail Sep 9, 2024, 1:59 PM

#

okay but for this case I need an acocunt which is available in both, Right?

wintry ridge Sep 9, 2024, 2:02 PM

#

daring berry you can technically also connect the account in test mode as well (by doing http...

The account is already available in both, the problem is that the Connected Account is only connected to your Platform in one mode.

You'll either want to use/create a Connected Account using your testmode API key from your Platform account, or use the approach my teammate mentioned in their message above.

#dishant_cli-connect-events