Webhooks Not Triggering / No Data

[bebates]

It looks like Webhooks are problematic again.  Around 4:19 PM CDT, my system started to receive Webhook payloads from Authorize.net that were invalid and/or empty.  responseCode was 0 even though I am only supposed to receive success payloads, authAmount was 0 which would be impossible, and entityName is transaction (which is correct), but thats all that I see in the payload node.  My merchantReferenceID field is missing, as well as the transaction ID itself.

Is there anyone that can actually talk to Authorize.Net support/developers to get this resolved?  I have quiet a few transactions I am going to have to record by hand due to the failing webhook system.

[DerekC]

Same boat.  All payment webhooks are sending an invalid payload with responesCode 0 and no "id" property.

[DerekC]

Fixed after last message and now broken again since the 14th.

Payment webhook payloads are:

1.  Missing the 'id' field with the transaction id

2.  responseCode = 0 & authAmount = 0.00

Making payment webhooks completely broken and useless.  Even more frustrating is that I am returning a 400 (bad request) when the webhook is sending bad data and then they disable the webhook (rather than fixing their bug)