Hi,
Thanks for prompt replies.
We are getting the straight up DECLINE webhook notifications in SandBox environment and not in the Production environment.
Below is a sample DECLINE webhook notification. We get this decline webhook notification when incorrect ZIP code is entered on an Accept Hosted payment form:
{"notificationId":"cb40d7b8-76ad-483a-8a35-6395067b5035","eventType":"net.authorize.payment.fraud.declined",
"eventDate":"2019-08-28T21:51:05.9286148Z","webhookId":"48541e7e-945b-4a9a-88de-187c1f75d9b5",
"payload":{
"responseCode":2,"avsResponse":"E","authAmount":25.00,
"fraudList":[{"fraudFilter":"Enhanced AVS Handling Filter","fraudAction":"decline"}],"entityName":"transaction","id":"60126516580"}}
To replicate this, set up WebHooks, use Accept Hosted form, and submit a payment with Zip 46203 (to test decline). Authorize.Net will then send a Decline webhook notification in SandBox environment.
However in production, we are not receiving any Decline webhook notifications.
Back to my question:
Are SandBox and Production environments not the same in terms of functionality?
If so, when can we expect the DECLINED(net.authorize.payment.fraud.declined) webhook notifications in Production ?
Thanks,
Arun