Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
You could ask for a list of differences, or the php.ini from each server to compare them yourself
I'm also mindful that the presence of any myDebug-xxxx.logs in your /logs/ folder can be helpful in this situation.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
Okay, so checkout_process is aborting. Otherwise the log file would also contain the response details.
When that's happening, the customer is seeing the browser do things. What are they seeing?
Obviously they see the authnet site before they click "Pay", and then later they eventually see something on your site. What's that? And, what are they seeing in-between, even if only for a nanosecond? (Maybe a screen recording might show the URL change a couple times before the screen redirects?)
Is the apache errorlog showing any 406 responses? or any other non-200 responses?
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
- Customer is sent to the Auth.net SIM payment form with their account details pre-populated so that they can input credit card #, exp date and CVV.
- Bottom of page has a "Pay Now" button.
- Click "Pay Now"
- Instantly, a generic auth.net white page with text
- Server log entry appears identical to post#3 above
No links back to the ZC site. Just the sterile, white auth.net page------------------------------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.
The payment is authorized and captured which can be seen within the auth.net account.
The email sent by auth.net to the merchant (me) is
Authorize.Net Merchant,
Your script timed out while we were trying to post transaction results to it.
Transaction ID: 6657207384
Transaction Result: This transaction has been approved.
The following message was displayed to the customer:
------------------------------
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.
------------------------------
Last edited by RixStix; 13 Nov 2014 at 09:52 PM.
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
Below is the screens received in a successful payment made on the test sitestep 1 of 4 shippingstep 2 of 4 payment methodstep 3 of 4 checkout confirmation
redirect to auth.net SIM form for payment details
PAY NOW button on SIM formredirect white screen & mixed content screen (must acknowledge mixed content) using FireFox browserThis page will automatically redirect you back to ChainWeavers.com for your order confirmationdetailsIf you are not redirected within 5 seconds, please click the button below to continueCONTINUE BUTTON.Popup window on top of the above white screen.Security warningAlthough this page is encrypted, the information you have entered is to be sent over an unencripted connection and could easily be read by a third party.Are you sure you want to continue sending this information?CONTINUE CANCELstep 4 of 4 ZC order confirmation screen===============================================
This is the order of screens on a failed payment transaction
- Checkout Step 1 of 4 shipping
- Checkout Step 2 of 4 payment method. Select Credit Card SIM method.
- Checkout Step 3 of 4 checkout confirmation. Confirm.
- Auth.net SIM payment form opens. https://secure.authorize.net/gateway/transact.dll
- Enter valid CC information.
- Click PAY NOW button.
- https://secure.authorize.net/gateway/transact.dll white, auth.net screen with customer message. transaction approved.[/FONT]
- Back button, to auth.net SIM payment form.
- Back button twice, document expired, reload. Checkout Step 3 of 4
Email received from auth.net showing payment details
========== MERCHANT DEFINED =========
securityToken : 573594402454131a474b64313c6596e5
zenid : b03737d35c3d8c4330608929ba6a72d3
==================================
zenid matches the zenid in the Checkout Step 3 of 4 checkout confirmation URL.
Not sure if security token is supposed to match anything.
[x_fp_hash] => sent to auth.net
Auth.net fingerprint troubleshooting generator matches [x_fp_hash] transmitted by ZC[/FONT]
Last edited by RixStix; 13 Nov 2014 at 11:43 PM.
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
Server log successful, test server transaction
Server log failed live server transaction198.241.168.60 - - [13/Nov/2014:14:31:47 -0800] "POST /ZEN153/index.php?main_page=checkout_process&action=confirm HTTP/1.1" 302- "-" "-"
198.241.168.60 - - [13/Nov/2014:14:31:48 -0800] "GET /ZEN153/index.php?main_page=checkout_success&action=confirm&zenid=549a33192447c5a4b58268 c12181d57f HTTP/1.1" 200 1087 "-" "-"
198.241.168.60 - - [13/Nov/2014:11:00:43 -0800] "POST /index.php?main_page=checkout_process&action=confirm HTTP/1.1" 302 208 "-" "-"
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
Looked at the SIM_mydebug files a bit closer and found that the data being sent to auth.net differs between the test and live site if that makes any difference.
The live site data sent to auth.net contains the zenID.
The test site data sent to auth.net does not contain the zenID
test site SIM debug
Sent TO auth.net
live site SIM debug[x_relay_URL] => http:\\chainweavers.TESTSITE/ZEN153/index.php?main_page=checkout_process&action=confirm
Sent TO auth.net
(I changed forwardslash to backslash after https:)[x_relay_url] => https:\\chainweavers.LIVESITE/index.php?main_page=checkout_process&action=confirm&zenid=b03737d35c3d8c 4330608929ba6a72d3
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com