@antonie17You do not have to send get requests, period. Not in time intervals and not even one single time. Here is how it works-
-you create a file on your website to process the webhook
-tie that file to a non-parameterized url on your website
-go to your merchant interface, then account, then Webhooks
-under endpoint copy and paste the url from step 2
-enroll in the events you want tied to that endpoint. E.G. authcapture
-set it on inactive and save
-you will have the endpoint set up with a Test button in your interface. Click test . If it says successful, set your endpoint on active. It it isn’t successful, three main causes are 500 response from server, url auth.net doesn’t like (e.g. url with query string), or DNS resolution. Also you cannot do them locally. Has to be on a remote connection or routed to some service like ngrok. IIS i believe has something where you can have webhooks routed to your localhost. Check your server logs and see what’s up. Do this and test. Once you get a ping successful notification move it to active
-Once it is active, you are ready to process live transactions (meaning sandbox or production transactions)
-every order that is completed on your accept hosted page will send a webhook to your endpoint, provided you are enrolled in the event. This happens with no effort on your part
-auth.net almost never goes down. If it fails to hit your endpoint 99.9% of the time it is you. So what auth.net does is repeatedly try to send any webhooks that do not return a 200 response. They do this over a period of 3 days. They do this at various intervals, without you doing anything.
-so what you need to do once you are getting successful pings (if your Test button pings are successful, all of your live pings will be too, unless your DNS is on and off, or if you change your programming on your endpoint and start throwing errors) is set up your programming to do the updates you need. Start by running test transactions and capturing the json payload. It will have a transid. That’s all you need.
Then once your updates are happening, you can set up the hash validation. For this you can set up a hash function and have successes and failures dumped to a log file. Set your endpoint on inactive and ping it with the Test button. See if you get failure or success. If you get success that means your hash function is working right.
