Help: eProcessing Network Questions - Using Authorize.net AIM Module

Hi,
I've followed the instructions in this thread, but got a bit lost since there now seems to be more references to the Authorize.net Web site in the authorizenet_aim.php code now.

I assume I need to adjust the following code:

Code:

---

// set URL
    $url = 'https://secure.authorize.net/gateway/transact.dll';
    if (defined('AUTHORIZENET_DEVELOPER_MODE')) {
      if (AUTHORIZENET_DEVELOPER_MODE == 'on') $url = 'https://test.authorize.net/gateway/transact.dll';
      if (AUTHORIZENET_DEVELOPER_MODE == 'echo' || MODULE_PAYMENT_AUTHORIZENET_AIM_DEBUGGING == 'echo') $url = 'https://developer.authorize.net/param_dump.asp';
      if (AUTHORIZENET_DEVELOPER_MODE == 'certify') $url = 'https://certification.authorize.net/gateway/transact.dll';
    }
    if (MODULE_PAYMENT_AUTHORIZENET_AIM_DEBUGGING == 'echo') $url = 'https://developer.authorize.net/param_dump.asp';

---

So, I'm planning on using the following as suggested in the post (originating in 2007) above.

Quote:

---

The production url is:
https://www.eprocessingnetwork.com/cgi-bin/an/order.pl

The url to include in the 2 developer mode sections is:
https://www.eprocessingnetwork.com/c...ct/transact.pl

---

So, there are five references to authorize.net Web sites in the current PHP page code as noted above, but the post only references three URLs, so I'm missing two of the needed URLs.

Any suggestions?

Thanks in advance.

- Running Zen Cart 1.3.8a
- This is a new store, without any previous CC processing working yet
- No add ons yet
- I've been customizing a theme a bit
- URL is https://shop.grayguns.com

Of the lines you posted, the ONLY line you need to change is this one:

Code:

---

    $url = 'https://secure.authorize.net/gateway/transact.dll';

---

All the others are for Zen Cart Programmer use only.

If you want to do your own testing against their developer server, just change the $url value to their developer server while you're doing developing. For the live store, ONLY use the live URL; you don't need developer options on a live store.

Credit card processing is set up with eProcessing Network and I've asked them to ensure everything is OK on their end. There still may be a problem on their end, but I'm trying to narrow down the issue.

I tried the emulation route for eProcessing Network using AutorizeNet. Changed the one line of code in authorizenet_aim.php at line 490 to...

Code:

---

https://www.eprocessingnetwork.com/cgi-bin/an/order.pl

---

That did not work, I kept getting the error ...

Quote:

---

Your credit card could not be authorized for this reason. Please correct the information and try again or contact us for further assistance.

---

I get two e-mails after the transaction is complete...

Quote:

---

Response Code: 1|1|1|This transaction has been approved.|APPROVED 123956|AVS
Match 9 Digit Zip and Address
(X)|20091027093118-05971-284567|TEST-1-whw74v|Test Product (qty: 1)
|0.50|CC|AUTH_ONLY|1|Steve|// REMOVED //|United
States|860-752-6352||steve.mcgough######################|Steve|// REMOVED //|United
States|0.00|0|0.25|FALSE|Oct-27-2009
09:31:31|00764C5A5D2158BE5350F09525D57E62|P|Date="October 27, 2009, 9:31
am"|IP="70.188.163.47"|Session="8bu4ei1fq90b96lh909fprbfl7"|ip_addr="174.143.11. 196".
Response Text:

