Payment Method - Authorize Accept JS

-- HikaShop version -- : 4.0.2
-- Joomla version -- : 3.9.3
-- PHP version -- : 7.1.26
-- Browser(s) name and version -- : Firefox 65.0.2

Hello,

We purchased the Authorize Accept JS plugin last night and wanted to try it.
There seems to be two issues:
1) a misspelled file name in the package, and
2) we are unable to Finish/Complete Checkout due to a dead button with no action on a click.

We've been running successfully with the old Authorize.net "AIM" plugin on this test site as well as on production. We are even using the latest development release of this plugin (authorize.zip) that accomodates the new SHA512 security key.

But back to the Accept JS payment method that we now want to use....

We noticed an issue right away upon installation. We get a warning about a non-existent file:

Hi Jerome,

In your latest build -- in the media folder -- the filename is still misspelled. It is "authorisejs.js", but it should be "authorizejs.js" (with a "z").

In addition, I have modified my own file with the following:

Replace

console.log(resp.messages.message[i].code + ": " + resp.messages.message[i].text);

console.log(resp.messages.message[i].code + ": " + resp.messages.message[i].text);
alert( resp.messages.message[i].text );

Please add a version number to your zip file in future. I had downloaded this months ago. Finally ready to install, I saw that the file name was the same so I used the one I already had. I had to start over. If there had been some indication of change, I would have made sure I used the current one. Thanks!

You’re welcome!

Do you have more detailed instructions for installation somewhere like you do for the older SIM payment method? It would be helpful for others. I had never used the Public Key for SIM and so I thought that the Signature Key was the same thing but I kept getting the error message that meant I needed a new Transaction Key. I even called Authorize and the tech thought I was doing it right (she was wrong). After going into the Authorize.net’s developer area, I discovered that they are not the same. Once I generated a Public Key, everything worked. Don’t even need the Signature Key.

Another issue: I used the same Return URL in Authorize Accept JS as I did for the SIM version. It brings up a 404 Page Not Found error. I left it blank and it gives the proper message so I may just leave it alone. But the message is so tiny, I prefer the Return URL but I don’t know why it doesn’t work. I tried the URL without the domain at front (which works on SIM payment method); and, I tried the URL with the MyDomain.com/ in front. Neither work. I tested the Cancel URL too and it didn’t work for me either. Not a big deal. I’m embarrassed to say I spent 4 hours trying to figure all this out with a few mistakes on my end — so I’m not in a hurry to revisit this! It usually only takes me 15-30 minutes to install a payment plugin when there are instructions.

Thanks for your help!

One other question: Which version of Accept.js did you use? The PCI-DSS SAQ A-EP solution or the PCI-DSS SAQ A compliant way. I need to be able to tell my client when she goes through her PCI compliance process.

Thank you for your answers! Yep, that’s the developer page I found that clued me in about the public key. I will contact HikaShop regarding the Return URL.

I'm curious what you might have found out about the return URL. I also placed my preferred return url in and the flow does not return to the desired url after finish/payment. What it seems to be doing is that it stays on category/checkout/confirm and I just receive a blank page. Then, I had the same result as you when leaving the return url blank, it also stays on category/checkout/confirm but this time, it delivers a full template page but just populates text simply stating Thank You for your purchase.

Of course a dedicate order confirmation page or customer account page is what I would like the user to return to after purchase. So I'm wondering if you were able to find something out on this. Thanks!

Thanks Nicolas. So I do get a fatal error which is this:
Fatal error: require_once(): Failed opening required '(server)/httpdocs/libraries/joomla/document/html/renderer/head.php' (include_path='.:/opt/alt/php74/usr/share/pear') in /(server)/httpdocs/templates/(templatename)/error.php on line 28.

Line 28 of error.php is this:
require_once(JPATH_LIBRARIES.'/joomla/document/html/renderer/head.php');

From what I can tell, there is no such document/html/renderer/head.php inside /httpdocs/libraries/joomla/.

Could this be the issue?

For what it's worth, I do have success with Accept JS without a url in Return URL setting and I can place more descriptive text to the customer after purchase via the language file. But I would like to have a more detailed post purchase landing page.

I appreciate your help and providing a plugin to use a supported API for Authorize.Net! We just purchased this and set it up on our site, but I get the “Your card token has expired” error when checking out.

-- HikaShop version -- : 4.3.0
-- Joomla version -- : 3.9.18
-- PHP version -- : 7.2
-- Browser(s) name and version -- : Google Chrome 83.0.4103.61
-- HTTPS/SSL - Yes
-- Payment form in payment listing - Yes
-- "Legacy" checkout - Yes this was enabled

After I disabled legacy options for add to cart and checkout it worked! I'm sorry I missed that part on the product page. Thank you again for your assistance.

After putting this plugin in place payments are being processed, but we aren't receiving the same payment notification emails and the order numbers and details are not in the auto-receipt from Authorize. The built-in plugin that uses depreciated API methods has the options for "Allow payment notifications from Authorize.net" and "Send details of the order" in its settings. Would these be the settings that allowed for this information? Is there a way to implement these same settings in the supported Accept.JS plugin?

I noticed this right away also and mentioned it (off forum) as well. It is useful to have all info on the notifications but I can get by without it. Although I would like to see it included in an update.

From what I recall on testing it a couple weeks ago, the Send Details of the Order setting on the deprecated api only sends the line item info and doesn't control the customer billing or customer shipping info.