#sow - express accounts

1 messages · Page 1 of 1 (latest)

lethal basin
#

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?

lethal basin
#

Are you still there and needing help @earnest wagon ?

earnest wagon
#

yes sorry was away

earnest wagon
#

I am not seeing any events if we I use stripe trigger account.updated <connect_express_account_id> in teh connected webhook event

safe vault
#

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?

earnest wagon
#

let me check

#

this is the test stripe express connect account : acct_1KC5Qw2HrjRfTo1u

#

can I use CLI to mock an update stripe trigger account.updated <connect_express_account_id>

safe vault
#

I'm seeing account.updated events on that Account.

#

The last one was back in late December though.

earnest wagon
#

how can i create one update now using cli to test ?

safe vault
earnest wagon
#

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

safe vault
#

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?

safe vault
#

Strange. Can you share a screenshot of the command and error?

earnest wagon
thick flower
#

👋 @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)?

earnest wagon
#

stripe version 1.7.9

thick flower
#

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!

earnest wagon
#

np thank you

thick flower
#

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?

earnest wagon
#

yes

thick flower
#

I wonder if the issue here is windows specific

earnest wagon
#

hmm ok i will try with linux / bash mode and see

earnest wagon
#

or can I use one single webhook endpoint (Direct mode) to capture all events including stripe connected account updates?

spare bloom
#

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?

earnest wagon
#

thank you so much!

spare bloom
#

That is great to hear! Glad you could get it working

earnest wagon
#

thanks for your all help !!