PayPal SDK v4.31 Changes

PayPal has updated its security measures for the PayFlow Pro SDK. Because of these changes they will no longer accept transactions from any version older than 4.31 starting at 12:00AM EDT on September 1, 2009. This will impact business for many of our customers, below is what you will instruct the customer to do if they can not submit PayPal orders after Sept 1 2009.

Informational Links

PayPal Homepage for PayFlow Pro changes:
https://cms.paypal.com/us/cgi-bin/?cmd=_render-content&content_ID=developer/gateway_update&mplx=3484-73577-1499-2

A FAQ for these changes can be found from PayPal here:
https://cms.paypal.com/us/cgi-bin/?cmd=_render-content&content_ID=developer/gateway_update_FAQ

Upgrade instructions for many 3rd party shopping carts:
https://cms.paypal.com/us/cgi-bin/?cmd=_render-content&content_ID=developer/gateway_update_merchant_cart

Code samples for using the HTTPS interface can be found here:
http://www.pdncommunity.com/pdn/board/message?board.id=payflow&thread.id=1008

ColdFusion

Customers using ColdFusion should see no change in functionality. This required an updated Java SDK to be installed on the server, which was completed by Infrastructure. The customer facing functionality and use of the CFXPayFlowPro tag should not change.

Miva

Miva customers will need to update their PayFlow Pro module to at least v4.2403. Instructions can be found here:

https://support.mivamerchant.com/supportsuite/index.php?_m=downloads&_a=viewdownload&downloaditemid=46

Classic ASP

Customers using ASP must use the HTTPS interface, using the examples above. If they are using ASP on a .NET server, they can also use the .NET methods on a .NET page. The usual restrictions apply -- pages using .NET must be an ASPX page, which can not include ASP code. Basically, this is a rewrite in .NET.

.NET

.NET customers should download the new .NET SDK and compile this into their application. For customers on a Medium Trust server (which will eventually be all servers) there are restrictions which will interfere with their connection. This is being whitelisted on the server as an allowed connection, and should not cause problems.