topic Notification response field responseCode 0 reasons in Integration and Testing

Notification response field responseCode 0 reasons

tijimolvt — Tue, 06 Feb 2024 07:54:55 GMT

We have an issue with the payload responseCode.

Sometimes we are getting the responseCode '0'

When checking the Authorize.Net documents it seems that the '0' responseCode is for declined transactions. So we have a condition checking in our code for responseCode=1 and processing this transactions only. But we noticed that the transaction in processed in Authorize.net.

Will you please give a clarification about this?

Re: Notification response field responseCode 0 reasons

mp3juice09 — Tue, 21 May 2024 06:02:59 GMT

Since we updated to London Patch 8 Hot Fix 2, I am intermittently getting a "0" HTTP response code from my outbound REST calls within the instance.The error returned is "java.lang.NullPointerException". The strangest part is that the normal response is still returned in Outbound HTTP Requests (it shows a normal 200 HTTP response code instead of 0). Anyone else have sporadic issues with RESTMessageV2 on this release? HI Support hasn't found much so far.