Sending to Authorizenet: Array
(
[x_login] => *******
[x_tran_key] => *******
[x_relay_response] => FALSE
[x_delim_data] => TRUE
[x_delim_char] => |
[x_encap_char] => *
[x_version] => 3.1
[x_type] => AUTH_ONLY
[x_method] => CC
[x_amount] => 0.50
[x_currency_code] => USD
[x_card_num] => XXXXXXXXXXXXX0027
[x_exp_date] => 0112
[x_card_code] => ****
[x_email_customer] => TRUE
[x_email_merchant] => TRUE
[x_cust_id] => 1
[x_invoice_num] => TEST-1-whw74v
[x_first_name] => Steve
[x_last_name] => // REMOVED //
[x_company] =>
[x_address] => // REMOVED //
[x_city] => // REMOVED //
[x_state] => Connecticut
[x_zip] => // REMOVED //
[x_country] => United States
[x_phone] => // REMOVED //
[x_email] =>// REMOVED //
[x_ship_to_first_name] => Steve
[x_ship_to_last_name] => // REMOVED //
[x_ship_to_address] => // REMOVED //
[x_ship_to_city] => // REMOVED //
[x_ship_to_state] => Connecticut
[x_ship_to_zip] => // REMOVED //
[x_ship_to_country] => United States
[x_description] => Test Product (qty: 1)
[x_recurring_billing] => NO
[x_customer_ip] => 70.188.163.47
[x_po_num] => Oct-27-2009 09:31:31
[x_freight] => 0.25
[x_tax_exempt] => FALSE
[x_tax] => 0.00
[x_duty] => 0
[Date] => October 27, 2009, 9:31 am
[IP] => 70.188.163.47
[Session] => 8bu4ei1fq90b96lh909fprbfl7
[x_test_request] => TRUE
[url] => https://www.eprocessingnetwork.com/cgi-bin/an/order.pl
)


Results Received back from Authorizenet: Array
(
[0] => Response from gateway
[1] => 1|1|1|This transaction has been approved.|APPROVED 123956|AVS
Match 9 Digit Zip and Address
(X)|20091027093118-05971-284567|TEST-1-whw74v|Test Product (qty: 1)
|0.50|CC|AUTH_ONLY|1|Steve|// REMOVED //|United
States|0.00|0|0.25|FALSE|Oct-27-2009
09:31:31|00764C5A5D2158BE5350F09525D57E62|P|Date="October 27, 2009, 9:31
am"|IP="70.188.163.47"|Session="8bu4ei1fq90b96lh909fprbfl7"|ip_addr="174.143.11. 196"
[Expected-MD5-Hash] => AAC57C7EAE2635047B37759A0C2E052E
[HashMatchStatus] => PASS
)


CURL communication info: Array
(
[url] => https://www.eprocessingnetwork.com/cgi-bin/an/order.pl
[content_type] => text/html
[http_code] => 200
[header_size] => 166
[request_size] => 178
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 4.505676
[namelookup_time] => 0.033813
[connect_time] => 0.043443
[pretransfer_time] => 0.126134
[size_upload] => 1029
[size_download] => 559
[speed_download] => 124
[speed_upload] => 228
[download_content_length] => 0
[upload_content_length] => 1029
[starttransfer_time] => 0.139127
[redirect_time] => 0
)


RAW data received:
1|1|1|This transaction has been approved.|APPROVED 123956|AVS Match 9 Digit
Zip and Address (X)|20091027093118-05971-284567|TEST-1-whw74v|Test Product
(qty: 1) |0.50|CC|AUTH_ONLY|1|Steve|// REMOVED //|Connecticut|06096|United
States|0.00|0|0.25|FALSE|Oct-27-2009
09:31:31|00764C5A5D2158BE5350F09525D57E62|P|Date="October 27, 2009, 9:31
am"|IP="// REMOVED //"|Session="8bu4ei1fq90b96lh909fprbfl7"|ip_addr="// REMOVED //"|

---

And the second e-mail says the transaction is complete...

Quote:

---

This message is to confirm that an order has been placed with // REMOVED //.

If you suspect that this order has been placed fraudulently, please contact // REMOVED //. Please include the body of this message in any correspondence to // REMOVED // regarding this order.

Please do not reply to this message. This is simply a courtesy confirmation for your records and security.

Order information is as follows:

Description: Test Product (qty: 1)

Amount: $0.50

Billing Info
// REMOVED //
E-Mail:// REMOVED //

Shipping Info
// REMOVED //

Approval Code: APPROVED 123956

---

I'm waiting to hear back from eProcessing Network, but they are suggesting that we use their own module here..

