#alexatrovertown
1 messages ยท Page 1 of 1 (latest)
Can you share an event id you expected to be delivered?
I'm using Checkout in a webview context, so I don't know that I have access to the actual event ID without accessing the customer's account
๐ stepping in
Are you seeing any Events sent to the webhook endpoint at all? Can you share a Connected Account ID that you expect to receive events from?
We basically need some ID to look at to be able to investigate
no, no events at all
connected account ID acct_1N1szSF7Pb0530gb
(test mode)
webhook ID we_1O9YrLLxba9E8AOFd3ndjPij
Thanks, looking
You haven't generated any Events on that Connected Account
So yeah none would be sent here.
Have you created your own test Connected Account and run tests generating Events on that account to ensure your webhook works?
I'm using Laravel Cashier, which I think doesn't allow specification of the connected account ID ๐ซ
I have it set via the Stripe SDK, but don't think I have a way of setting it within the Laravel Cashier config, which may be the whole reason behind this
None of that really matters to be honest...
You can do this completely with the CLI for instance
Or you can create a test Connected Account right through your Dashboard
And trigger events via the CLI. See: https://stripe.com/docs/webhooks#test-webhook
if I'm not passing the connected account's account ID in the checkout session, then no events would be associated with the connected account, right?
Correct, the Checkout Session must be created on the Connected Account
right, I'm using Laravel Cashier which doesn't support setting the account ID for its API requests, so I'll need to fork it to add that ability (per one of their maintainers' comments on a similarly reported issue) so I think this is more of a "me" problem than a Stripe problem ๐
thank you, will chase that down
Yeah as I noted, you can make these one off requests via the CLI or cURL if you don't want to fork. You can also trigger Events directly from the CLI