Hi,

I"m getting educated on an app where I'll be using CF8 to process C/Card transactions. I'm reading the PayFlow Pro Developers Guide..... meanwhile...

I see a PayflowPro.cfc in the ZIP and examples of how to call it:
<CFX_PAYFLOWPRO
QUERY = "RESULT"
HOSTADDRESS ="test-payflow.verisign.com"
HOSTPORT = "443"
TIMEOUT = "30"
PROXYADDRESS = ""
PROXYPORT = ""
PROXYLOGON = ""
PROXYPASSWORD = ""
TRXTYPE = "S"
TENDER = "C"
PARTNER = "PayPal"
USER = "PayPalLoginID"
PWD = "PayPalpassword"
ACCT = "5105105105105100"
EXPDATE = "1209"
AMT = "27.33"
COMMENT1 = "This is a comment - noautomatically escaped"
COMMENT2 = "Embedded = and & work when escaped"
CERTPATH = "C:\Inetpub\wwwroot\CFIDE\certs">

1) Is anyone using this code successfully?

2) I'm unclear how to read the response from the server? Using CGI.something? THen use CFIF to look for 0 or another result and proceed...

Any snippets would be much appreciated ;-) (sorry for the Newby questions, I've never done C/Card trans in CF)

Thanks!

Howdy,

We have a lot of customers that use PayFlowPro. If you are on a shared server, CFX_PayFlowPro should be installed already. On a VPS or dedicated you will have to register it.

If you are on a shared server, will need to contact support and we can move the required certificate files to a subfolder of your site (or you can upload them - you should have received some with the documentation) and support will give you the path to your website on the server. The line of code should then look something like:





I have never personally built an app that uses this tag, but I was able to find some sample code that I *think* should work. But I am not a developer




Hope this gets you started!!!



-Dave

Thanks,

This looks a bit sparse but I'll certinally start here.

Anyone else using this tag please post with your thoughts or code-snippets ;-)


THX.

<!--
PayPal Payflow Pro Custom ColdFusion Tag - v4.01

Updated Payflow Pro Coldfusion Tag to work with latest
Payflow Pro Java SDK available from PayPal at
http://www.pdncommunity.com/pdn/board/message?board.id=payflow&thread.id=650

This tag is not a "complete" drop-in replacement for the older v3 CF Tag.

Here is a list of a few items must be addressed migrating from v3 to v4:

1. Host Urls are changed. They are now pilot-payflowpro.paypal.com (testing) and payflowpro.paypal.com (production)
2. The Java SDK requires the use of Sun's Java implementation using the URLSTREAMHANDLER tag as shown below. Your
implementation might require a different handler. See the Release Notes of the Java SDK.
3. The Java SDK has full debugging which can be turned off or on by passing a log file name as shown below.
4. Passing the tag DEBUG itself will display the items passed to class path and will help with debugging.
5. The VENDOR tag is now required as shown below.
6. The Request ID is auto-generated if you do not pass one. However, you can supply your own request id in the
parameter REQUESTID, but you must supply a value otherwise an exception will be thrown.
7. The payflow.jar file, which is obtained from the url above, must be included in the same directory as
the class file.

!-->

<CFX_PAYFLOWPRO QUERY = "RESULT"
HOSTADDRESS = "pilot-payflowpro.paypal.com"
HOSTPORT = "443"
TIMEOUT = "30"
PROXYADDRESS = ""
PROXYPORT = ""
PROXYLOGON = ""
PROXYPASSWORD = ""
TRXTYPE = "S"
<!---sale, auth--->
TENDER = "C"
<!--- credit, [ach]--->
PARTNER = "partner"
USER = "user"
PWD = "password"
VENDOR = "vendor"
ACCT = "5105105105105100"
EXPDATE = "1209"
AMT = "0.01"
STREET = "123 Main Street"
ZIP = "12345"
COMMENT1 = "This is a comment - note that it is automatically escaped"
COMMENT2 = "Embedded = and & work when escaped"
<!--- This streams the new files, rather than storing the old files --->
URLSTREAMHANDLER = "sun.net.www.protocol.https.Handler"
CERTPATH = "C:\websites\<your home dir>\<subdirectory>">
DEBUGFILE = "C:\websites\<your home dir>\<subdirectory>\payflow_java.log">
DEBUG
>


<!-- Parmlist not needed becuse we are passing all required !-->
<!-- PayPal parameters though the Cold Fusion tag. !-->


<!-- Returned in the Query !-->
<CFOUTPUT QUERY="RESULT">
<hr>
<p><b>PARMLIST:</b> #PARMLIST#<BR>
<p><b>RESULTSTR:</b> #RESULTSTR#<BR>
<p><b>VERSION:</b> #VERSION#<BR><BR>
</CFOUTPUT>

<!-- Or access directly !-->
<hr>

<CFOUTPUT QUERY="RESULT">

<!-- Check return code !-->
<!-- Place all of your logic here !-->
<CFIF result.result IS "0">
Transaction <b>#result.respmsg#</b><br>
Result: #result.result#<br>
PNREF: #result.pnref#<br>
AuthCode: #result.authcode#<BR>
<!-- FPS return codes !-->
<!-- 126 - Fraud Protection Services Filter -- Flagged for review by filters !-->
<CFELSEIF result.result IS "126">
Transaction under review:<BR>
Thank you for your purchase, we are currently reviewing your order.<BR>
Transaction <b>#result.respmsg#</b><br>
Result: #result.result#<br>
PNREF: #result.pnref#<br>
AuthCode: #result.authcode#<BR>
<!-- 127 - Fraud Protection Services Filter -- Not processed by filters !-->
<CFELSEIF result.result IS "127">
Transaction under review:<BR>
Thank you for your purchase, we are currently reviewing your order.<BR>
Transaction <b>#result.respmsg#</b><br>
Result: #result.result#<br>
PNREF: #result.pnref#<br>
AuthCode: #result.authcode#<BR>
<!-- 125 - Fraud Protection Services Filter -- Declined by filters !-->
<CFELSEIF result.result IS "125">
Transaction Declined:<BR>
We are unable to complete your purchase at this time. Please contact
this site's customer service.<BR>
Click back and check to ensure your payment information is correct.<BR>
Transaction <b>#result.respmsg#</b><br>
Result: #result.result#<br>
PNREF: #result.pnref#<br>
<!-- AuthCode commented out since result 125 does not return an !-->
<!-- AuthCode in the response as the transaction was not processed. !-->
<!-- If it is uncommented, you will get an UndefinedElementException: !-->
<!-- Element AUTHCODE is undefined in RESULT. See the RESULTSTR value !-->
<!-- displayed above which contains the actual response string for !-->
<!-- the values which may be accessed successfully. !-->
<!--- AuthCode: #result.authcode# ---><BR>
<!-- End FPS return codes !-->
<CFELSE>
Transaction Declined: #result.respmsg#<br>
</CFIF>

</CFOUTPUT>
----------------------------

By Sept 2009, Paypal will require us to use the new format. The script is here...
http://developer.paypal-portal.com/pdn/board/message?board.id=payflow&thread.id=6807

[/quote]