Our authorize.net processing is done in some OLD perl cgi code - any
perl programmers out there? We are trying to convert to the SHA-512
hashing. Our current processing uses MD5, via the perl module
Digest::MD5.I use LWP::UserAgent to POST directly t...
@Renaissance @jgoebel @airman81 Ok, I am officially crying uncle.
@Renaissance - I decided to go back one more time tonight - and set up
the string with the login (I am not showing actual value below, but did
use the correct one), trans ID (0 for tes...
@RenaissanceYeah, I think you’ve got me on the right track with the 3
fields based on the updated documentation and using the AIM method. It
has truly been a group effort. I will try tomorrow. And the data being
sent has always worked, so I’m sure th...
@airman81OK - your post prior to this made sense and as I replied,
matched what I was doing in terms of the sig key to binary and hashing
the text. Now you posted something different and included a time stamp
and sequence, etc - and I don’t understan...
@jgoebelI’m using the hash because that was the code that was given to
me years ago by Authorize.net. I didn’t understand what it was doing,
but it worked. And they DO return the MD5 hash ( and now the SHA-512
hash) in the string that I split into an...
@airman81This matches what I’m doing (in terms of converting the hex sig
key to binary and hashing the string). So, I’m going to say I’m doing
that part correctly and will wait until I can once again try the 3
fields that some people say I should be ...