I have found another payment processor that has implemented an XML based protocol. They provide some unsuitable pre-written integration options but have confirmed that those can be bypassed and their functionality replicated on any platform by just posting them xml formed requests.
If I were to write a set of tcl functions that take the payment request parameters and form an xml string to send to their server using AOLServer API calls I think that we would have a fast efficient and scaleable process. By the way, is tls the only way to do an ns_httpget over ssl or is there an ns_httpsget or equivalent?. How else could I ensure that the xml request goes out encrypted?
I wondered whether you think that this is as good an option as writing a *.so module (as with the verisign solution) to allow access to c libraries for making connections to payment providers. In other words for purely technical reasons do we prefer the verisign module or the authorize module?
Richard
