Payflow Pro and Authorize.net

jeff-christie

Have a new 7.7 customer who currently uses authorize.net for credit card verification and doesn't really want to switch when moving to FACTS and eStorefront. I'm not an expert in this area, but I did some digging and saw one website that seemed to say that payflow pro is a payment gateway and it seemed like it could be tied to authorize.net too not just paypal. Has anyone come across this or have any thoughts? Is this even possible with FACTS and the tcp/ip manager, even with some additional work or setup?

Legacy Contributor

I am actually today working on creating a CNP (Card Not Present) replacement class for Authorize.Net that will still use the same methods/functions as the Payflow Pro Class (cspfp.pvc) in Facts so there is very limited code changes in FACTS - just change a couple of lines in SOC610.

A few things I have found out today.
- TCP/IP Manager will not work (or I just have not felt like going through the ordeal of trying since it passes some sort of paramaeer as "Verisign" in the connection string and I am not sure if there is a way to denote Authorize.Net (I have asked several times before and can never get a straight answer) - Since this has been specific to one client of mine and they are on an AIX server, I just post directly within curl ( open(hfn)"

- From what I can see, CP (Card Present ) and CNP (Card Not Present) seem to be posted to two different authorize.net gateways and in two different formats. I am only working at this time for a CNP transaction so its not a big deal at this time.... but they will be integrating the CP into their system in the near future which I am sure I will have to accommodate.

- If passing the Credit Card name field you will have to parse it into first and last name fields in the param_list$ (x_first_name= and x_last_name=)

- All the result codes are different (at least CNP) than Payflow Pro as Payflow Pro uses named-value pairs in its results and Authorize.Net sends a delimited string as its results (you can specify the delimiter you want the response to use within the post of the processor)

I am still in the process of interrogating the responses in Authorize.Net and converting them to look identical to PayFlow Pro's Responses so there is very limited changes between Auth.Net and Payflow Pro but if I find anything else of interest for you, I will let you know.

These are the guides that I have been using -
Authorize.Net - developer.authorize.net/.../
Payflow Pro - cms.paypal.com/.../PP_PayflowPro_Guide.pdf (using to assist in translating Authorize.Net responses into Payflow Pro Responses for FACTS purposes)

Hope this helps!