#sow - express accounts
1 messages · Page 1 of 1 (latest)
You need a Connect endpoint for events related to connected accounts
You can create a test mode account and run through some onboarding pages to trigger account update events
Does the event work without the account id parameter, or is it telling you it's unsupported?
Are you still there and needing help @earnest wagon ?
yes sorry was away
can we use the stripe trigger cli for the same?
I am not seeing any events if we I use stripe trigger account.updated <connect_express_account_id> in teh connected webhook event
Hello! It could be that the account in question isn't connected to your platform account yet. Are you seeing the account.updated events on the account itself?
let me check
this is the test stripe express connect account : acct_1KC5Qw2HrjRfTo1u
i am not seeing any logs here : https://dashboard.stripe.com/test/connect/accounts/acct_1KC5Qw2HrjRfTo1u/developers
can I use CLI to mock an update stripe trigger account.updated <connect_express_account_id>
I'm seeing account.updated events on that Account.
The last one was back in late December though.
how can i create one update now using cli to test ?
The account.updated event isn't supported with stripe trigger, but you can use Stripe CLI to make a change to the Account that would in turn trigger an account.updated event to be generated, such as updating the Account's metadata: https://stripe.com/docs/api/accounts/update#update_account-metadata
ok thanks but the problem is I am not getting that event if I have configured the webhook to listen for the connect events
it is only going to the webhook with "Direct" mode
When I tried now, it says the below error, stripe accounts update acct_1KC5Qw2HrjRfTo1u -d "metadata[order_id]"=6735
stripe accounts update requires exactly 1 positional argument. See stripe accounts update --help for supported flags and usage
tried this way too, stripe accounts update --stripe-account acct_1KC5Qw2HrjRfTo1u -d "metadata[order_id]=6735"
stripe accounts update requires exactly 1 positional argument. See stripe accounts update --help for supported flags and usage
Is Stripe CLI logged in as your platform account?
You wouldn't use --stripe-account when updating the Account via the API, you would specify the account ID.
To clarify, stripe accounts update acct_1KC5Qw2HrjRfTo1u -d "metadata[order_id]"=6735 throws the error about the positional argument?
ys same error
Strange. Can you share a screenshot of the command and error?
👋 @earnest wagon Rubeus has to head out soon so I'm also jumping in. give me a bit to catch up
Quick question - what version of the CLI are you using (you can check by running stripe -v)?
stripe version 1.7.9
Sorry for the delay - running into some issues getting my CLI on the same version as yours! Just wanted to tell you I'm still looking!
np thank you
finally on the same version as you, but I'm still not getting the same errors.... and just to double check your CLI is logged into the platform account, right?
yes
I wonder if the issue here is windows specific
hmm ok i will try with linux / bash mode and see
or can I use one single webhook endpoint (Direct mode) to capture all events including stripe connected account updates?
Helo, karbi had to step out. Catching up here and will have an answer to that in a minute
I think it should but it might be worth testing that while also specifying the separate connect endpoint to see if that triggers properly
Is that command working now but the event is not getting picked up?
All good, I think issue was m CLI within Windows version. I used your shell in console and it worked and I can see the events coming through : https://stripe.com/docs/stripe-cli?shell=true
thank you so much!
That is great to hear! Glad you could get it working
thanks for your all help !!