#michael-harvey_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/1374488903268175873
đ 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.
- michael-harvey_api, 6 days ago, 8 messages
Hi! Do you have more than one Sandbox? Are you sure you swapped the API keys in your code that created the link?
actually, do you know what is the url that the request comes from? i want to make sure that we are allowing requests from stripe into our network
If you don't see the event in your Dashboard, that either means we didn't generate it, or you're looking in the wrong Dashboard - or rather, that the API keys you are using to create the Payment Link are not from the Stripe Account you expect.
i do see the event in the dashboard, but i need to allow access for Stripe events into our network
is there a url or ip address that i need to grant access to?
What's the Event ID?
evt_3RQwplQphwi3c0fh1pfmUeTh
https://docs.stripe.com/ips#webhook-notifications has a list of the IP addresses the webhook deliveries might come from.
https://www.ssllabs.com/ssltest/analyze.html?d=x01.oadomain.com&hideResults=on
The problem is with your webhook server's TLS certificate.