Re: [WebDNA] MD5 Hash issue

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 102418
interpreted = N
texte = 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 On Apr 15, 2009, at 6:12 PM, Tony Miller wrote: > All, > > I have WebDNA talking with Authorize.net and it is sending back the > following Response Text: > > This transaction cannot be accepted. > Hash: 93948820X....... > Status: Error > Reference Number: 0 > > I've been searching the list archive, but haven't found an answer. > Do I need to add something to the global authorize.net files or is > the solution some setting I'm missing. I'm not a WebDNA whiz so I'm > learning as I go here. > > I got this explanation from A-N for how the HASH is put together: > > The MD5 Hash option lets your script verify that the results of a > transaction are actually from Authorize.Net. MD5 is a specific way > of encrypting information to make it unreadable unless the original > information that created the MD5 hash is known. Every time we > return the results of a transaction, we also return an MD5 hash > that would, due to the nature of the MD5 algorithm, be unique to > the transaction. > > The MD5 hash is created by combining MD5 Hash Value (which is > assigned by the merchant in the account's Settings); the API Login > ID; the transaction ID number we assigned to the transaction; and > the amount of the charge, in that order. The resulting string is > then used to generate the MD5 hash. > > For an example, if your MD5 Hash Value was "secret", your API Login > ID was "mylogin", the transaction ID was "987654321", and the > amount was "1.00", then an MD5 would be generated from the > following string: "secretmylogin9876543211.00". > > When your script receives the results of the transaction you can > create an MD5 hash on your side, in the same basic manner, and then > confirm it matches ours. You will already know your MD5 Hash Value > and your API Login ID, and will receive the Transaction ID and > amount in the results. > > Any help would be great. > > Tony Miller > tmiller@thehawkeye.com > > > > --------------------------------------------------------- > 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:

    
  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)
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 On Apr 15, 2009, at 6:12 PM, Tony Miller wrote: > All, > > I have WebDNA talking with Authorize.net and it is sending back the > following Response Text: > > This transaction cannot be accepted. > Hash: 93948820X....... > Status: Error > Reference Number: 0 > > I've been searching the list archive, but haven't found an answer. > Do I need to add something to the global authorize.net files or is > the solution some setting I'm missing. I'm not a WebDNA whiz so I'm > learning as I go here. > > I got this explanation from A-N for how the HASH is put together: > > The MD5 Hash option lets your script verify that the results of a > transaction are actually from Authorize.Net. MD5 is a specific way > of encrypting information to make it unreadable unless the original > information that created the MD5 hash is known. Every time we > return the results of a transaction, we also return an MD5 hash > that would, due to the nature of the MD5 algorithm, be unique to > the transaction. > > The MD5 hash is created by combining MD5 Hash Value (which is > assigned by the merchant in the account's Settings); the API Login > ID; the transaction ID number we assigned to the transaction; and > the amount of the charge, in that order. The resulting string is > then used to generate the MD5 hash. > > For an example, if your MD5 Hash Value was "secret", your API Login > ID was "mylogin", the transaction ID was "987654321", and the > amount was "1.00", then an MD5 would be generated from the > following string: "secretmylogin9876543211.00". > > When your script receives the results of the transaction you can > create an MD5 hash on your side, in the same basic manner, and then > confirm it matches ours. You will already know your MD5 Hash Value > and your API Login ID, and will receive the Transaction ID and > amount in the results. > > Any help would be great. > > Tony Miller > tmiller@thehawkeye.com > > > > --------------------------------------------------------- > 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:

PROBLEM (1997) [WebDNA] Text Variable in Search (2010) Showing unopened cart (1997) &fieldsdir=ra truely random?? (2000) [WC 2.1.30] Stack overflow. (2000) ReadDateFormat bug in 3.x (1998) Hiding HTML and page breaks (1997) [WebDNA] WebDNA 7 (2011) Emailer (WebCat2) (1997) Great product and great job ! (1997) a search based on ^(contains) (1998) [index] (1997) No Data Results (1997) Date Sorting (1997) Shipping Math (1999) carriage returns in data (1997) XML WebDNA (2006) Newbie Help (2003) [WebDNA] writing pdfs on the fly (Avery labels #5160) (2010) Help needed: older WebCat app breaks under 4.0.1 (2000)