Re: [WebDNA] MD5 Hash issue

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 102417
interpreted = N
texte = Tony, I have not tried to talk to Authorize.net.. so someone else who has please chime in here.. ..but whoever does will need to see more of your code to track the issue. You need to find out why Authorize.net is sending you back that error status. Perhaps they have some debug flags you can turn on to see more of the reason why the order "cannot be accepted". ? Perhaps that is what that "Reference Number:0" is trying to tell you? Have a look in Authorize.net docs.. look up what that reference number means and/ or see if there is some debug flags that will give you back more information. Just quick thoughts. -G On Apr 15, 2009, at 4: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)
Tony, I have not tried to talk to Authorize.net.. so someone else who has please chime in here.. ..but whoever does will need to see more of your code to track the issue. You need to find out why Authorize.net is sending you back that error status. Perhaps they have some debug flags you can turn on to see more of the reason why the order "cannot be accepted". ? Perhaps that is what that "Reference Number:0" is trying to tell you? Have a look in Authorize.net docs.. look up what that reference number means and/ or see if there is some debug flags that will give you back more information. Just quick thoughts. -G On Apr 15, 2009, at 4: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/ Govinda

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:

Showif for mulitple variations (1997) Re[2]: Balancing randomness (2000) Emailer help....! (1997) Is there a max number of fields? (1998) PCSDecrypt bugs still unfixed ... (2000) MacActivity and PCS (1997) email database file (2005) Sami -pdf (1998) problems with 2 tags (1997) WebCatalog for guestbook ? (1997) textarea to page display (1998) Questions. (1998) too many nested tags ... (1997) Protect vs Authenicate (1997) Setting up WebCatalog with Retail Pro data (1996) WebCatalog/WebMerchant bug? (1999) [WebDNA] File Include HTM (2008) Modulo function? (2000) Lost Field (1998) [OT] Bad Hard Drive? (2003)