Re: [WebDNA] MD5 Hash issue

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 102420
interpreted = N
texte = 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 Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] MD5 Hash issue (Donovan Brooke 2009)
  2. Re: [WebDNA] MD5 Hash issue (Tony Miller 2009)
  3. Re: [WebDNA] MD5 Hash issue (Terry Wilson 2009)
  4. Re: [WebDNA] MD5 Hash issue (Terry Wilson 2009)
  5. Re: [WebDNA] MD5 Hash issue (Donovan Brooke 2009)
  6. Re: [WebDNA] MD5 Hash issue (Donovan Brooke 2009)
  7. Re: [WebDNA] MD5 Hash issue (Tony Miller 2009)
  8. Re: [WebDNA] MD5 Hash issue (Tony Miller 2009)
  9. Re: [WebDNA] MD5 Hash issue (Donovan Brooke 2009)
  10. Re: [WebDNA] MD5 Hash issue (Terry Wilson 2009)
  11. Re: [WebDNA] MD5 Hash issue (Donovan Brooke 2009)
  12. Re: [WebDNA] MD5 Hash issue (Tony Miller 2009)
  13. Re: [WebDNA] MD5 Hash issue (Donovan Brooke 2009)
  14. Re: [WebDNA] MD5 Hash issue (Terry Wilson 2009)
  15. Re: [WebDNA] MD5 Hash issue (Tony Miller 2009)
  16. Re: [WebDNA] MD5 Hash issue (Donovan Brooke 2009)
  17. Re: [WebDNA] MD5 Hash issue (Terry Wilson 2009)
  18. Re: [WebDNA] MD5 Hash issue (Donovan Brooke 2009)
  19. Re: [WebDNA] MD5 Hash issue (Tony Miller 2009)
  20. Re: [WebDNA] MD5 Hash issue (Donovan Brooke 2009)
  21. Re: [WebDNA] MD5 Hash issue (Terry Wilson 2009)
  22. Re: [WebDNA] MD5 Hash issue (Tony Miller 2009)
  23. Re: [WebDNA] MD5 Hash issue (Tony Miller 2009)
  24. Re: [WebDNA] MD5 Hash issue (Terry Wilson 2009)
  25. Re: [WebDNA] MD5 Hash issue (Donovan Brooke 2009)
  26. Re: [WebDNA] MD5 Hash issue (Terry Wilson 2009)
  27. Re: [WebDNA] MD5 Hash issue (Tony Miller 2009)
  28. Re: [WebDNA] MD5 Hash issue (Tony Miller 2009)
  29. Re: [WebDNA] MD5 Hash issue (Terry Wilson 2009)
  30. Re: [WebDNA] MD5 Hash issue (Govinda 2009)
  31. [WebDNA] MD5 Hash issue (Tony Miller 2009)
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 Tony Miller

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:

Press Release hit the NewsWire!!! (1997) quotation marks needed? (2000) spawn (1998) Number searching/formats (1998) Question from a Neebie (2000) PCS Frames (1997) can WC render sites out? (1997) WebCatalog for guestbook ? (1997) European Convention (2004) [WebDNA] products.db (2013) WebCat2_Mac RETURNs in .db (1997) Share cost of training videos! (1998) format_to_days on NT (1997) Customizing WebDelivery.html (1998) Formatting of email on NT (1998) japanese characters (1997) Getting total number of items ordered (1997) Virtual hosting and webcatNT (1997) Using Plug-In while running 1.6.1 (1997) Another question (1997)