Auth.net SIM Error 99 Cannot be accepted

[mc12345678]

For most likely correction see: http://www.zen-cart.com/showthread.p..._currency_code

[RixStix]

TNX mc12345678, I thought I had seen something recent but the search function didn't find it for me. Could have been out of frustration.

Making that change, gets one step further in the process, then receive the following screen (WITHOUT ANY DELAY). I tried commenting out the currency (lines 343/381) and also adding the code to line 385 (independently of each other). Results are identical.

The setting to REQUIRE CVV is set within the zencart SIM setup, though is not required when actually entering payment information.

An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

This transaction has been approved.
It is advisable for you to contact the merchant to verify that you will receive the product or service.

Authorize.Net Merchant,

Your script timed out while we were trying to post transaction results to it.
Transaction ID: 0
Transaction Result: This transaction has been approved.

The following message was displayed to the customer:

No order is generated by zencart.

[RixStix]

The setting to REQUIRE CVV is set within the zencart SIM setup, though is not required when actually entering payment information.

This part resolved.
Requires additional configuration within the Auth.net account to allow VIEW, EDIT, and REQUIRE card code.

Still script timeout error.

In the meantime, work on css to make the auth.net SIM page have the same, or at least similar, appearance as our zencart pages.

[mc12345678]

What about the results of the curltester code found in the extras folder, extras/curltester.php?

Also, has the SSL3 been commented out as posted here: http://www.zen-cart.com/showthread.p...yment-security

Recommend the curltest first, the SSL change and then the curltest again after that... Then based on all reports to be able to offer a suggestion of further diagnosis.

[RixStix]

What about the results of the curltester code found in the extras folder, extras/curltester.php?

Also, has the SSL3 been commented out as posted here: http://www.zen-cart.com/showthread.p...yment-security

Recommend the curltest first, the SSL change and then the curltest again after that... Then based on all reports to be able to offer a suggestion of further diagnosis.

CurlTest => GOOD for both Auth.net production and sandbox servers.

No SSLv3 to comment in Auth.net SIM

Script timeout seems strange to me since the response is instant. I would have expected some delay in page update before receiving the auth.net white screen.

Next ???

Not a fan of SIM but also not a fan of SAQ-D for AIM either. SAQ A-ep is much more palatable for PayPal and SIM.

[mc12345678]

CurlTest => GOOD for both Auth.net production and sandbox servers.

No SSLv3 to comment in Auth.net SIM

Script timeout seems strange to me since the response is instant. I would have expected some delay in page update before receiving the auth.net white screen.

Next ???

Not a fan of SIM but also not a fan of SAQ-D for AIM either. SAQ A-ep is much more palatable for PayPal and SIM.

Okay, so details: has or doesn't have ssl3 to comment out, eh... :)

Made me think though. Sandbox is what is currently setup.. Is there an expectation that sandbox traffic will generate order ids in a cart? I've never actually used authorize.net nor tried to track down sandbox functionality within it, but just wondering if some portion of the communication has been "cut" to support sandbox mode. Afterall, it looks like the other changes have taken hold.

Cleared cache? And are you sure that there are no differences required between using all of the same credentials on two different "sites" using two different methods of processing (SIM/AIM)?

That's about as much as I've got at the moment

[RixStix]

Okay, so details: has or doesn't have ssl3 to comment out, eh... :)

No SSL version checks in SIM

Made me think though. Sandbox is what is currently setup.. Is there an expectation that sandbox traffic will generate order ids in a cart? I've never actually used authorize.net nor tried to track down sandbox functionality within it, but just wondering if some portion of the communication has been "cut" to support sandbox mode. Afterall, it looks like the other changes have taken hold.

From what I remember in the past, orders placed when Auth.net AIM in test mode are generated and stored the same as production.

Cleared cache? And are you sure that there are no differences required between using all of the same credentials on two different "sites" using two different methods of processing (SIM/AIM)?

Zencart setup instructions for AIM and SIM are identical as far as the steps for acquiring the credentials from the Auth.net account. Additional Auth.net SIM setup

• Auth.net SIM setup Response/receipt URL = default/blank
• Auth.net SIM setup Relay Response = blank
• Auth.net SIM setup Silent POST URL = blank

auth.net account set to LIVE. zc sandbox SIM set to test (test CC numbers) This is per zencart Auth.net SIM testing instructions. ZC in test but live auth.net does not required to be in TEST mode.

Once we get the sandbox working then we'll worry about issues that may be caused by a different php version used in our live site.

If I had any idea of what/when/where to look for the script that is giving timeout errors, I'd peek and poke around.

TNX for the suggestions so far.