Difference between revisions of "X-Cart:Protx/Sage Pay API update"

From X-Cart 4 Classic
Jump to: navigation, search
(Created page with '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 sai…')
 
m
 
(18 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{XC 4.1}} {{XC 4.2}}
 +
 
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.
 
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:
 
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 ''
+
: ''On the integration side of things there is a requirement to change the URL end points from Protx.com to SagePay.com: [http://help.qtmsoft.com/images/b/b0/URLs.pdf Source and destination URLs]''
−
 
 
−
''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:
+
: ''But it is not an urgent change as both old and new URL end points will be active for the next 6 months.''
  
−
''In order to continue to deliver high levels of security we recently performed an in-depth scan
+
{{Note1|<ins>Here are the specific </ins>URL end points changes <ins>that </ins>should be applied to your X-Cart installation:
−
of vendors who are passing invalid characters to the Sage Pay systems. We noticed that you are
+
* payment/cc_protxdir.php (VSP Direct)
−
one of these vendors and strongly advise you to update your integration as soon as possible.
+
: the following URLs:
−
Accepting invalid characters is not considered best practice and we are therefore updating
+
:: https://ukvpstest.protx.com:443/VSPSimulator/VSPDirectGateway.asp
−
our systems accordingly.
+
:: https://ukvpstest.protx.com:443/vspgateway/service/vspdirect-register.vsp
 +
:: https://ukvps.protx.com:443/vspgateway/service/vspdirect-register.vsp
 +
:: https://ukvpstest.protx.com:443/VSPSimulator/VSPDirectCallback.asp
 +
:: https://ukvpstest.protx.com:443/vspgateway/service/direct3dcallback.vsp
 +
:: https://ukvps.protx.com:443/vspgateway/service/direct3dcallback.vsp
 +
: should be replaced with these URLs correspondingly:
 +
:: https://test.sagepay.com:443/Simulator/VSPDirectGateway.asp
 +
:: https://test.sagepay.com:443/gateway/service/vspdirect-register.vsp
 +
:: https://live.sagepay.com:443/gateway/service/vspdirect-register.vsp
 +
:: https://test.sagepay.com:443/Simulator/VSPDirectCallback.asp
 +
:: https://test.sagepay.com:443/gateway/service/direct3dcallback.vsp
 +
:: https://live.sagepay.com:443/gateway/service/direct3dcallback.vsp
 +
* payment/cc_protx.php (VSP Form)
 +
: the following URLs:
 +
:: https://ukvpstest.protx.com/VSPSimulator/VSPFormGateway.asp
 +
:: https://ukvpstest.protx.com/vspgateway/service/vspform-register.vsp
 +
:: https://ukvps.protx.com/vspgateway/service/vspform-register.vsp
 +
: should be replaced with these URLs correspondingly:
 +
:: https://test.sagepay.com/Simulator/VSPFormGateway.asp
 +
:: https://test.sagepay.com/gateway/service/vspform-register.vsp
 +
:: https://live.sagepay.com/gateway/service/vspform-register.vsp
 +
}}
  
−
'''How this affects you:'''
+
Updating the Protx URLs to Sage Pay URLs is the main, but not the only change. Protx/Sage Pay also updated their integration protocol from version 2.22 to 2.23. Here is what an email received from Sage Pay says:
  
−
We are implementing an update to the Sage Pay integration protocol on Friday the 29th of May 2009.
+
: ''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.''
  
−
This update increases the stringency of the character validation checks performed on incoming transactions
+
: ''How this affects you:''
−
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
+
: ''We are implementing an update to the Sage Pay integration protocol on Friday the 29th of May 2009.''
−
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.
+
: ''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.''
  
−
If you use the older version of X-Cart, you need to update your store and apply the attached patches.
+
: ''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.''
  
−
'''For v4.2.1 and v4.2.0:'''
+
The Sage Pay/Protx integration was updated in X-Cart v.4.2.2 and higher to use the new protocol version 2.23. If you use an older version of X-Cart, we recommend you to update the Sage Pay/Protx integration in your X-Cart store. To do it, you should apply the corresponding patch.
  
−
* upload the attached ''func.cc_protx_common.php ''file to the ''include/func ''directory of your store
+
'''For v.4.1.12, v.4.2.0 and v.4.2.1:'''
−
* 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:'''
+
You can find the patch by the following path in the "File area" section of your {{QA}}:
  
−
* upload the attached ''func.cc_protx_common.php ''file to the ''include/func ''directory of your store
+
: X-Cart -> X-Cart supporting files for prev versions -> X-Cart 4.1 -> X-Cart 4.1.12 -> Updates and patches -> protx-sage_pay-patch-2010-05-28_4.1.12.tgz
−
* if you use Protx Direct, apply the ''protx_direct_41x.txt ''patch''. ''If you use Protx Form, apply the ''protx_form_41x.txt'' one
+
: X-Cart -> X-Cart supporting files for prev versions -> X-Cart 4.2 -> X-Cart 4.2.0 -> Updates and patches -> protx-sage_pay-patch-2010-05-28_4.2.0.tgz
 +
: X-Cart -> X-Cart supporting files for prev versions -> X-Cart 4.2 -> X-Cart 4.2.1-> Updates and patches -> protx-sage_pay-patch-2010-05-28_4.2.1.tgz
  
−
If you use v4.0.x or older, please contact our support team.
+
{{Note1|In X-Cart v.4.2.2, v.4.2.3 and v.4.3.0 some problems related to Sage Pay (Protx) payment gateway were fixed. Thus, we also created patches for these versions, which include the corresponding bug-fixes only. The patches can be found in the "File area" section as well.}}
  
−
'''Files:'''
+
'''If you use older versions''', please contact our support team.
−
* [[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]]
 
  
 
[[Category:API updates]]
 
[[Category:API updates]]
 
[[Category:X-Cart user manual]]
 
[[Category:X-Cart user manual]]

Latest revision as of 12:32, 12 April 2011

X-Cart 4.1or above
X-Cart 4.2or above

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: Source and destination URLs
But it is not an urgent change as both old and new URL end points will be active for the next 6 months.
Here are the specific URL end points changes that should be applied to your X-Cart installation:
  • payment/cc_protxdir.php (VSP Direct)
the following URLs:
https://ukvpstest.protx.com:443/VSPSimulator/VSPDirectGateway.asp
https://ukvpstest.protx.com:443/vspgateway/service/vspdirect-register.vsp
https://ukvps.protx.com:443/vspgateway/service/vspdirect-register.vsp
https://ukvpstest.protx.com:443/VSPSimulator/VSPDirectCallback.asp
https://ukvpstest.protx.com:443/vspgateway/service/direct3dcallback.vsp
https://ukvps.protx.com:443/vspgateway/service/direct3dcallback.vsp
should be replaced with these URLs correspondingly:
https://test.sagepay.com:443/Simulator/VSPDirectGateway.asp
https://test.sagepay.com:443/gateway/service/vspdirect-register.vsp
https://live.sagepay.com:443/gateway/service/vspdirect-register.vsp
https://test.sagepay.com:443/Simulator/VSPDirectCallback.asp
https://test.sagepay.com:443/gateway/service/direct3dcallback.vsp
https://live.sagepay.com:443/gateway/service/direct3dcallback.vsp
  • payment/cc_protx.php (VSP Form)
the following URLs:
https://ukvpstest.protx.com/VSPSimulator/VSPFormGateway.asp
https://ukvpstest.protx.com/vspgateway/service/vspform-register.vsp
https://ukvps.protx.com/vspgateway/service/vspform-register.vsp
should be replaced with these URLs correspondingly:
https://test.sagepay.com/Simulator/VSPFormGateway.asp
https://test.sagepay.com/gateway/service/vspform-register.vsp
https://live.sagepay.com/gateway/service/vspform-register.vsp

Updating the Protx URLs to Sage Pay URLs is the main, but not the only change. Protx/Sage Pay also updated their integration protocol from version 2.22 to 2.23. Here is what an email received from Sage Pay says:

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 Sage Pay/Protx integration was updated in X-Cart v.4.2.2 and higher to use the new protocol version 2.23. If you use an older version of X-Cart, we recommend you to update the Sage Pay/Protx integration in your X-Cart store. To do it, you should apply the corresponding patch.

For v.4.1.12, v.4.2.0 and v.4.2.1:

You can find the patch by the following path in the "File area" section of your X-Cart Account:

X-Cart -> X-Cart supporting files for prev versions -> X-Cart 4.1 -> X-Cart 4.1.12 -> Updates and patches -> protx-sage_pay-patch-2010-05-28_4.1.12.tgz
X-Cart -> X-Cart supporting files for prev versions -> X-Cart 4.2 -> X-Cart 4.2.0 -> Updates and patches -> protx-sage_pay-patch-2010-05-28_4.2.0.tgz
X-Cart -> X-Cart supporting files for prev versions -> X-Cart 4.2 -> X-Cart 4.2.1-> Updates and patches -> protx-sage_pay-patch-2010-05-28_4.2.1.tgz
In X-Cart v.4.2.2, v.4.2.3 and v.4.3.0 some problems related to Sage Pay (Protx) payment gateway were fixed. Thus, we also created patches for these versions, which include the corresponding bug-fixes only. The patches can be found in the "File area" section as well.

If you use older versions, please contact our support team.

Retrieved from "https://help.x-cart.com/index.php?title=X-Cart:Protx/Sage_Pay_API_update&oldid=5874"