#ssqwid_webhooks
bright scrollBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1349822356670910536
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
quasi dust
Hello, when I look at the endpoints on that account, none of them are specifically subscribed to charge.succeeded. That event would show up on an account endpoint if it was subscribed to that event type
And the reason it is sent to that connect hook is because it is subscribed to that event type, so it will get events from any of that platform's connected accounts that are subscribed to that event type
leaden thunder
This is the endpoint we're looking at that is subscribed to charge.succeeded: https://dashboard.stripe.com/workbench/webhooks/we_1J2K8H2nnsqyEcvlPxj9k2Q1
It now appears to us that our account is somehow acting as BOTH "your account" and a connected account. Our account is shown in the list under Connected Accounts: https://dashboard.stripe.com/connect/accounts/acct_102h252nnsqyEcvl - but it also is the primary account.. is it perhaps set up in a strange or incorrect way that would make it behave as both the platform account and a connected account?
quasi dust
Ah gotcha, I see now. Yes I do see that the account is considered to be connected to itself. I forgot that that could happen. Can you see your account listed as an installed app on this page? That may let you disconnect
https://dashboard.stripe.com/test/settings/apps
Can look into other ways to disconnect if that does not work
The other way that I can think of doing this is using OAuth to revoke the account's connection. I am not finding much no how an account can be connected to itself but I am pretty sure it would have to be OAuth https://docs.stripe.com/connect/oauth-reference#post-deauthorize
leaden thunder
I see it listed under Connect Extensions
ok, very interesting.. we'll have to think about it and look in test mode.. I'd be nervous to disconnect or make any other major changes to our main account without being sure it's not going to have unintended effects
quasi dust
Yep, so you should be able to click ... and Uninstall to revoke that access. I think the only things this should effect is that the connect events should no longer be sent and you won't be able to retrieve objects if you pass your own account ID as a connected account ID. I will see if I can find anything else but there isn't much documented on this that I have found so far
Ah scratch that second part. You can still retrieve objects like that even if your account isn't "connected" to itself
leaden thunder
Ok thank you.. we'll investigate this in test mode for sure. makes me a bit nervous to make any fundamental changes to the way our main account is set up, but we'll test and tread carefully. if you find any other information about it, we'd love to have it. In any case this definitely helps us solve a confusing mystery!
quasi dust
Sounds good, I am still having a bit of trouble finding docs. I will ask my colleagues to see if they have anything and will get back with whether we can find anything.
quasi dust
From looking a bit further my colleagues haven't found other consequences of note. It looks like this used to be possible with the OAuth flow, but we started preventing it in 2020. The two relevant changes that I have found are:
- Connected endpoints won't receive self events
- Cannot make direct charges with an application fee anymore (will still be able to create them without a fee)
So testing this in test mode before trying it in live mode is definitely a good idea, but we haven't found anything too big to be on the lookout for ourselves.