DECLINED WebHook Notifications not being sent in Production

[arun1103]

We are moving from SIM to AcceptHosted method.
We enabled WebHooks and are using it.
In the SandBox environment, we tested and we are receiving DECLINED  (net.authorize.payment.fraud.declined) webhook notifications.

Fyi... we have all Payment Events enabled(including net.authorize.payment.fraud.declined) in WebHooks settings in Production and Test. 

 
We moved to Production and we are not receiving DECLINED(net.authorize.payment.fraud.declined) webhook notifications. We are only receiving SUCCESFUL(net.authorize.payment.authcapture.created) webhook notifications. 

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

[Renaissance]

@arun1103

The transactions in question trigger fraud filters in the interface?

[arun1103]

Hi,

When you say "fraud filters in the interface", do you mean the WebHooks settings we choose ? 

All the "Payment Events" are selected, including the net.authorize.payment.fraud.declined (declined transaction).

Thanks,

Arun

[Renaissance]

@arun1103

I mean the transactions for which you are not getting webhooks. You say that you are not getting webhooks for fraud filter declined events. You are only supposed to get those webhooks when a transaction is flagged as potential fraud and you decline the transaction either in the interface or through an API call.

[arun1103]

We have AVS enabled. 

We see the message 'Transaction is Declined' on the Accept Hosted payment form. 

We also see the declined transactions in the Authorize.Net user interface. 

Thanks,

Arun

[Renaissance]

@arun1103

You do not get webhooks for those transactions. The FDS declines do not give the user a “this transaction has been declined” message . From the customers perspective it is the same as any transaction. Then on the merchants end there will be a notification that the transaction has been held. The merchant can accept or decline. If you decline you will get a Webhook for that transaction.

What you describe is a straight up declines transaction, and there is no way to get a webhook for that transaction. To get a webhook you need a transaction Id, and you do not get a transaction Id until payment has went through or been held.

[arun1103]

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

[Renaissance]

@arun1103

The zip code you enter is not an incorrect zip code. It is a zip code to trigger a fraud filter event. Sandbox and production are identical. Sandbox has those zip codes to trigger events. But the short answer to your question is that you will not receive a webhook for declined orders. To get a webhook the transaction has to at least make it to the point that you have a transaction id.

[arun1103]

It turns out that Advanced Fraud Detection Suite (AFDS) on the production account was not enabled. We had the old suite enabled.

The SandBox environment by default had the AFDS enabled.

We now get the webhook notifications for Declined transactions(address mismatch) - 'net.authorize.payment.fraud.declined'.

To sign up for Advanced Fraud Detection Suite™ (AFDS): - Click Tools from the main toolbar. - Click Fraud Detection Suite in the main left side menu. - Click Sign Up for the Fraud Detection Suite at the bottom of the page. - The Fraud Detection Suite Service Addendum page appears. - Click the checkbox labeled I have read and understand the Terms of Service.

[Renaissance]

@arun1103

Good. So the transactions were fraud detection transactions. You made it sound like you wanted webhooks for declined transactions in general