#jefskoa_webhooks
royal harnessBOT
👋 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/1407757780009484442
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- jefskoa_webhooks, 34 minutes ago, 43 messages
urban wolf
This is a continuation of a previously conversation that was closed.
The most recent event I tested where I expected the 'account' element was: evt_1RyEmYI1VSC7qNYwnSCM4s0G
visual ridge
I'm looking at the request (req_2aqlZlJH2Duz4O) associated with the event you shared and this is not a connect request. It's a Payout request made on the account.
urban wolf
Correct. I'm capturing the event in my webhook app. The issue is I need the connected account for a payout.
visual ridge
I'm not sure what you mean by you need the connected account for a payout.
Have you created connected accounts in the Sandbox?
urban wolf
yes. And I"m logged into the Dev Dashboard sending at the Platform level. I'm trying to mimic a production payout at the platform level where the payout info would be triggered from the webhook of a payout with a connected account. That connected account is needed by my app to determine our internal customer Id. Since I'm at the platform login, I am looking to test:
stripe trigger payout.updated
My listener pgm is active and getting data. The issue is I need to "feed in" a connected account number. Can that be passed in the trigger option?
For example, in my sandbox, I need the webhook info for a payout to have the account element set to: acct_1Qpv01IvHz5DOm3o.
Hold on, I think I found the option.
OK, still not seeing the account entry in the body of the webhook json when I use this in the CLI:
stripe trigger payout.updated --stripe-account acct_1Qpv01IvHz5DOm3o
The last event Id I tested and passed in the stripe account w/ the trigger was: evt_1RyFBSI1VSC7qNYwnMd6nLMx
visual ridge
Ok, I just tested this on my end and it works as expected. I looked at the request (req_33VEWvrRK7sazh) for the event you shared and it's still not a connect request. There doesn't appear to be anything wrong with the syntax you shared.
royal harnessBOT
urban wolf
when you write "it works as expected", did you find the connected account string anywhere in the payload received by the listener?
I'm not sure I'm explaining my challenge correctly. We are attempting to capture all payouts from any of our Connected Accounts. We are logged into the Stripe CLI at the platform level so our listener app gets everything. The challenge I'm having is getting a Connected Account into the payload/json. This is all running in a sandbox now.
peak fern
Hi, taking over as my teammate needs to step away. Let me catch up.
urban wolf
OK, I need to step away for lunch. Can you ensure this doesn't go dormant while I'm away? I don't want to start over again if the thread closes while I'm out. 😭
peak fern
I will be here for another hour.
urban wolf
ok
peak fern
Are you able to try stripe trigger payout.created --stripe-account acct_1Qpv01IvHz5DOm3o ?
urban wolf
yes, I did that:
stripe trigger payout.updated --stripe-account acct_1Qpv01IvHz5DOm3o
I received the payload/json in my .net app. Looks good. Stripe-Signature header is there. Stripe-Account header is not there and the account element in the body is null.
peak fern
stripe trigger payout.created --stripe-account acct_1Qpv01IvHz5DOm3o and not updated please
You're trying payout.updated
urban wolf
Correct. I need to know when it was paid out to the bank not when created. I found while payout.paid is an event, it is not an event I can send in the CLI, payout.update was as close as I could get.
peak fern
Ok, I think I might know the issue.
You need to be logged into the platform first, then you can use the stripe listen command with --forward-connect-to <url> in order to receive the event that has the account ID that you are looking for
https://docs.stripe.com/cli/listen#listen-forward-connect-to
If you do this, then you will see the account attribute from the Event that you are expecting. You can see in the docs that this attribute only exists when you are using Connect
https://docs.stripe.com/api/events/object?api-version=2025-07-30.preview&rds=1#event_object-account
urban wolf
Yes, that is what I am doing. I am sending the Trigger event from the Stripe dashboard in a web browser where I am logged in to the Platform. I then have Stripe CLI running on my pc with this listening command:
stripe listen --events reporting.report_run.succeeded,payout.updated,payout.paid --forward-to localhost:64492/v1/webhooks/receive/stripe
My app is receiving the payout information, but I need to be able to send in a Connected Account to further test the app. Now, my assumption (and I hope I'm correct) that in Production, we can set up the web hook across the entire Platform, get the payouts from any of our hundreds&hundreds of Connected Accounts and find that connected account value somewhere in the HTTP payload. (Can you verify I'm right?) But what I'm trying to do now is test Stripe Sandbox with my local app where I can use the Connected Account associated with a test payout that I need to grab an internal customer Id based on that Connected Account. Without getting that Connected Account in the JSON payload from the webhook info, I'm dead in the water.
royal harnessBOT
peak fern
Yes, that is correct. If you create a Payout via the API: https://docs.stripe.com/connect/manual-payouts#regular-payouts you'd see the account id
Ok, my teammate is taking over.
urban wolf
The Payout would be created by Stripe as our Connected Accounts are set to auto-create for the most part.
But I also need to know how to test my app with Platform and ConnectedAccounts.
Does Stripe provide Dev/Tech support so we can get on a call? I feel like I'm spinning my wheels with multiple people coming into this thread and not being able to know if Im explaining my challenge correctly each time.
turbid spire
Hi taking over here. We staff this discord server in shifts and help many people out at once. If you would rather have 1:1 support you can write into Stripe Support. They don't do calls with a dev unless you're a premium support user though. They'd just help you over email.
urban wolf
OK, I'll keep trying here in this thread. Let me know what info you need to continue the discussion. Thx.
turbid spire
Reading through the thread real quick
royal harnessBOT
turbid spire
So looks like you're using the dashboard to run these stripe trigger commands
One thing I did notice is the event you shared earlier is a payout.paid event not payout.created
urban wolf
Yes, I don't need when it was created. I need the event when it was actually paid to the bank. As I understand it, those are different events, different time lines. The Dashboard/Dev -- and perhaps the CLI in general -- doesn't support a payout.paid trigger. I have to use the payout.updated event - not ideal but not sure what else to use to test. And I'm need to get an account in the json/payload which is the main crux of my question -- how to get that done in a sandbox. Then back up the a question above. I need confirmation that in a production environment when we have the entire Platform (all connected connects) sending out webhook events for payouts.paid that the connected account (that account associated with a payout) is included in the payload/json . Phew!!! That's a lot.
turbid spire
Ok I was able to repro your issue
Looks like it's a dashboard workbench bug
If you log into stripe cli on your local machine you should be able to successfully pass --stripe-account in the stripe trigger command
Looks like workbench in the dashboard is ignoring that param for some reason...
urban wolf
OK, I'll give it a try ... hold on pls. Might be a few minutes.
turbid spire
Sure np
Ok also my colleague figured out how to do this in workbench
It expects slightly different syntax agh
Sorry this is so confusing
This is the syntax you need to use in the dashboard: stripe payouts create --amount=10000 --currency="USD" --stripe-account="acct_1QSARNQPFyyXy2aJ"
Notice the equal signs and the quotes around the account id
urban wolf
Hey, I think I got it!!!!!
stripe trigger payout.updated --stripe-account acct_1Qpv01IvHz5DOm3o
turbid spire
Yeah ^ should work locally
If you want to do it from the dashboard workbench you'll have to use the syntax I shared above
urban wolf
Will that trigger the event for the web hook:
stripe payouts create --amount=10000 --currency="USD" --stripe-account="acct_1QSARNQPFyyXy2aJ"
turbid spire
It will, but it's not running a stripe trigger simulation
it's actually just running a payout creation api request on the connect account
ie running this request: https://docs.stripe.com/api/payouts/create
urban wolf
OK, I need that simulation so I get back to a payout event. I'll use the Stripe CLI on the PC. Thanks!