I'm planning on using the Payment gem in an upcoming project -- I have looked at the documentation, but haven't actually used it yet.
From my experience with Authorize.net's API on other projects, there are a lot of features that can be ignored. I've never used the MD5 fingerprint and it's never stopped me from processing transactions :-)
I suspect that the Payment gem is only doing the ADC Direct response over a SSL connection. It's not bothering to verify the transaction results from the authorization source.
That's not a big deal, in my opinion. If you've established the SSL connection to secure.authorize.net, it's pretty much guaranteed that you're talking with the authorization source that you'd expect.
by Craig Hockenberry — Oct 21
From my experience with Authorize.net's API on other projects, there are a lot of features that can be ignored. I've never used the MD5 fingerprint and it's never stopped me from processing transactions :-)
I suspect that the Payment gem is only doing the ADC Direct response over a SSL connection. It's not bothering to verify the transaction results from the authorization source.
That's not a big deal, in my opinion. If you've established the SSL connection to secure.authorize.net, it's pretty much guaranteed that you're talking with the authorization source that you'd expect.