#drae_webhooks
dry sphinxBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1250094060484562954
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
shell tundraBOT
potent willow
Hi there 👋 it sounds like you're likely seeing the behavior that happens when you have a Connected Account connected to your Platform in both live and testmode:
https://support.stripe.com/questions/connect-account-webhook-configurations
It should be safe to have your livemode Event handling code, that's running on your live webhook endpoint, ignore the testmode Events.
regal stream
Shouldn't it be seperated? I don't understand why it was connected to the live mode anyways. Why when I change something on my local is it sending the live server events related to it? How do I stop this? Why did it connect to live when I do not have live keys locally?
This has also affected our testers, I don't see how they have managed to connect their test mode accounts to live considering the live keys only exist on one server
I mean.. I do see now that the account exists in both modes.. can we just delete the live mode accounts and will that sort it out?
potent willow
Shouldn't it be seperated?
It'd be awesome if it was, but this is unfortunately expected system behavior
Why when I change something on my local is it sending the live server events related to it?
If this is for a Connected Account that is connected to your Platform in both test and livemode, that's why. If not, I'll need more context and details to understand what you're referring to.
How do I stop this?
Disconnect the Connected Account in one mode, otherwise you can't
Why did it connect to live when I do not have live keys locally?
I'm not exactly sure offhand, my best guess is that the Connected Account went through onboarding in both live and testmode for your flow. I may be able to provide more insight on that if you can tell me more about how you onboarded/created this Connected Account.
regal stream
How can I identify all of the accounts which are both enabled for test mode and live, and disconnect the live accounts?
Thank you also for the response
I don't have the details at hand to give on how it may have been set up. I would imagine my local is more at risk of this issue as I do need to often switch between live modes- however with the UAT site tester accounts, this seems very odd.. so I would need to investigate more to see if there was some kind of issue in the past which mixed up keys or something... :/
If I could identify the accounts and disconnect them that would be ideal
potent willow
You can use the API to list Connected Accounts associated with your Platform:
https://docs.stripe.com/api/accounts/list
You can make that request in both live and testmode to see the list of Accounts for each mode and compare them.
regal stream
I will take a look, thank you
potent willow
However, taking a closer look at the Connected Account being used in your flow, it's a Standard Connected Account which can't be deleted or rejected.
https://docs.stripe.com/api/accounts/delete
Do you use OAuth to make the connections in livemode? If so, I believe you can use the flow shown here to remove them from your Platform:
https://docs.stripe.com/connect/oauth-reference#post-deauthorize
regal stream
It's been about 3 years since I touched the auth part of the Stripe set up, so I'm not 100% sure but I think we do.
Does this mean it has to be disconnected programatically ?
potent willow
There's also a dashboard tab in that section, but I'm less familiar with that approach since we focus on helping developers with our API in this forum.