X-Cart:Protx/Sage Pay API update

Protx changed its name to Sage Pay this spring. However, this change affects not just the name and the logo. There are slight changes in the products as well.

A Sage Pay rep said:

On the integration side of things there is a requirement to change the URL end points from Protx.com to Sagepay.com: http://protx.gtml1.com/Protxlz/Instances/Protxlz/documents/URLs.pdf

But it is not an urgent change as both old and new URL end points will be active for the next 6 months.

But it is not the only change. Protx/Sagepay updated their validation rules:

In order to continue to deliver high levels of security we recently performed an in-depth scan of vendors who are passing invalid characters to the Sage Pay systems. We noticed that you are one of these vendors and strongly advise you to update your integration as soon as possible. Accepting invalid characters is not considered best practice and we are therefore updating our systems accordingly.

How this affects you:

We are implementing an update to the Sage Pay integration protocol on Friday the 29th of May 2009.

This update increases the stringency of the character validation checks performed on incoming transactions to our systems, and is designed to ensure that transactions which include invalid characters are rejected.

This means that as of the 29th of May 2009 any transactions passed to Sage Pay that include invalid characters will be rejected. Your business will therefore be unable to process transactions after this date if no action is taken.

The SagePay/Protx integration was updated in X-Cart v.4.2.2 and higher. So if you use this or newer version of X-Cart, you don't need to modify anything.

If you use the older version of X-Cart, you need to update your store and apply the attached patches.

For v4.2.1 and v4.2.0:

• upload the attached func.cc_protx_common.php file to the include/func directory of your store
• if you use Protx Direct, apply the protx_direct_42x.txt patch. If you use Protx Form, apply the protx_form_42x.txt one

For 4.1.x:

• upload the attached func.cc_protx_common.php file to the include/func directory of your store
• if you use Protx Direct, apply the protx_direct_41x.txt patch. If you use Protx Form, apply the protx_form_41x.txt one

If you use v4.0.x or older, please contact our support team.

Files:

• File:Func.cc protx common.php
• File:Protx direct 42x.txt
• File:Protx form 42x.txt
• File:Protx direct 41x.txt
• File:Protx form 41x.txt