#belle_webhooks
1 messages ยท Page 1 of 1 (latest)
๐ 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/1365101635822424126
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- belle_error, 21 hours ago, 47 messages
Hello again. ๐
hello again! ๐
I am once again asking for your assistance
I feel a bit dumb, but I think I just realized what the problem could be...
Of course! It looks like your only livemode webhook is a Connect webhook instead of an Account webhook; you'd need to add a live Account webhook in order to pick these events up.
Sorry, that was bad timing. I meant "of course I can help," not "of course you're dumb" - you're obviously not.
hahah no worries
I can be a bit dumb at times, that much is true ๐
I just realized this webhook is set up to listen to events from connected accounts only
and the only accounts that are connected accounts are my seller accounts
so it makes sense the webhook is not picking up checkout sessions from non-seller accounts
Yuppers. But if you're using Destination charges, those Events will be emitted on your Account webhook.
How can I create a new webhook that listens to events from any user, regardless if they are a connected account or not?
You can't, but you could use the same webhook endpoint URL for both if that makes sense for you.
i.e., you could have events sent to the same URL whether they're for your Account or for your Connected Accounts.
hmmmm. I'm not sure I understand, I'm sorry. I need users to be able to checkout whether they are connected accounts or not, so would I be able to do this with this webhook even though it seems to only listen to events from connected accounts?
And how come it's not possible to create a new webhook?
I should mention that when I was testing in development with a test key, this was working correctly. I guess it was only a "mock" webhook and not a real one. I might be a bit confused on how stripe webhooks work
Yes, because in testmode you have an Account webhook, but no Connect webhook.
In live you have a Connect webhook, but no Account webhook.
I'm reading stripe's docs and it sounds like webhooks can only listen to events if they are either from my own account or from a connected account, is that correct?
And if that is the case, is it even possible to be able to use webhooks to process checkouts from a user that does not have a stripe connected account?
Or is it possible that a webhook set to listen to events from my account would work to be able to let any user checkout?
It can listen to both, but you're likely to cause issues for yourself if they're literally the same event handler, unless it's set up to distinguish between the two types of events and route to the correct code.
You can only tell Stripe where to send Account events and where to send Connect events; they can be sent to the same place.
So I'm thinking of creating a new event destination within this webhook and setting it to listen to events from my account. It would have the same endpoint URL, do you think that could cause issues? Should I delete the endpoint that listens to events from connected accounts altogether?
So I created a new destination and tried it and it seems to work now
You may want to listen to some Connected Account events, but if it was completely working in testmode, then yes, what you're proposing is likely what you want to do.
You could check for the presence or absence of account on the Event payload: if it's there, it's a Connected Account event. If it's not, it's not.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Ok, I think I got it ๐ I might need the connected accounts endpoint in the future for seller events, so I think I will keep both
thank you so much for all your help!
If the webhook endpoint's code isn't set up to deal with Connect stuff at all, then just remove the endpoint so you don't have to worry about it getting events it doesn't expect.
Also you're very welcome! ๐