idealecigs Posted December 5, 2013 Share Posted December 5, 2013 *** Errors with validation when configuring NMI and Authorize.net AIM module *** I need help with getting my Prestashop working with the Authorize.net AIM module. I have NMI as my merchant gateway and they use an emulator so I can use the Authorize.net AIM module. Its all installed and URLS were changed to NMI properly but I can't see to get ANY card to go through. NMI Integration specialists couldn't figure it out today and, of course, redirected me back to Prestashop and said the issue was not on their end. I just need someone to work with me or help me out so I can get things up and running. The error i am stuck on now is when I try to process card and click Validate from shopping cart, I receive this error: The ccexp field is required authorize aim ... What could be the issue here? Do you think its an issue with Authorize.net module and my prestashop version? I am using 1.5.6. I will attach my validation.php if you wish to look over it. Any help would be greatly appreciated. Derek Carlson validation.php Link to comment Share on other sites More sharing options...
Dh42 Posted December 5, 2013 Share Posted December 5, 2013 If you want, pm me backoffice access to your shop, ftp access, and the test card numbers they gave you to use and I can take a look at it. Link to comment Share on other sites More sharing options...
VapeCrushers Posted December 12, 2013 Share Posted December 12, 2013 Any movement on this? I am having the exact same issue with the same provider.... Link to comment Share on other sites More sharing options...
VapeCrushers Posted December 12, 2013 Share Posted December 12, 2013 This script is badly broken. I spoke with the gateway and this was their response. We see the X_Exp_date as 122. The Exp date used was 12/2015. They have included a fix that was posted by a Prestashop developer. so it's dropping the last 3 digits of they year and putting "2" instead of "15". Any ideas?? Link to comment Share on other sites More sharing options...
Dh42 Posted December 12, 2013 Share Posted December 12, 2013 Actually their gateway is not complaint. They are using a different date variable than auth.net uses. Link to comment Share on other sites More sharing options...
VapeCrushers Posted December 12, 2013 Share Posted December 12, 2013 Ok, so what did you do? Just use a different merchant provider? It seems like NMI could easily fix this one.... Presta modules can be written to pass a simple date code in any format..... Link to comment Share on other sites More sharing options...
idealecigs Posted December 12, 2013 Author Share Posted December 12, 2013 Hey everyone.. i fixed my issue with this by simply purchasing a Authorize.net Module. The one provided in the Prestashop setup is badly broken and shouldn't be used. I spoke with support at NMI and they sent it to their support and couldn't fix it. They said it was a Prestashop issue.. This was true since I purchased a Authorize.net module and all is good now. I purchased mine for $49.00 from ModuleBazaar and it worked like a charm. They also have great support if you need to make any changes to the module. Wish there was an easier and cheaper fix but there isn't.. Trust me.. lol.. well worth the 49 bucks though.. Here is the link to their product: http://www.modulebazaar.com/en/authorize-net.html Feel free to write me or respond to this thread and I would be happy to help. I feel soon I will be an expert of Prestashop 1.5 tweaking since I have fixed numerous issues myself besides this one.. Good luck to everyone.. Derek Link to comment Share on other sites More sharing options...
idealecigs Posted December 12, 2013 Author Share Posted December 12, 2013 by the way, any Authorize.net paid module should work.. I have tried all FREE ones with no success.. There are a few out there but this one was the cheapest to get up and running smoothly.. Hey dh42, why have you not responded to any of my messages? check your mail buddy Link to comment Share on other sites More sharing options...
Dh42 Posted December 12, 2013 Share Posted December 12, 2013 It has nothing to do with Prestashops module. The module was written to work with authorize.net, not NMI. They should develop and release a module. For your problem, can you try printing out the x_exp_date variable and see what you get as a value. Link to comment Share on other sites More sharing options...
Dh42 Posted December 12, 2013 Share Posted December 12, 2013 Btw, I have dozens of clients that are running the auth.net module with auth.net, not having any issues. Link to comment Share on other sites More sharing options...
idealecigs Posted December 12, 2013 Author Share Posted December 12, 2013 DH42, please don't discourage users about this issue.. NMI developed their gateway to exact specifications of Authorize.net module. The one provided with this prestashop version is corrupt. There is no fix besides purchasing a new updated module from a 3rd party. Anyone who has questions or needs help just direct all questions to me and I promise not give you the "run around".. lol I have learned so much in this whole process and have been successful at coding PHP and TPL files.. Good luck to everyone using Prestashop 1.5. I enjoy the interface very much and so do all my customers who buy from my shop. Link to comment Share on other sites More sharing options...
Dh42 Posted December 12, 2013 Share Posted December 12, 2013 The issue is not with the module, I have set up the auth.net module on almost 100 sites. The issue is with the gateway. As a FYI, the auth.net module was written by auth.net, not Prestashop. So you might let them know they wrote the module wrong. Link to comment Share on other sites More sharing options...
idealecigs Posted December 12, 2013 Author Share Posted December 12, 2013 DH42, you are not helping anyone.. you just keep saying the same things on here.. I am actually helping Prestashop users and not telling them what they need to do to correct these issues.. I understand auth.net module was written by auth.net but you are not telling anyone how to fix this.. for NMI integration, users need an updated module that works with NMI gateway.. Dh42, how much experience do you have with NMI gateway integration with Auth,net module? It doesn't matter if you have worked on 5000 sites unless you have corrected the EXACT issue these users are having... Link to comment Share on other sites More sharing options...
Dh42 Posted December 12, 2013 Share Posted December 12, 2013 Watch me help someone. If you want to send me access to your ftp and to your backoffice, I will fix the auth.net module to work with NMI and make a repository for it on github so people can have the fix for the future. And clam down. Link to comment Share on other sites More sharing options...
idealecigs Posted December 12, 2013 Author Share Posted December 12, 2013 i'm calm.. lol.. just trying to give you advice on how to actually help users.. without all the politics... ha Link to comment Share on other sites More sharing options...
Dh42 Posted December 12, 2013 Share Posted December 12, 2013 I wasn't giving politics I was letting people that find the thread in the future know where the actual problem lies. The problem is because they are not using the same date variable that auth.net uses. There is no issue with the auth.net module, the issue is with using the auth.net module for a gateway that it was not designed to use. Link to comment Share on other sites More sharing options...
VapeCrushers Posted December 12, 2013 Share Posted December 12, 2013 I appreciate all your help! The Validate.php file, is that the only culprit, or are there other files that need to be modified? the code changes should be the same for every site that uses NMI, correct? NMI said to change this: $_POST['x_exp_date_m'].$_POST['x_exp_date_y'] To This: $_POST['x_exp_date'] = str_pad($_POST['x_exp_date_m'],2,'0',STR_PAD_LEFT).$_POST['x_exp_date_y'] However, the left side of the month is not the problem, it is the right side of the Year. The results were: 2013/12/12 19:09:27 (0.157s) < 3|0|122|The ccexp field is required REFID:5214869||P|0|20||27.00| CC|auth_capture||erik|swanson||6041 St Clair Ct |||93063||||||||||||||||||242A3CC7511878ED835E1339468AD9F0|P| So I don't understand why would you need access to the back end of the site. The whole issue centers on how the Validate.php hands off the date variable Link to comment Share on other sites More sharing options...
Dh42 Posted December 12, 2013 Share Posted December 12, 2013 I would need ftp access at the least, and a test card number. The reason being is that the docs for the NMI api are pretty sparse. The first thing I was going to do was print the variable for the exp and see what is output. From what I have read though, the exp date needs to be sent through in another variable name. Link to comment Share on other sites More sharing options...
Dh42 Posted December 12, 2013 Share Posted December 12, 2013 Ok, so the fix is pretty simple. it is actually sadly enough a bug I introduced to the module a few weeks back. If you open up the module/authorizeaim/authorizeaim.tpl file and delete the red line and replace it with the green line in this pull request, it will fix the modules date issue. https://github.com/PrestaShop/PrestaShop-modules/pull/157/files Link to comment Share on other sites More sharing options...
Dh42 Posted December 16, 2013 Share Posted December 16, 2013 Here is a complete packaged NMI module if anyone here now or in the future is still interested. NMI Payment module for Prestashop Link to comment Share on other sites More sharing options...
Recommended Posts