#coreyw - webhook testing

1 messages · Page 1 of 1 (latest)

misty temple
#

You can trigger these by making the corresponding API requests for a test mode connected account, or if they are express accounts these will fire while going through onboarding

karmic matrix
#

Is a test mode connected account different from enabling test mode on our main account? We only have one account, as far as I understand it.

misty temple
#

ah, ok, stepping back what are you trying to do? Those events are typically related to Connect account setup/verification. It sounds like you're not a connect platform, though.

karmic matrix
#

Correct, I don't believe we are on a connect platform. We've hooked up those webhooks I mentioned mostly as a security check, so if someone manages to log into our stripe account and tries to change the bank account (https://dashboard.stripe.com/settings/payouts) to their own, we could get a notification. Same for changes to users on the account. We just want to get notifications when users in our Stripe console account are added/modififed/removed.

#

However, it doesn't look like there is a "test mode" version of bank or user data, so it appears we can't test those webhooks by actually modifying users or bank details in the console. I believe that would trigger the live webhooks as opposed to the test mode webhooks.

#

I'm just looking to confirm that.

#

We've used the "Send test event" for the test mode webhook, but it would just be nice to trigger those webhooks with actual actions in the console vs the test event.

misty temple
karmic matrix
#

Ah, I see. Is there any way to receive emails or notifications via other channels for particularly sensitive changes, such as bank account informaiton?

misty temple
#

No, but those actions should require your password to take -- for more help with your account security I'd ask you to reach out to our support team here: https://support.stripe.com/contact

karmic matrix
#

Ok, thank you for those clarifications.

misty temple
#

NP!