Authorize.Net Accept.JS - suspecious AVS transations - verify vs pending

-- HikaShop version -- : 4.6.0
-- Joomla version -- : 3.10.10
-- PHP version -- : 7.4.30
-- Browser(s) name and version -- : any
-- Error-message(debug-mod must be tuned on) -- : None

In the old Authorize.net plugin, if the AVS threshold was reached in Authorize.Net's merchant control panel, the order in HikaShop was sent to pending. This was with Instant Capture turned on. This allowed the store owner time to review and release or cancel as needed.

However with Accept.JS, it is set to verified regardless of when instant capture is on.

The store owner has asked if that same behavior could be in Accept.JS, per the store owner's request.

May be it has to do with how Accept.JS handles the status code returned by Authorize.net?

I've updated the to 1.0.4 (was on 1.0.2), so not sure if this was addressed in that update since I cannot find a changelog for the plugin.

Does Accept.JS 1.0.4 work with PHP 8.1?

I got an error after upgrading the site to run under 8.1 on the final step of check out where I get a 404 and error:

error - Uncaught Throwable of type ParseError thrown with message "syntax error, unexpected token "readonly"". Stack trace: #0

It was working fine under PHP 7.4 before, but this is also part of an upgrade to Joomla 4.2.

PayPal standard payment plugin works fine.

Intresting.

I rolled back PHP 8.0 and now get a 500 system error:

Warning: foreach() argument must be of type array|object, null given in /plugins/hikashoppayment/authorizejs/lib/net/authorize/util/ANetSensitiveFields.php on line 60

The normal authorize.net payment plugin (AIM) works (using it as a temporary solution)

Hello,

I am checking to see if Authorize.Net Accept.JS has been updated to work with PHP 8.0? Found out when we moved from PHP 7.4 that ends security support on November 28th 2022 that we were unable to take credit cards because of the 500 Internal Server Error. That is what the customer said he had and also checked that we did not have any payments through Authorize.net when we normally have several in a day.

Okay, how would I go about getting the beta of the new version of the plugin to try out on php 8.0?

I suspect the issue with the ReadOnly token is that in PHP 8.1, ReadOnly is a reserved term, you can't name objects readOnly anymore. I'm seeing the same behavior in the Authorize.net JS payment plugin. Unfortunately, I have other code in my site that isn't compatible with PHP 8.0, so, I seem to be stuck. May I contact you regarding the Beta as well?

ReadOnly being a reserved word in Php 8.1 causes the page to throw a compilation error (there is apparently an exception in 8.1 which allows the term to still be used as Function Name, but not as a Constant).

A ) GitHub listed a modification (changing the constant to "ReadOnlyProperty") which is included in the most recent fileset. I downloaded the current fileset and swapped it for that in the existing plugin code and that error went away.

B ) There were still numerous deprecated warnings regarding Serialize and Unserialize. These were easily tracked down, modifying those classes by changing method names from serialize to __serialize and unserialize to __unserialize, then removing the "implements Serialize" and "implements Unserialize" from the class declarations.

C ) XmlDriver and YamlDriver both had methods which did not match the formats of their class "Extending" method declarations, so removing the "string" clarification for last input variable made them match.

D ) There was an errors in /plugins/hikashoppayment/authorizejs/lib/net/authorize/util/ANetSensitiveFields.php where null values were being supplied to foreach statements, which I patched by changing

foreach($sensitiveTags as $sensitiveTag)

foreach($sensitiveTags ?? [] as $sensitiveTag)

I'm also interested in testing this out and sent an email.

MonkeyT12 - were your changes to the current production or beta?

Thanks. I just tried a beta couple of different ways with PHP 8.0, and so far, so good.

I'll monitor it over the weekend to see how it goes.

I sent in a message. Would have done so sooner, but its been a crazy few days.

MonkeyT12 made the modifications directly in the lib of the current plugin.