Authorize.net Gateway Errors without Message

[colinodell]

We received the following response from Auth.Net this morning:

Thank you for contacting Authorize.Net in regards to that error. We apologize for the inconvenience.

We have reviewed this with the development team involved and identified the cause as being due to a code change to limit the field separator value to 1 character. We have rolled back this update, your connection should be working.

Although it would be recommended to use field encapsulation and field separator values instead of a multiple character field separator going forward.

I hope that information is helpful.

---

[rgallagher71347]

But yet, they still have not updated https://status.authorize.net/

They push us to use that page, but then sweep a major problem under the carpet and don't even really publicly acknowledge it.

I think they should be held to a higher level of accountability then that.

Also, what are they doing pushing a major code update to their production environments at 10:00 AM PST & 1:00 PM EST on a Tuesday?

[harisnano]

Is there an ETA on when Authorize.net is going to rollback the change? Also will the rollback cause any issue with the patch?

[zoeyurifoox]

The rollback happened yesterday.

The patch will continue to work and you should implement the patch regardless of it working now.