Theocacao
Leopard
Design Element
Comment on "Ruby, the Payment Gem and Authorize.net"
by Daniel Lyons — Oct 21
Same here. I implemented a custom "AIM" transport for my company last year. I don't remember anything about "fingerprints" and so we're definitely not using that functionality, but yet we're processing transactions every day, so it's clearly not a necessary requirement.

One thing I noticed was that the AIM implementor's guide was often vague about the distinction between recommended and required.
Back to "Ruby, the Payment Gem and Authorize.net"
Design Element

Copyright © Scott Stevenson 2004-2015