#adi_webhooks
desert pelicanBOT
đ 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/1357336896157519984
đ 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.
- adi_webhooks, 49 minutes ago, 13 messages
- adi_webhooks, 3 hours ago, 4 messages
distant owl
Hi, let me help you with this.
but not through the checkout session.
What do you mean by this?
thorn eagle
Hello, I would need some help with the process of online payment with the webhook. we_1R5mwFKDXIK7QcLztZi6njHM
I create a checkout session in the backend, then i send the link to the frontend and it opens it, as a reference I saved cs_test_a1VmnMk79CbICYN63tVTfW0v4qAtO5W8sHTuvO6fR7cWwJyup6MRM4KboM this, i think it is the checkout session id. The problem is that it doesnt come to the events like payment_intent.succeeded after I make the payment successfully. It doesnt send any event to the webhook from what i can see.
Maybe I have something in the process of expecting the events wrong with how i have my webhook setup?
The only time i had luck with sending events is only with the Stripe CLI.
distant owl
I see Events are correctly created, e.g. checkout.session.completed https://dashboard.stripe.com/test/events/evt_1R9n4kBbJ5V7UikQ4LSqAmvJ
But it doesn't seem like you have any webhook endpoints registered on the Connected account.
You want to get the Events from the Connected accounts on your Platform account, right?
thorn eagle
I didnt know these are split. Is this possible?
Or, do I need another webhook setup for that?
distant owl
Yes, some endpoints listen to events on your own (Platform) account, and others listen to events happening on connected accounts.
desert pelicanBOT
thorn eagle
Is there any possibility to let my webhook listen to the connect accounts or is this the only way?
I see that there is this connect parameter that is by default false, where can i set it to true? Is it doable in the dashboard?
distant owl
It's better to create a separate webhook endpoint for Connect events.
thorn eagle
Where can I set it up to be a Connect Webhook?
I see now that this differs on the acacia version from the new basil version
native scroll
Hey @thorn eagle stepping in since vanya needs to step away
thorn eagle
Hello
native scroll
This is a choice you make in the UI when creating a webhook endpoint in the Dashboard, or using the API it is determined by using connect=true:
https://docs.stripe.com/api/webhook_endpoints/create#create_webhook_endpoint-connect
This cannot be change after endpoint creaiton, so you'll need t create a new endpoint to set it as Connect-type
thorn eagle
So if I delete my current one and try to create one with the same URL and events I would be able to see somewhere this type?
I see this is an either/or choice. Can I create it under the same URL but different endpoint ? Like having my account webhook /webhook/account and another one /webhook/connect ?
native scroll
Yea, you can use either the same or different URLs, up to you
I suggest using different ones to make handling events simpler, since there will be distinct signing secrets
But technically you can use the same URL for more than 1 endpoint
thorn eagle
Since I have only 1 backend I meant that I want to use the same base URL and then have different endpoints for both because they both have different webhook secrets as un said. I just implemented it right now. I will run a test in 2 minutes
native scroll
YOu mean two different paths on the same domain? like example.com/account-webhooks and example.com/connect-webhooks?
Thats totally fine, you can use any URL you want, thats up to you