Hacker News Reader

I am using PayPal's PayFlowPro. They were acquired by PayPal from Verisign, I believe. It has an XML API and a url string type of API. The API contains a very convenient methodology for handling subscription payments, which is why we use them. I was not really into storing credit card information, so the recurring payment is very handy. Very good reporting API as well.

View on HN

Was the API clear and easy to use? Did you have any trouble with documentation. I have used PayPal but in a more traditional sense, processing single payments. They provide a url where you can verify the buyer. Sometimes their service calls your cgi/script over and over with "complete" status but in fact it isn't. Are there any such quirks with PayFlowPro?

Yes, you can't really think of PayFloPro as PayPal. It is an actual merchant account. You obtain full credit card authorizations and can run reports to reconcile things through the API. The only thing to be mindful of is that the libraries they provide for using the APIs are pretty much either C or Java (I want to say PHP also, but I am not 100%). If you do not use the libraries I am pretty sure you can use URL strings to pass data back and forth.

Sorry, By 'Yes' I meant that the API was very clear. I have not seen any quirks dealing with the PayFlowPro system, it is all server side.

Reply on news.ycombinator.com