My message can be disregarded. In my case, I apparently forgot to save changes made to checkout_process.php. I could have saved myself a ton of time had I checked this out sooner, but at least it's working...
Latest News: (loading..)
0
992 replies to this topic
#942
Posted 02 June 2009, 18:52
Has anyone converted orders_trustcommerce.php to work with Auhorize.net?
It allows shop owners to run transactions (preauth / postauth / refund) directly from the orders.php page in osC administration.
[img]http://eric4.com/tc-example.gif[/img]
Regards,
Eric_K
It allows shop owners to run transactions (preauth / postauth / refund) directly from the orders.php page in osC administration.
[img]http://eric4.com/tc-example.gif[/img]
Regards,
Eric_K
#943
Posted 02 June 2009, 20:03
Ok... i am not real smart with this stuff - that being said - I installed the AIM module... ran some test transactions with authorize.net in test mode and the cart in test mode - working fine. So took it out of test mode on both and put in the specified test cc numbers that are supposed to decline - the don't... Get order processed... if I put in the 4222222222222 or a bad expiry it declines.
Additionally - none of the orders are showing up in the authorize.net reports... I followed all the instructions, and am very confused about whether this thing is working properly or not - it looks like it is - but when i check for transactions at authorize.net there is nothing there...
Any help greatly appreciated.
Additionally - none of the orders are showing up in the authorize.net reports... I followed all the instructions, and am very confused about whether this thing is working properly or not - it looks like it is - but when i check for transactions at authorize.net there is nothing there...
Any help greatly appreciated.
#944
Posted 03 June 2009, 23:16
Where do we change the Payment Method text on the invoice? It says: Authorize.net AIM. We want it to say: Credit Card because Authorize.net AIM means nothing to the customer. This contribution keeps the customer on our site so they have no idea who the card processor even is. No sense risking confusing them...
I thought it was in catalog\includes\languages\english\authorizenet_aim.php but evidently not. I changed it there and it didn't appear to affect anything on the invoice...
I thought it was in catalog\includes\languages\english\authorizenet_aim.php but evidently not. I changed it there and it didn't appear to affect anything on the invoice...
#945
Posted 04 June 2009, 05:04
kru, on Jun 3 2009, 06:16 PM, said:
Where do we change the Payment Method text on the invoice? It says: Authorize.net AIM. We want it to say: Credit Card because Authorize.net AIM means nothing to the customer. This contribution keeps the customer on our site so they have no idea who the card processor even is. No sense risking confusing them...
I thought it was in catalog\includes\languages\english\authorizenet_aim.php but evidently not. I changed it there and it didn't appear to affect anything on the invoice...
I thought it was in catalog\includes\languages\english\authorizenet_aim.php but evidently not. I changed it there and it didn't appear to affect anything on the invoice...
Nevermind. Didn't realize it was storing that Payment Method in the orders table. Changing this in catalog\includes\languages\english\authorizenet_aim.php DOES in fact change it on any new invoices created since the change. A quick update of the orders table took care of the first few stragglers...
The only downside... It changes it on the Admin panel under the Payments module listing. So we changed our description to Credit Card Online so as to differentiate, as well as report on it. (We'll use a report to go back to Paypal and make them aware of how much money they lost in processing fees as a result of their sneaky strong-arm tactics in trying to get us to upgrade to their Website Payments Pro for $30 per month. Yes, they recently tightened their acceptance rules for payments made through the basic/free gateway which was resulting in a LOT of decline transactions. Of course this problem is remedied if we "upgrade to the Pro version for only $30 per month." Then we can choose our own security settings and make them more relaxed. Nevermind that their default security settings for the basic/free gateway are ridiculously strict now. They're getting too big for their own good, if you ask me. Think they can do whatever they want because they already have us "hooked". Little do they know how easy it is to get an Authorize.net account and add this contribution...)
Yes, that was an official somewhat-off-topic rant...
#946
Posted 10 June 2009, 19:27
Hello,
I have been digging around this Contribution Forum and I just can't seem to find where anybody may have had the same problem I am having.
I have installed the Authorize.net AIM as described. I enable it for testing and when I put in all the info, I get a
Expiry Date Entered is not valid
Can anybody assist me?
Thanks,
Troy
I have been digging around this Contribution Forum and I just can't seem to find where anybody may have had the same problem I am having.
I have installed the Authorize.net AIM as described. I enable it for testing and when I put in all the info, I get a
Expiry Date Entered is not valid
Can anybody assist me?
Thanks,
Troy
#947
Posted 10 June 2009, 19:36
Torg42, on Jun 10 2009, 02:27 PM, said:
Hello,
I have been digging around this Contribution Forum and I just can't seem to find where anybody may have had the same problem I am having.
I have installed the Authorize.net AIM as described. I enable it for testing and when I put in all the info, I get a
Expiry Date Entered is not valid
Can anybody assist me?
Thanks,
Troy
I have been digging around this Contribution Forum and I just can't seem to find where anybody may have had the same problem I am having.
I have installed the Authorize.net AIM as described. I enable it for testing and when I put in all the info, I get a
Expiry Date Entered is not valid
Can anybody assist me?
Thanks,
Troy
Expiration date has to be passed as four digits at all times. So January 2012 would be 0112. If you're leaving off the zero, that's your problem...
#948
Posted 10 June 2009, 19:55
Wow, thanks for the quick response!
I have drop downs for the Month and Year. I hit continue and on the confirmation page it shows up as you say. I hit the confirm order and then I get the error, and I am back at the CC Info page.
Thanks again,
Troy
I have drop downs for the Month and Year. I hit continue and on the confirmation page it shows up as you say. I hit the confirm order and then I get the error, and I am back at the CC Info page.
Thanks again,
Troy
#950
Posted 11 June 2009, 17:49
Torg42, on Jun 11 2009, 12:24 PM, said:
Hello again,
The CC Date works fine for the stock CC payment module. But with the Auth AIM I get the Expiry error. Does that help?
Thanks,
Troy
The CC Date works fine for the stock CC payment module. But with the Auth AIM I get the Expiry error. Does that help?
Thanks,
Troy
I'm not really an expert on this module, as we had it working within 30 minutes of install, so we didn't have any real problems to run down. I am anal enough that I read through this support thread first though. Two suggestions I would have is to make sure your delimiters are set correctly and/or you might want to add error tracking code. If I'm thinking of the right mod (have been researching/implementing several lately), there was a user who posted some code for this quite a few pages back.
Edited by kru, 11 June 2009, 17:49.
#954
Posted 11 June 2009, 19:23
Okay, that didn't help.
I wonder why the Expiration Date works for Stock CC Payment module, but it fails out for the Authorize.net AIM mod. That doesn't make any sence to me.
Maybe something with the Checkout_confirmation.php?
I wonder why the Expiration Date works for Stock CC Payment module, but it fails out for the Authorize.net AIM mod. That doesn't make any sence to me.
Maybe something with the Checkout_confirmation.php?
#956
Posted 20 June 2009, 12:57
Torg42, on Jun 11 2009, 10:22 AM, said:
Okay, I think I get what your taling about with the delimiter bit. I will try to set it to a , instead of a pipe.
Troy
Troy
I was getting the same error. Changed
tep_draw_hidden_field('authorizenet_aim_cc_expires_month', $_POST['authorizenet_aim_expires_month']) .
tep_draw_hidden_field('authorizenet_aim_cc_expires_year', $_POST['authorizenet_aim_expires_year'], -2) .
to
tep_draw_hidden_field('authorizenet_aim_cc_expires_month', $this->cc_expiry_month) .
tep_draw_hidden_field('authorizenet_aim_cc_expires_year', substr($this->cc_expiry_year, -2)) .
around line 180 in modules/payment/authorizenet_aim.php
And that solved the problem.
(Not sure why $_POST['authorizenet_aim_expires_month'] is null at this point in the code whereas $this->cc_expiry_month is not, but that was the case.)
#957
Posted 22 June 2009, 21:11
I was having the "There has been an error processing your credit card. Please try again and if problems persist, please try another payment method." error message with this module as well. After digging through hundreds of threads on this topic I finally was able to get my mod working.
First issue to resolve is to make sure CURL is configured on your hosting provider. To verify contact your host and ask. I was hosted on a windows machine using webhost4life and caused some issues but working with them I was able to resolve it. I also used the "sample php" code on the http://developer.authorize.net/samplecode/ site and put in my user id and API key and was able to rule that issue out. It's generic code that will allow you to run a test and return the error codes from authorize to tell if you are getting values back. If you get a success with that code CURL and your API login credentials are most likely setup correctly.
A couple of things to remember with these modules:
1. If you have a "test" account set up you will want to use the test mode but if you have a real authorize.net account setup with it in "test mode" you will want to run everything in "live" settings mode in the module.
2. Set Transaction version = 3.1 (this is AIM) in the Authorize.net settings
3. Set your Direct Response Delimiter in the Authorize.net settings
Delimited Response: no
Field separator: comma(,)
Field Encapsulation Character: blank
4. Set your response/receipt URLs in your authorize.net settings
https://yourdomian.com/catalog/checkout_confirmation.php (Default Receipt URL)
https://yourdomain.com/catalog/checkout_process.php (Default Relay Response URL)
5. Be careful using these but use a logger on these modules - in my case I was making it to through the OSC shopping cart process only to find that I was not passing the CC info to authorize because of an incorrect </form> tag in the checkout_confirmation.php code. I ended up using the authorizenet_cc_aim.php module as it was the most updated at the time and found this post to be spot on to the issue I was having of not passing the CC data and getting the error sending me back to the payment page - http://forums.oscommerce.com/index.php?sho...t&p=1280555. The post by Jeff Wigal also includes a logger for viewing the info you are passing to authorize and the response you are getting back from them. Again make sure you delete the logged info when you are done testing and delete or comment out the code. There is also a logger for the authorizenet_aim.php by Joshua Morris for the Authorize Net AIM module (GPL) - vger module here http://forums.oscommerce.com/index.php?sho...t&p=1283835
For me changing the checkout_confirmation.php tags worked. I did read through all these posts and followed the advice for setting up the MD5 hash as well. I am now able to run a credit card successfully so I am just trying to pass along what worked for me to others that maybe having the same issue. I am not a developer but these posts were easy enough to follow and test. I would recommend you backup any code that you will be changing and follow the advice of the posters about deleting any files that the loggers create - it's sound advice.
Jon
First issue to resolve is to make sure CURL is configured on your hosting provider. To verify contact your host and ask. I was hosted on a windows machine using webhost4life and caused some issues but working with them I was able to resolve it. I also used the "sample php" code on the http://developer.authorize.net/samplecode/ site and put in my user id and API key and was able to rule that issue out. It's generic code that will allow you to run a test and return the error codes from authorize to tell if you are getting values back. If you get a success with that code CURL and your API login credentials are most likely setup correctly.
A couple of things to remember with these modules:
1. If you have a "test" account set up you will want to use the test mode but if you have a real authorize.net account setup with it in "test mode" you will want to run everything in "live" settings mode in the module.
2. Set Transaction version = 3.1 (this is AIM) in the Authorize.net settings
3. Set your Direct Response Delimiter in the Authorize.net settings
Delimited Response: no
Field separator: comma(,)
Field Encapsulation Character: blank
4. Set your response/receipt URLs in your authorize.net settings
https://yourdomian.com/catalog/checkout_confirmation.php (Default Receipt URL)
https://yourdomain.com/catalog/checkout_process.php (Default Relay Response URL)
5. Be careful using these but use a logger on these modules - in my case I was making it to through the OSC shopping cart process only to find that I was not passing the CC info to authorize because of an incorrect </form> tag in the checkout_confirmation.php code. I ended up using the authorizenet_cc_aim.php module as it was the most updated at the time and found this post to be spot on to the issue I was having of not passing the CC data and getting the error sending me back to the payment page - http://forums.oscommerce.com/index.php?sho...t&p=1280555. The post by Jeff Wigal also includes a logger for viewing the info you are passing to authorize and the response you are getting back from them. Again make sure you delete the logged info when you are done testing and delete or comment out the code. There is also a logger for the authorizenet_aim.php by Joshua Morris for the Authorize Net AIM module (GPL) - vger module here http://forums.oscommerce.com/index.php?sho...t&p=1283835
For me changing the checkout_confirmation.php tags worked. I did read through all these posts and followed the advice for setting up the MD5 hash as well. I am now able to run a credit card successfully so I am just trying to pass along what worked for me to others that maybe having the same issue. I am not a developer but these posts were easy enough to follow and test. I would recommend you backup any code that you will be changing and follow the advice of the posters about deleting any files that the loggers create - it's sound advice.
Jon
#958
Posted 24 July 2009, 19:53
Sup peeps, I just have one simple question - With this module, if a credit card gets declined for ANY reason at all - how can that be automatically reflected on the order within the admin. Is there a setting for this in oscommerce rc2a? Can I set up in oscommerce to email declined notifications?
Thanks!
Thanks!
#959
Posted 25 July 2009, 19:53
I'm running osCommerce Online Merchant v2.2 RC2.
I have all my authorize.net information correct.
I downloaded the latest version of Vger's Authorize.net AIM contribution, and just dropped it in my /includes/modules/payment directory, as the contribution page said.
Then, I logged into my admin panel, went to Modules >> Payment, and Activated the Vger's Contribution, and inputted all the correct information.
On the Modules >> Payment page in my admin panel, there are the following errors:
Don't know how to fix that...
Then, on the frontend, when I add an item to my cart and go to checkout, on the checkout_confirmation.php page, it displays near the bottom:
How do I change the MODULE_PAYMENT_.... text to say what I want it to say?
and FINALLY, when I confirm the checkout, it takes me to a blank white page with the following errors:
I changed the credit card owner name for security purposes. But, the order goes through in the Authorize.net account (status: Captured/Pending Settlement). And osCommerce sends a receipt email to the customer. So basically, everything is working, but this last page throws an error, instead of doing what it's supposed to do. How do I fix these small problems?? Has anyone had this problem before?
I could really use some insight here.
PS Thanks Vger's for the contribution! It works, just needs a little tweaking on my end.
I have all my authorize.net information correct.
I downloaded the latest version of Vger's Authorize.net AIM contribution, and just dropped it in my /includes/modules/payment directory, as the contribution page said.
Then, I logged into my admin panel, went to Modules >> Payment, and Activated the Vger's Contribution, and inputted all the correct information.
On the Modules >> Payment page in my admin panel, there are the following errors:
Warning: main(/home/mbbucket/public_html/shop/includes/languages/english/modules/payment/authorizenet_aim.php) [function.main]: failed to open stream: No such file or directory in /home/mbbucket/public_html/shop/admin/modules.php on line 136 Warning: main(/home/mbbucket/public_html/shop/includes/languages/english/modules/payment/authorizenet_aim.php) [function.main]: failed to open stream: No such file or directory in /home/mbbucket/public_html/shop/admin/modules.php on line 136 Warning: main() [function.include]: Failed opening '/home/mbbucket/public_html/shop/includes/languages/english/modules/payment/authorizenet_aim.php' for inclusion (include_path='/usr/lib/php:.:/usr/php4/lib/php:/usr/local/php4/lib/php') in /home/mbbucket/public_html/shop/admin/modules.php on line 136
Don't know how to fix that...
Then, on the frontend, when I add an item to my cart and go to checkout, on the checkout_confirmation.php page, it displays near the bottom:
MODULE_PAYMENT_AUTHORIZENET_AIM_TEXT_CREDIT_CARD_OWNER Owner Name MODULE_PAYMENT_AUTHORIZENET_AIM_TEXT_CREDIT_CARD_TYPE CC type MODULE_PAYMENT_AUTHORIZENET_AIM_TEXT_CREDIT_CARD_NUMBER 1234XXXXXXXX1234 MODULE_PAYMENT_AUTHORIZENET_AIM_TEXT_CREDIT_CARD_EXPIRES 1234 MODULE_PAYMENT_AUTHORIZENET_AIM_TEXT_CVV XXX
How do I change the MODULE_PAYMENT_.... text to say what I want it to say?
and FINALLY, when I confirm the checkout, it takes me to a blank white page with the following errors:
Warning: payment(includes/languages/english/modules/payment/authorizenet_aim.php) [function.payment]: failed to open stream: No such file or directory in/home/mbbucket/public_html/shop/includes/classes/payment.php on line 38 Warning: payment(includes/languages/english/modules/payment/authorizenet_aim.php) [function.payment]: failed to open stream: No such file or directory in/home/mbbucket/public_html/shop/includes/classes/payment.php on line 38 Warning: payment(includes/languages/english/modules/payment/authorizenet_aim.php) [function.payment]: failed to open stream: No such file or directory in/home/mbbucket/public_html/shop/includes/classes/payment.php on line 38 Warning: payment() [function.include]: Failed opening 'includes/languages/english/modules/payment/authorizenet_aim.php' for inclusion (include_path='/usr/lib/php:.:/usr/php4/lib/php:/usr/local/php4/lib/php') in /home/mbbucket/public_html/shop/includes/classes/payment.php on line 38 1054 - Unknown column 'transaction_details' in 'field list' UPDATE orders SET cc_type = 'Visa', cc_owner = 'Credit Card Owner Name', cc_number = 'XXXXXXXXXXXX1234', cc_expires = '1234', transaction_details = 'Transaction ID|2533773056;AVS Response|Address (Street) and five digit ZIP match;Card Code Response|Match' WHERE orders_id = 2 LIMIT 1 [TEP STOP]
I changed the credit card owner name for security purposes. But, the order goes through in the Authorize.net account (status: Captured/Pending Settlement). And osCommerce sends a receipt email to the customer. So basically, everything is working, but this last page throws an error, instead of doing what it's supposed to do. How do I fix these small problems?? Has anyone had this problem before?
I could really use some insight here.
PS Thanks Vger's for the contribution! It works, just needs a little tweaking on my end.