http://www.zen-cart.com/index.php?main_page=product_contrib_info&cPath=40_48&products_id=1151

I installed that module and tested.

I set the Enable eProcessingNetwork To Collect CC# to FALSE since that was the only way I could even get it to show input fields for the credit card information.

I've got the correct Login ID and Restrict Key in there.

I tried using the test account of 4111111111111111 with any Exp Date (no mention of CVV) and when I get to the final step and hit the confirm button, I am returned back to Step 2.

No e-mails come through.

I also tried using a good credit card - same result.

Could the problem be on the shipping side and how the zones are set up? Trying to ship to the USA only for a flat rate.

UPDATE

OK, for those of you who are trying to set up eProcessing Network using the AuthorizeNet emulation, the issue may be the new version of authorizenet_aim.php file.

To be fair, I'm thinking the new authorizenet_aim.php file is just fine, but if you try to use it for eProcessing Network, in version 1.3.8a of Zen Cart, it will probably not work.

I installed a fresh version of 1.3.7.1 and patched it. Then I noted the clear differences between the admin set up comparing the two .php files from the two versions of ZC.

I tested my processing in 1.3.7.1 and it worked.

I took the authorizenet_aim.php file from 1.3.7.1 and used that in place of the version that was in 1.3.8a. I changed the URL to hit https://www.eprocessingnetwork.com/cgi-bin/an/order.pl instead of the authorizenet URL and the processing worked.

Important Question
Have I messed anything up using the old file from 1.3.7.1?

I did get it to work, but I'm not sure if there is something that I have missed - that could cause a security issue so this needs to be checked and I'd appreciate it if someone would provide me a "yes that will work" or "no, don't do that" answer.

Here was my process...

Testing

• Installed a second implementation of Zen Cart at a new URL, but installed version 1.3.7.1, not the new 1.3.8a version
• Went into /includes/modules/payment and updated line 380 of authorizenet_aim.php to reference the following URL - https://www.eprocessingnetwork.com/cgi-bin/an/order.pl - instead of the authorizenet URL.
• Accessed the admin section of Zen Cart, went to Modules > Payment and updated the Authorize.net (AIM) payment module to include the correct Login ID and Transaction Key (used the Restrict Key).

Note: At this point it was clear the options in the right sidebar for the Authorize.net (AIM) payment module for version 1.3.7.1 of Zen Cart was quite different than 1.3.8a. As an example, there was no HASH5 reference.

• I created a test product and was able to successfully get an authorization. I did not get the "Your credit card could not be authorized for this reason. Please correct the information and try again or contact us for further assistance." error.

Work Around for 1.3.8a

• I took the authorizenet_aim.php file that was used in the 1.3.7.1 version of Zen Cart (the old version I modified above) and used that file to replace the new file that is in Zen Cart 1.3.8a. Processing worked correctly.

Questions

• Is what I did OK to do?
• I think there are other authorizenet PHP files in other folders. Should those also be used to replace their 1.3.8a versions?

Cheers

Using the older version simply loses all the bugfixes and improvements offered in the newer version.
I think what you're doing is overkill.
All you needed to do was change the URL and comment out the hash-protection logic, and maybe change the field delimiters.

Quote:

---

Originally Posted by DrByte

Using the older version simply loses all the bugfixes and improvements offered in the newer version.
I think what you're doing is overkill.
All you needed to do was change the URL and comment out the hash-protection logic, and maybe change the field delimiters.

---

I changed the URL and spent quite a bit of time with eProcessing Network trying to get it to work. They said they were noting a "slight" trend and asked if I could try the previous version.

What it comes down to is that it was not working by just changing the URL. It's working now. I am concerned primarily about security.

Can you provide information on how to comment out the hash-protection logic (which lines where) and change field delimiters? I'm not familiar how to do that.

I'm willing to work on this - and as noted - document my solutions and process.

Turning off the hash-evaluation: http://www.zen-cart.com/forum/showpo...93&postcount=6

Delimiter: http://www.zen-cart.com/forum/showpo...73&postcount=2

