This is just a quick announcement to anyone how ever worked with or currently is working with the PayflowPro SDK. A customer of mine logged into their PayflowPro manager the other day and was greeted with the following message.
I decided to sit down and update my cfpayflowpro project. The old project used the Java API so I scrapped the project and re wrote it from the ground up. This project will now allow you take advantage of the updated PayflowPro SDK. I would like to take a few minutes and explain the architecture of the project because I really like how It came out. This is by far nowhere near a release because I still need to add some error handling and support for other methods like authorization & credits but this is a solid start.
This is a quick snapshot of the project structure.
The main component acts as a service manager for the entire project. This is the component you need to instantiate and use. The rest of them are all tied in through a nice api. The Account is a bean that hold your account information. The proxyVO is another bean and this one will hold proxy settings. The proxy settings are needed because this is basic http call so if your network uses a proxy you need to set this up. There also components for parsing the result and sending out notifications. Here is the code for the main component but I encourage you to download the project and give me some feedback. As I said before this project is not completed yet so any feedback would help.
#1 by Ryan Stille on 5/6/09 - 10:58 AM
Also I wanted to throw this out there - for those who are using the old CFX_PayFlowPro tag (which will stop working in September), there is a drop in replacement Custom Tag called CF_PayFlowPro available here: http://cf_payflowpro.riaforge.org/
For the most part you just need to switch CFX_ to CF_ and you are done.
#2 by Dan Vega on 5/6/09 - 11:06 AM
#3 by Jeff Coughlin on 5/6/09 - 11:28 AM
If I do use Dan's, I'll just have to make sure it's simple enough to add a method for recording the transaction info to a local database (if it doesn't already exist).
#4 by Dan Vega on 5/6/09 - 11:32 AM
#5 by scott conklin on 8/17/09 - 10:02 PM
great work. just one question though. I got a list element error (list element not found in list)In the parseResponse method of the PFproResult cfc. apparently the return string that i am getting back does not contain the elements that you are expecting, namely there is no PPREF and CORRELATIONID elements in my return string (in fact, i get a few that you don't parse).
here is what i get back in doing a test run...
RESULT=0&PNREF=V79C1DFC29AD&RESPMSG=Approved&AUTHCODE=010101&AVSADDR=Y&AVSZIP=Y&IAVS=N&PREFPSMSG=No Rules Triggered&POSTFPSMSG=No Rules Triggered
1) have you ever run into this before?
2) and have you thought of some error trapping or validation to check to see if all these elements are present
thanks for your work on this, a real big help.
#6 by Rodrigo Munera on 11/5/09 - 11:13 AM
I'll keep you posted if you're interested.