Re: [WebDNA] MD5 Hash issue
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102421
interpreted = N
texte = But the password is not the same as the trans key. Is there a field for a transaction key? If not, you'll have to use the password I guess, even though that's a pretty bad idea to throw around a password unless you're the only one privvy to this stuff. But be warned... Authorizenet makes you change this every 3 months, so you'll have to stay on top of it. On Apr 16, 2009, at 9:50 AM, Tony Miller wrote: > Terry, > > Your description is exactly how I have mine set up. I have the API > Login ID in the AuthorizeNet Login field and the Transaction Key in > the AuthorizeNet Password field. > > Snippet from support email: > > ? Please check your script and verify you are posting the API Login > ID for the account in question. If you are not posting the correct > API Login ID, please edit the script and confirm that the field > x_login is set to the API Login ID that you may obtain from the > Authorize.Net Merchant Interface. Please see the Merchant > Integration Guide at http://www.authorize.net/support/ > merchant_guide.pdf for instructions on obtaining the API Login ID. > > I can't see a problem with the WebDNA, but they keep alluding to > that as the culprit. > > Tony Miller > tmiller@thehawkeye.com > > On Apr 15, 2009, at 10:12 PM, Terry Wilson wrote: > >> With Authnet you have other options. One is to send a transaction >> key. This is something the authnet account holder generates from >> their authnet account settings and gives to you. It's a several >> character string that stays the same until they generate a new >> one. It acts as a password of sorts, and allows a webserver to >> communicate to the authnet account holder's account. You send this >> key, along with their authnet username, and that's all they need. >> This is how I've been doing mine for years, and my authnet clients >> do the same. No hash, no problem. >> >> Terry > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/
Associated Messages, from the most recent to the oldest:
But the password is not the same as the trans key. Is there a field for a transaction key? If not, you'll have to use the password I guess, even though that's a pretty bad idea to throw around a password unless you're the only one privvy to this stuff. But be warned... Authorizenet makes you change this every 3 months, so you'll have to stay on top of it. On Apr 16, 2009, at 9:50 AM, Tony Miller wrote: > Terry, > > Your description is exactly how I have mine set up. I have the API > Login ID in the AuthorizeNet Login field and the Transaction Key in > the AuthorizeNet Password field. > > Snippet from support email: > > ? Please check your script and verify you are posting the API Login > ID for the account in question. If you are not posting the correct > API Login ID, please edit the script and confirm that the field > x_login is set to the API Login ID that you may obtain from the > Authorize.Net Merchant Interface. Please see the Merchant > Integration Guide at http://www.authorize.net/support/ > merchant_guide.pdf for instructions on obtaining the API Login ID. > > I can't see a problem with the WebDNA, but they keep alluding to > that as the culprit. > > Tony Miller > tmiller@thehawkeye.com > > On Apr 15, 2009, at 10:12 PM, Terry Wilson wrote: > >> With Authnet you have other options. One is to send a transaction >> key. This is something the authnet account holder generates from >> their authnet account settings and gives to you. It's a several >> character string that stays the same until they generate a new >> one. It acts as a password of sorts, and allows a webserver to >> communicate to the authnet account holder's account. You send this >> key, along with their authnet username, and that's all they need. >> This is how I've been doing mine for years, and my authnet clients >> do the same. No hash, no problem. >> >> Terry > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/
Terry Wilson
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Help! WebCat2 bug (1997)
Page Breaks in Word (2003)
Emailer (1997)
printing twice? and fix (1997)
Not really WebCat - need HTML Grider (1997)
Enhancement Request for WebCatalog-NT (1996)
HideIf ip= OR ip= (1998)
no global [username] or [password] displayed ... (1997)
[WebDNA] List Archives? (2009)
Textarea (1998)
Editing the search string (1997)
Emailer (1997)
Database (2000)
ftp to webstar (2001)
possible, WebCat2.0 and checkboxes-restated (1997)
Re:2nd WebCatalog2 Feature Request (1996)
WCS Newbie question (1997)
WCS Newbie question (1997)
$purchase WITHOUT creditcar (1997)
wc 2 pro users - sites, quotes wanted (1997)