Originally Posted by
DrByte
High-level overview:
Writing a payment integration takes a strong understanding of that payment provider's API.
Consider the Authorize.net AIM payment module as an example.
The various functions (actually "methods") in that class handle different stages of checkout, and most of them are documented in docblocks in the code.
Essentially you must map each of the fields that are to be submitted via the API into appropriate objects in your payment module, and then transmit it using whatever prescribed method is documented in the API.
If you use a text-file-compare tool like winmerge to compare the authorizenet_aim.php module against the linkpoint_api.php module you'll see the differences between two modules using different APIs, which will give you essential clues necessary when cloning either one for your own use. You'll see the differences in class names and constants, and so on.
Bookmarks