From what I understand, which is not much, AuthnetXML.class.php gives me access to all the php apis at once. AuthorizeNet.php does this as well, but by folding in all the other apis. The document I found regarding AuthnetXML seems to suggest that this file gives direct access to all api methods without needing the separate files. Is this right?
Does AuthnetXML.class.php replace AuthorizeNet.php? Or is it used separately? Does AuthnetXML generate the xml being sent, or is it acting on xml that it wants me to generate?
Thanks
(Also, if I have multiple questions, do you want them in separate posts?)
09-01-2012 08:37 PM
Ok, I see. They're really all XML conversion apis. Meaning I don't have to muck around in my own xml. Apparently you were able to create a single XML solution to cover every api type, since AIM now comes in a pure XML syntax.
Now all I need is the authnetXML doc!
09-02-2012 12:40 PM
You can use the examples provided in the AuthnetXML package as a guide for making each API call. There's also a tutorial that gives a good overview of how it all works.
09-03-2012 09:52 PM
Ok, I think I got it. It sounds like the documentation for AuthnetXML is entirely in the sample files provided (the examples folder of the AuthnetXML package). It looks pretty complete, but I just want to verify:
Is that a comprehensive list of the available functions?
10-03-2012 01:10 PM
It currently represents all of the available API calls. So, yes, it is complete. :)
10-04-2012 05:49 PM