PayFlow Pro Certs Path

[Former Member]

I am having difficulties configuring my credit card gateway. I have downloaded the SDK for PayFlow Pro (PayFlow Pro .NET v4.3.1), but the SDK provides no certificate. According to PayPal, as of version 4.3, PayFlow Pro no longer uses a certificate.

If I try leaving the "Certs Path" entry blank, I receive the following error on checkout:

Version 2007.0.631.12

Message Object reference not set to an instance of an object.

Source NetPoint.CreditCards

Stack at NetPoint.CreditCards.Functions.AuthorizeIBiz(Payment payment)

at NetPoint.CreditCards.Functions.Authorize(Payment payment)

at netpoint.classes.NPCCAuth.Authorize(NPOrder order)

at netpoint.commerce.verify.btnOrder_Click(Object sender, ImageClickEventArgs e)

If I give "Certs Path" an arbitrary folder such as "C:\Windows\Certs" that exists, but does not contain a certificate, I get the following error:

Credit card not authorized (The server certificate chain did not validate: The server certificate chain did not validate)

I saw this issue addressed in the forums a while back in February of 2008, but I did not see an answer or resolution. Is there an update for the software that I don't have? Is there any workaround to this?

Just as the previous poster in February of 2008 did, I called PayPal and had them send me a legacy SDK with a certificate, but according to him this will stop working as of September of this year.

Any help would be greatly appreciated.

[Former Member · Accepted solution]

SP1 uses the new PayFlowPro SDK, but as you can see from other threads it seems to be having issues.

You need to download the older PPF SDK and follow the instructions in the readme file.

- The certs path needs to actually contain the cert file that comes within the download

- You need to set a system path variable "PFPRO_CERT_PATH = C:\Windows\Cert"

- Copy the pfpro32.dll file into Windows\System 32

[Former Member · Accepted solution]

So I suppose this means you wouldn't recommend upgrading right now? My company's considering switching to Authorize.Net to get around this issue, but if a new release from SAP is likely forthcoming, then we will probably stick with PayFlow Pro. Will there likely be a more stable release before September of this year?

Thanks

[Former Member · Accepted solution]

It's actually a simple workaround, so I would recommend upgrading to SP1 before going live with SP0