Hello Everyone,
We've recently noticed an issue in our Authorize.NET integration, which has worked fine for many years. The x_SHA2_Hash parameter in silent posts is now empty. A signature key had already been generated for these accounts. We are seeing this both in sandbox and production.
I regenerated the signature key in sandbox, and now the parameter is populated in the silent posts for initial payments created via AIM, but not for rebills of the ARB subscription.
Is anyone aware of any changes in the functionality of the SHA2 hash in silent posts since 2019? Is it necessary for me to pass some parameter in the XML ARBCreateSubscriptionRequest to cause an SHA2 hash to be generated?
Thanks
