Authorize.net - Invalid Notification

  • Posts: 139
  • Thank you received: 9
  • Hikaserial Standard Hikashop Business
2 days 19 hours ago #370932

-- HikaShop version -- : 6.4.0
-- Joomla version -- : 5.4.3
-- PHP version -- : 8.2.30
-- Browser(s) name and version -- : Firefox 148.0.2
-- Error-message(debug-mod must be tuned on) -- : Invalid notification

On occasion we have a credit card transaction that is authorized via Authorize.net SIM, but shows up as declined in the backend. For the most recent case of this, the customer reported that they got an "Invalid notification" error when they made the payment. We were on Business 6.1.0 at the time and have just upgraded to 6.4.0. Maybe that issue has been corrected since 6.1.0, but I wanted to report the issue just in case it hasn't. We've seen this issue for some time with the Authorize.net SIM, but the vast majority of transactions don't have this issue.

Please Log in or Create an account to join the conversation.

  • Posts: 85323
  • Thank you received: 13937
  • MODERATOR
2 days 15 hours ago #370937

Hi,

The "Invalid notification" error means that the hash validation between Authorize.net and HikaShop failed. The plugin compares a hash calculated from the notification data with the hash sent by Authorize.net to verify authenticity.

Since you mentioned that most transactions work fine and this is intermittent, it is likely related to special characters in the customer's name or address. The SHA-512 signature hash includes customer data fields (name, address, city, state, zip, etc.) and if any character is encoded differently between what Authorize.net sends and what PHP receives, the hash will not match.

Could you check: do you have a Signature Key configured in the plugin settings? This is different from the MD5 Hash field. Authorize.net deprecated the MD5 method back in 2019, so you should be using the Signature Key (SHA-512) instead. You can find/generate your Signature Key in your Authorize.net merchant account under Account > Settings > Security Settings > General Security Settings > API Credentials & Keys.

Also, could you check if the affected transactions have something in common? For example, customers with accented characters in their names, special characters in their addresses, or non-US addresses? That would help confirm whether this is a character encoding issue in the hash calculation.

If you have debug mode enabled in the payment method settings, you should also be able to get more information about the problem in the "Payment log file" under the HikaShop configuration page. The details there will help us pinpoint the exact cause.

Please Log in or Create an account to join the conversation.

  • Posts: 139
  • Thank you received: 9
  • Hikaserial Standard Hikashop Business
2 days 4 hours ago #370951

There is a Authorize Signature Key in use. Should I clear out the MD5 Hash box?

For the recent customer with the problem, there was no special characters with the customer's info or address. I did not make note of other customers with that issue. I will if that happens in the future.

I'll enable the payment debug feature.

Please Log in or Create an account to join the conversation.

  • Posts: 85323
  • Thank you received: 13937
  • MODERATOR
1 day 17 hours ago #370954

Hi,

You don't need to clear out the MD5 Hash box, but you can if you want. It won't change anything.
Report to us once you get the issue again with the debug turned on so that we can check the payment log file.

Please Log in or Create an account to join the conversation.

Time to create page: 0.060 seconds
Powered by Kunena Forum