Re: [WebDNA] MD5 Hash issue
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102419
interpreted = N
texte = G There's no custom coding here. I am using the straight-up WebMechant interface, configured with the admin, built right out of StoreBuilder and deployed and using the Authorize.net Direct Connect method. I'm about blind from reading on the archive list and I think the WebDNA interface is functioning properly. It appears that the SIM method requires the hash for improved security, but the AIM method (which I understand is the method used in the auth.net template) does not require a hash. The hash is being returned in the response text, but I think it is purely information. WebDNA is connecting too auth.net and getting a response. I'm of the opinion that it's something that is not "turned on" at auth.net, but I can't seem to convince anyone in support to dig a little deeper. I have had quite a time with the banks with setting up the account and the processor config too. Is the above logic flawed somehow? Does everyone using this have to customize it to get it to work? Thanks for the input. Tony Miller tmiller@thehawkeye.com On Apr 15, 2009, at 5:30 PM, Govinda wrote: > 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/ > > --------------------------------------------------------- > 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:
G There's no custom coding here. I am using the straight-up WebMechant interface, configured with the admin, built right out of StoreBuilder and deployed and using the Authorize.net Direct Connect method. I'm about blind from reading on the archive list and I think the WebDNA interface is functioning properly. It appears that the SIM method requires the hash for improved security, but the AIM method (which I understand is the method used in the auth.net template) does not require a hash. The hash is being returned in the response text, but I think it is purely information. WebDNA is connecting too auth.net and getting a response. I'm of the opinion that it's something that is not "turned on" at auth.net, but I can't seem to convince anyone in support to dig a little deeper. I have had quite a time with the banks with setting up the account and the processor config too. Is the above logic flawed somehow? Does everyone using this have to customize it to get it to work? Thanks for the input. Tony Miller tmiller@thehawkeye.com On Apr 15, 2009, at 5:30 PM, Govinda wrote: > 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/ > > --------------------------------------------------------- > 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/
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:
[OT] Adding languages to Alpha Editor (2004)
WC TableGrinder (1997)
2.0 Info (1997)
How To question on setting up downloads (1997)
[WebDNA] plupload ? (2012)
$Quit, $CloseDatabase corrections (1997)
View order not right (1997)
Multi Actions (1999)
NT Manual (1997)
WebCat2b12 Mac.acgi--[searchstring] bug (1997)
normal users.db calls ... (1998)
WebCatalog can't find database (1997)
Showing specific [cart] contents (1998)
[SHOWIF] (1997)
[WebDNA] Non-numbers entered into a field that asks for a (2008)
autosensing lanague selection (1997)
[removehtml] (was: Undocumented tags and contexts) (2000)
remotely creating and populating a stock inventory db - almost there! (1999)
Databases (2000)
Extended [ConvertChars] (1997)