Re:How not to get acquired
by polyfractal on Thursday June 21, 2012 @04:29PM
(#4144035)
I don't have the code handy (was client work for a third party), but we definitely used XML through Auth.net's AIM. Here are the API docs for it:
http://www.authorize.net/support/AIM_guide_XML.pdf
We also used XML through their CIM to manage customer profiles. To be fair, this was all in PHP, and the code was inherited so I'm not sure if there was a better way to deal with Auth.net's API.
I do know that their dashboards were thoroughly unpleasant to deal with and I felt the API was obtuse in many different locations.
Interesting. Here's the non-XML AIM guide: http://www.authorize.net/support/AIM_guide.pdf
That's the one we use. I didn't even know they had an XML option--and now I'm going to try to forget it! :-)
Re:How not to get acquired
by polyfractal on Thursday June 21, 2012 @06:30PM
(#4144501)
Interesting! I had no idea they had a non-XML option. If I was still working on the project, I'd totally push for that.
Good to know for future projects =)
Business::OnlinePayment is one of those standup CPAN libraries that may not be well known but solves real(world) problems. I'm using it in a line of business app at work and when we ditched authorize.net I migrated to ippay by changing a couple lines of code.
I think the perl lib formats and sends this as XML, and perhaps dropping down to XML is required if the language lib isn't up to date.
Re:How not to get acquired
by mike-cardwell on Thursday June 21, 2012 @05:14PM
(#4144222)
No it doesn't
Does the non-AIM option (I forget what it is called) use XML?