I am using zencart 1.3.8a and I am having a similar problem with the eProcessingNetwork module. My Host control panel gives me the option to switch between PHP 4 and 5. Whenever I try to use PHP version 5, the module always gives an error msg and returns me to Step 2 of the checkout. I always get the same error message that only appears in the URL:

https:// x-cream.net/index.php?main_page=checkout_payment&payment_error=eProcessingNetwork&error=The+ credit+card+number+starting+with++was+not+entered+correctly%2C+or+we+do+not+acce pt+that+kind+of+card.+Please+try+again+or+use+another+credit+card.

I don't think the transaction is ever leaving zencart. I believe that the actual values of the form are being lost somewhere, but I can't figure out where. If you look closely at the URL you will notice that the actual credit card number is missing.

There are few PHP options that I can change in my control panel but I'm not a Unix person so I have no idea what I'm doing. All I know for sure is that when I switch to PHP 4 it works fine. I also know that it can work fine with PHP 5 because my old host server is running PHP 5 and it works. This has something to do with the PHP 5 configuration on my new host server. But I'm clueless. Please help! :dontgetit

Oh, and the reason I need PHP 5 is because I've installed an affilate program that won't work on PHP 4.

I solved my own problem! :clap: It turns out that there was a setting in my php.ini file that was causing all the trouble. Set

register_long_arrays = On

By default my host server had this configured to be Off. This was preventing any of the values from the variables in the eProcessingNetwork module to submitted when moving from Step 2 to Step 3. This was generating an error and causing the script to simply return to Step 2. I did not have this problem when I configured my apache control panel to php 4. But I need to use other applications that require php 5. My guess is that this is not something that can be configured in PHP 4.

I think this might help a few people trying to use the official eProcessingNetwork module v1.01.
BTW: I am running zencart 1.3.8a

Quote:

---

Originally Posted by merclord

I solved my own problem! :clap: It turns out that there was a setting in my php.ini file that was causing all the trouble. Set

register_long_arrays = On

By default my host server had this configured to be Off. This was preventing any of the values from the variables in the eProcessingNetwork module to submitted when moving from Step 2 to Step 3. This was generating an error and causing the script to simply return to Step 2. I did not have this problem when I configured my apache control panel to php 4. But I need to use other applications that require php 5. My guess is that this is not something that can be configured in PHP 4.

I think this might help a few people trying to use the official eProcessingNetwork module v1.01.
BTW: I am running zencart 1.3.8a

---

Okay, so that means that your module is using the $HTTP_GET_VARS and/or $HTT_POST_VARS array variables for handling GET and POST data.
PHP 5 has deprecated those variables, and they're not supported in upcoming PHP 6.
You'll want to change the code to use $_GET instead of $HTTP_GET_VARS and $_POST instead of $HTTP_POST_VARS (similar with $HTTP_REQUEST_VARS and $HTTP_SERVER_VARS if you have them), if you want the code to be compatible moving forward.

Ref: http://www.php.net/manual/en/ini.cor...er-long-arrays

Also, when youre logged into your eProcessing Network account:

In "Processing Control" uncheck ALL "Disabled Integrations". After hours of not being able to figure out why I got the "Credit Card cannot be processed..." error message, I disabled these settings and it worked!

I'm still learning this package so please be nice. I think I'm making a very simple mistake with getting this configured.

hopefully a simple thing.


I made the url change per the ePN webpage. That was the only modification I made to the authorizenet_aim.php code.

For the loginid, I used my ePN account number
For the transaction key, I put in the RestrictKey from ePN

If I put the RestrictKey value in for the MD5 hash, my transaction is declined using the 5424000000000015 as the CC number.

If I leave the MD5 has blank, I get a hash error - as one would expect - and the transaction is declined.

What is supposed to go in that field? I'm sure I'm just missing something simple.

While I've no interest in using eProcessing, if you're trying to retrofit the AIM module to work with it, you'll have to leave the MD5 Hash field blank, since that only works with Authorize.net. And you'll need to use Zen Cart v1.3.9.

Thanks. Found their module. Their website didn't mention it but did mention the authorize.net emulation. I'll give their module a shot.