We've created webhooks for each of several types of events we want to track.
When we go to test them, no matter which webhook we test (e.g.
, the event that is sent is "net.authorize.payment.authcapture.created".
What is the point of a webhook test if it doesn't actually simulate the webhook?
Solved! Go to Solution.
I don't think its our domains issue, It was working perfectly yesterday on the same domain, Today stoppeed working and when testing it gives this error
Error: The ping operation failed. This could be due to connectivity issues, invalid url or server downtime. Check the url details for the webhook and try again
> if you moved to a well established domain you wouldn’t have this problem.
Or if we moved to a payment gateway that could be bothered to invest in DNS infrastructure that any startup in 2019 has, we wouldn't have this problem.
I get that if you've made the investment in Authorize.net, you're willing to put up with this sort of thing because you're already on board. You're hardly going to scrap your existing investment just because of a DNS issue on a sandbox. But imagine that that's your first ineraction with Authorize.net, and the 'legacy' provider you're moving off of never had any problems like that. How do you suppose it looks to us engineers, much less our customers?
It miraculously started working tonight, so it likely was DNS. Nothing like a black box with no detailed errors to instill confidence.