Jump to content

LaughingHorse

Member
  • Posts

    164
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by LaughingHorse

  1. Do you think it would be worth it to try a new transaction key then? It's just a matter of going to Authnet and creating one while killing off the current one.
  2. There is a space there. I removed the space.Tested and still got the 99 error. I'm thinking of going back to the Authnet website and generating a new transaction key and loading it in place of the current one. After the test here is the error info. Today, 08:07 [Unknown ()] raw_fingerprint: - ***********^151206-080701-69941449410823^1449410823^351.70^ Today, 08:07 [Unknown ()] txn_key (ignore the carets): - ^****************^ Today, 08:07 [Unknown ()] encode method: - hash_hmac Today, 08:07 [Unknown ()] x_login: - *********** Today, 08:07 [Unknown ()] x_fp_sequence: - 151206-080701-69941449410823 Today, 08:07 [Unknown ()] x_fp_timestamp: - 1449410823 Today, 08:07 [Unknown ()] x_amount: - 351.70 Today, 08:07 [Unknown ()] x_tran_key: - **************** Today, 08:07 [Unknown ()] x_fp_hash: - e7907fae6857e38df4b92ebff4ec4e1c I did notice in the raw_fingerprint, while it does have: x_loginx_fp_sequencefp_timestampx_amountit does not appear to have the txn_key (x_tran_key) info. Unless the error code is cutting off at a certain number of spaces. So before generating a new transaction code, is there a way to double check that the x_tran_key is being picked up in the fingerprint? I am using the Authorize.net Payment Gateway version 1.1.1 CubeCart 6.0.8
  3. Today, 18:38 [Unknown ()] raw_fingerprint: - LOGIN CODE ^151205-183841-14691449362323^1449362323^21.41^ Today, 18:38 [Unknown ()] txn_key (ignore the carets): - ^TRANS KEY CODE^ Today, 18:38 [Unknown ()] encode method: - hash_hmac Today, 18:38 [Unknown ()] x_login: - LOGIN CODE Today, 18:38 [Unknown ()] x_fp_sequence: - 151205-183841-14691449362323 Today, 18:38 [Unknown ()] x_fp_timestamp: - 1449362323 Today, 18:38 [Unknown ()] x_amount: - 21.41 Today, 18:38 [Unknown ()] x_tran_key: - TRANS KEY CODE Today, 18:38 [Unknown ()] x_fp_hash: - 878e9ae5dbee8f24acf5bbb1143626bf ********************************************************************************************************************** * Note: for security, I replaced the LOGIN CODE and TRANS KEY CODE with those words. * * The Login code and Trans Key were correct before I changed them * **********************************************************************************************************************
  4. You mentioned above we could try to verify that the encryption process is the same for my version of PHP Would it make sense to do that? This issue is a hard nut to crack But the satisfaction of beating it will be great
  5. Yes, Chicago would be -6 from GMT and the server is on CST I can check with them regarding breaking apart the fingerprint. I was only able to get the info to put in the test URL on Authnet today after you gave me the code to capture the errors. I did generate both fingerprints from the Authnet tool.
  6. Yes, I copied and pasted the key. I'll try manually entering it. run another order and see what happens. Be right back. Got the same error messages with a different Fingerprint The generated fingerprint: E6339D021AA25A8A9AF5466717498730 Troubleshoot a Response Code 99Verify that you are using the current transaction key. Obtain a new transaction key in the Merchant Interface and update all scripts that require a transaction key accordingly. Please note that once a new transaction key has been obtained, the old transaction key will expire and become invalid after 24 hours. Be sure that all sites using SIM are updated with the new transaction key before the old key expires. To obtain a transaction key: Log into the Merchant Interface at: https://account.authorize.net/.Click Account from the main toolbar.Click API Login ID and Transaction Key.Under Create New Transaction Key, enter the answer to your Secret Question.To disable the old transaction key, check the box titled Disable Old Transaction Key(s). Note: If the Disable Old Transaction Key(s) box is not checked, the old transaction key will automatically expire and become invalid in 24 hours.Click Submit.Remember to store the transaction key in a secure location. Do not share it with anyone, as it is used to protect your transactions. Check to see if you have a properly formatted value for x_amount. Verify that there is no dollar sign. The value should be strictly numeric. Additionally, our sample scripts require a numeral with two decimal places. Fingerprints created with an invalid amount value may result in Response Code 99.Compare the case of x_amount that is being posted to your script with the case of x_amount in the fingerprint generating script. Some scripting languages (such as Perl and PHP) are case sensitive. If you post x_Amount to your SIM script and the script is programmed for x_amount, the uppercase version may be ignored by the script and result in an incorrect fingerprint. Correct the case of either your post variable or the variable in the script to fix the error. Note: The sample Perl script is written to accept the amount field as x_amount. The sample PHP script is designed to accept this field as x_Amount.
  7. Just noticed below the Fingerprint it gave me this Troubleshoot a Response Code 99Verify that you are using the current transaction key. [NOTE: I am using a current transaction key] Obtain a new transaction key in the Merchant Interface and update all scripts that require a transaction key accordingly. Please note that once a new transaction key has been obtained, the old transaction key will expire and become invalid after 24 hours. Be sure that all sites using SIM are updated with the new transaction key before the old key expires. To obtain a transaction key: Log into the Merchant Interface at: https://account.authorize.net/.Click Account from the main toolbar.Click API Login ID and Transaction Key.Under Create New Transaction Key, enter the answer to your Secret Question.To disable the old transaction key, check the box titled Disable Old Transaction Key(s). Note: If the Disable Old Transaction Key(s) box is not checked, the old transaction key will automatically expire and become invalid in 24 hours.Click Submit.Remember to store the transaction key in a secure location. Do not share it with anyone, as it is used to protect your transactions. Check to see if you have a properly formatted value for x_amount. Verify that there is no dollar sign. The value should be strictly numeric. Additionally, our sample scripts require a numeral with two decimal places. Fingerprints created with an invalid amount value may result in Response Code 99.Compare the case of x_amount that is being posted to your script with the case of x_amount in the fingerprint generating script. Some scripting languages (such as Perl and PHP) are case sensitive. If you post x_Amount to your SIM script and the script is programmed for x_amount, the uppercase version may be ignored by the script and result in an incorrect fingerprint. Correct the case of either your post variable or the variable in the script to fix the error. Note: The sample Perl script is written to accept the amount field as x_amount. The sample PHP script is designed to accept this field as x_Amount.
  8. It gave me a generated Fingerprint: E6339D021AA25A8A9AF5466717498730
  9. OK too a screenshot of the system error log, and covered up the LoginId and Transaction key. Left the rest alone so you can see them.
  10. Just noticed in the Fingerprint, is it collecting x_login Also is the nomenclature being transmitted to Authnet the way Authnet wants e.g. x_tran_key x_amount I'm guessing the "txnkey" is the private transaction key Authnet assigned to my account.
  11. Does that go between $fp_sequence = $this->_basket['cart_order_id'].time(); // Enter an invoice or other unique number. $fp_timestamp = time(); $fingerprint = $this->_getFingerprint($this->_module['acNo'],$this->_module['txnkey'], $this->_basket['total'], $fp_sequence, $fp_timestamp); And $hidden = array( 'x_type' => $this->_module['payment_type'], //AUTH_CAPTURE or AUTH_ONLY 'x_login' => $this->_module['acNo'], 'x_fp_hash' => $fingerprint, 'x_amount' => $this->_basket['total'], 'x_fp_timestamp' => $fp_timestamp, 'x_fp_sequence' => $fp_sequence, 'x_version' => '3.1', 'x_show_form' => 'payment_form', 'x_test_request' => 'false', 'x_method' => 'cc', 'x_invoice_num' => $this->_basket['cart_order_id'], 'x_description' => "Payment for order #".$this->_basket['cart_order_id'],Thank You
  12. OK, just had a long talk with someone in support of Authorize.net She told me I need to find where CubeCart is generating the Fingerprint Code. She said it's somewhere in the back end. x_login x_tran_key x_fp_timestamp x_fp_sequence x_amount x_currency_code I was also told that authorize.net "developer section' advises to avoid generating x_currency_code because it is causing issues. They have a tool to help track down errors at https://developer.authorize.net/api/reference/responseCode99.html And there is a guide at http://www.authorize.net/content/dam/authorize/documents/SIM_guide.pdf From the Authorize.net guide (pg26) Generating the Unique Transaction Fingerprint Transaction authentication for SIM is a transaction fingerprint, or a hash of merchant- and transaction-specific information using the HMAC-MD5 hashing algorithm (Hash-based Message Authentication Code) (MD5 RFC 1321 with a 128-bit hash value). The HMAC-MD5 algorithm is used only for generating the unique transaction fingerprint. The transaction fingerprint must be generated for each transaction by a server-side script on the merchant’s web server and inserted into the transaction request. The payment gateway uses the same mutually exclusive merchant information to decrypt the transaction fingerprint and authenticate the transaction. You can develop a script for generating a fingerprint in two ways:  By using the API field information in this section to customize your script.  By using a free Authorize.Net sample code available on the Developer Center at http://developer.authorize.net
  13. Thank you! This is a really perplexing problem. the authnet 99 issue
  14. I adjusted the store setting in the control panel to CST which is what the server is. I am still getting the Authnet-error 99 I have the Timezone set to America/Chicago The UTC Offset is at 0 Do I need to change that as well to -6 hours (the current difference) And if so, will I need to change it back when time changes in the Spring. Further: I'm about to implement a SSL. When I do that so I need to switch to AIM? If so, should I wait to try and fix the error 99 issue till the SSL is installed? Also do I need to change anything regarding the Password Required Mode
  15. Bsmither, Thank you! I tried that location, but didn't like the look so I placed it a bit above. Around line 138 <p class="buy_button"><strong>{$LANG.catalogue.out_of_stock}</strong></p> {/if} {/if} </div> <!-- added call us --> Now it is right next to the product picture, just below the buy button.
  16. Just joined GitHub and posted. As for my memory... It's like a screen door
  17. Hi! I would like to know how I can show my store phone number in two places: On the Contact Us formOn the product page right below the "Add to cart" button (see attached)I did experiment by adding the phone number and address to the Copyright page, but it did not stand out too well, and i want to make it really easy for customers to find the phone number. Thanks in advance for your advice! Allen
  18. If I remember correctly, you had put in a request for something like this about 7 or 8 months ago. But since there is nothing I figured someone may know a way around it.
  19. I have the Store Settings time set for New York Time Because we ship in a New york minute (heh heh heh) I'll check and see if I can find it in the Control panel. Thank you!
  20. Bsmither - Yeah, the child skin did not really seem to be fitting the way it seems to work. Thanks for your help. I've got that part working right now. I knew it had to be something minor I missed
  21. So I need my host to fix this then? (time stamp) I have it set for SIM currently, and that is where I am getting the errors. I also have not done anything to edit any of the internals - with the exception of the look. So the fp_sequence is stock as installed. The test order # is: 151130-150953-2043
  22. Bsmither Thank you! If I understand correctly I change <uid>[email protected]</uid> TO <uid>UUID-Code</uid> AND change <name><![CDATA[foundation]]></name> <display><![CDATA[Foundation]]></display> TO <name><![CDATA[SKINNAME]]></name> <display><![CDATA[SKINNAME]]></display> Skin name being whatever the name of the child skin is. UUID code can e generated on line with a tool I just found here: https://www.uuidgenerator.net so a code like this: 095f4d8b-b647-4c35-84ea-83d16b05d73a Is that correct?
  23. I have authnet set up see attached: [Authnet settings Screenshot from 2015-11-30 10:13:24.png] When I click on checkout, the page refreshes, and I have to click on checkout again. It brings me over to authorize.net and I get a 99 error See attached screenshot [Authnet-error 99 Screenshot from 2015-11-30 10:10:27.png] I called authnet because the error was happening on their site. The information I got from them was the error is either the Transaction Key. I get a new one and entered it while the rep from authnet was on the phone. It was entered correctly, as was the API login ID. The rep told me the error 99 is caused either because the wrong transaction key and/or wrong API Login ID was entered. We doublechecked and found it was correct. OR it is caused because "Amount has to be set in scripting prior to the generation of the fingerprint hash may not be properly posting all required fields for AIM x_login x_underscorefp_sequence x_fp_timestamp x_fp_has x_amount" The error log and system error log on my system are clean. (No errors registered) Thank you in advance for your help. AN update from an email just received from authnet: Issues with these values or with the generation process can cause Error 99. The three most likely causes of Error 99 are: 1) The Transaction Key that you have embedded in your script is not correct. Just to be sure, generate a new transaction key, disable the old transaction key, enter the new value in your script and test the connection.2) The amount has to be set in your scripting prior to the generation of the fingerprint hash. This usually means that the amount should be set in a previous form and posted to the script that generates the fingerprint hash. 3) You may not be properly posting all the required fields for SIM. The following fields must be present in your payment form request in order for the transaction to be accepted: 1. API Login ID (x_Login) 2. The sequence number of the transaction (x_FP_Sequence) 3. The time when the sequence number was generated (x_FP_Timestamp) 4. The Fingerprint Hash (x_FP_Hash) 5. The amount of the transaction (x_Amount) 4) If you are attempting to pass the field x_currency_code with your payment form request, you must include this field in your fingerprint hash generation. Since Authorize.Net currently handles transaction amounts in the merchant's local currency by default, you may alternately stop passing x_currency_code.
  24. I am using Foundation Skin on CC6.08 I downloaded the entire skin using an FTP package (Filezilla) I then renamed the skin and uploaded it into the skins folder on my installation. When I went into Store Settings | Layout settings | Looking at the drop down "Skin Settings" the only option I have is "Foundation" The renamed, uploaded skin is not showing as an option. I then went to "Maintenance" and ticked the Clear cache Clear SQL cache Clear language cache Clear image cache and Rebuild Sitemap options. Clicked "Save' and the new skin is not showing up. I'm sure I'm missing something silly. Thanks in advance for your help.
  25. Hi! Back again. We discussed at one time, having the ability to add the insurance rates from USPS. It is still not there. Currently we are losing from 2.75-$10 per shipment due to not being able to charge for Insurance. For example, one item sells for 342.10 Cube Cart gives a rate of $9.60 which does not include insurance ($5.80). I did add $2.90 in the field "Handling Cost" to cover the signature. Is there some code I can add to the USPS module that will grab and add the insurance charges from the USPS website to the shipping US and International? Or, worst case scenario, is there a way to just add an additional percentage (for now) to the USPS rates, like 3% of the item total. I think since USPS is giving the info from their site, and CubeCart is receiving that info it is logical to be able to include that in what we are charging for the shipping. I also tried a work around of creating a tax class "Insurance and signature", but unfortunately, it can only apply to one country, not everything. My ideal scenario or set up would be something like the attached screen shots (long term), but is there anything I can do in the short term? Thanks!
×
×
  • Create New...