X-Cart:Protx/Sage Pay API update - Revision history

Admin at 08:32, 12 April 2011

2011-04-12T08:32:09Z

Seyfin at 05:55, 8 October 2010

2010-10-08T05:55:25Z

Ivka at 11:39, 7 October 2010

2010-10-07T11:39:27Z

Seyfin at 05:59, 7 October 2010

2010-10-07T05:59:40Z

Seyfin at 05:09, 7 October 2010

2010-10-07T05:09:46Z

Ivka at 09:45, 9 September 2010

2010-09-09T09:45:42Z

Ivka at 09:44, 9 September 2010

2010-09-09T09:44:49Z

Ivka at 09:20, 9 September 2010

2010-09-09T09:20:25Z

Ivka at 05:05, 2 April 2010

2010-04-02T05:05:22Z

Ivka at 05:04, 2 April 2010

2010-04-02T05:04:46Z

@@ Line 1: / Line 1: @@
 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.
@@ Line 50: / Line 52: @@
 '''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 Qualiteam account:
+You can find the patch by the following path in the "File area" section of your {{QA}}:
 : 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

@@ Line 17: / Line 17: @@
 :: https://ukvps.protx.com:443/vspgateway/service/direct3dcallback.vsp
 : should be replaced with these URLs correspondingly:
-:: https://test.Sage Pay.com:443/Simulator/VSPDirectGateway.asp
+:: https://test.sagepay.com:443/Simulator/VSPDirectGateway.asp
-:: https://test.Sage Pay.com:443/gateway/service/vspdirect-register.vsp
+:: https://test.sagepay.com:443/gateway/service/vspdirect-register.vsp
-:: https://live.Sage Pay.com:443/gateway/service/vspdirect-register.vsp
+:: https://live.sagepay.com:443/gateway/service/vspdirect-register.vsp
-:: https://test.Sage Pay.com:443/Simulator/VSPDirectCallback.asp
+:: https://test.sagepay.com:443/Simulator/VSPDirectCallback.asp
-:: https://test.Sage Pay.com:443/gateway/service/direct3dcallback.vsp
+:: https://test.sagepay.com:443/gateway/service/direct3dcallback.vsp
-:: https://live.Sage Pay.com:443/gateway/service/direct3dcallback.vsp
+:: https://live.sagepay.com:443/gateway/service/direct3dcallback.vsp
 * payment/cc_protx.php (VSP Form)
 : the following URLs:
@@ Line 29: / Line 29: @@
 :: https://ukvps.protx.com/vspgateway/service/vspform-register.vsp
 : should be replaced with these URLs correspondingly:
-:: https://test.Sage Pay.com/Simulator/VSPFormGateway.asp
+:: https://test.sagepay.com/Simulator/VSPFormGateway.asp
-:: https://test.Sage Pay.com/gateway/service/vspform-register.vsp
+:: https://test.sagepay.com/gateway/service/vspform-register.vsp
-:: https://live.Sage Pay.com/gateway/service/vspform-register.vsp
+:: https://live.sagepay.com/gateway/service/vspform-register.vsp
 }}

@@ Line 1: / Line 1: @@
 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 SagePay 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://help.qtmsoft.com/images/b/b0/URLs.pdf Source and destination URLs]''
+: ''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.''
@@ Line 17: / Line 17: @@
 :: 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.Sage Pay.com:443/Simulator/VSPDirectGateway.asp
-:: https://test.sagepay.com:443/gateway/service/vspdirect-register.vsp
+:: https://test.Sage Pay.com:443/gateway/service/vspdirect-register.vsp
-:: https://live.sagepay.com:443/gateway/service/vspdirect-register.vsp
+:: https://live.Sage Pay.com:443/gateway/service/vspdirect-register.vsp
-:: https://test.sagepay.com:443/Simulator/VSPDirectCallback.asp
+:: https://test.Sage Pay.com:443/Simulator/VSPDirectCallback.asp
-:: https://test.sagepay.com:443/gateway/service/direct3dcallback.vsp
+:: https://test.Sage Pay.com:443/gateway/service/direct3dcallback.vsp
-:: https://live.sagepay.com:443/gateway/service/direct3dcallback.vsp
+:: https://live.Sage Pay.com:443/gateway/service/direct3dcallback.vsp
 * payment/cc_protx.php (VSP Form)
 : the following URLs:
@@ Line 29: / Line 29: @@
 :: 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.Sage Pay.com/Simulator/VSPFormGateway.asp
-:: https://test.sagepay.com/gateway/service/vspform-register.vsp
+:: https://test.Sage Pay.com/gateway/service/vspform-register.vsp
-:: https://live.sagepay.com/gateway/service/vspform-register.vsp
+:: https://live.Sage Pay.com/gateway/service/vspform-register.vsp
 }}
-Updating the Protx URLs to Sagepay URLs is the main, but not the only change. Protx/Sagepay also updated their integration protocol from version 2.22 to 2.23. Here is a quotation from the email received from SagePay:
+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.''
@@ Line 46: / Line 46: @@
 : ''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 to use the new protocol version 2.23. If you use an older version of X-Cart, we recommend you to update the SagePay/Protx integration in your X-Cart store. To do it, you should apply the corresponding patch.
+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:'''
@@ Line 56: / Line 56: @@
 : 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
-NOTE: 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.
+{{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.}}
 '''If you use older versions''', please contact our support team.

@@ Line 1: / Line 1: @@
 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 SagePay 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://help.qtmsoft.com/images/b/b0/URLs.pdf Source and destination URLs]''
@@ Line 34: / Line 34: @@
 }}
-But it is not the only change. Protx/Sagepay updated their validation rules:
+Updating the Protx URLs to Sagepay URLs is the main, but not the only change. Protx/Sagepay also updated their integration protocol from version 2.22 to 2.23. Here is a quotation from the email received from SagePay:
 : ''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:'''
+: ''How this affects you:''
 : ''We are implementing an update to the Sage Pay integration protocol on Friday the 29th of May 2009.''
@@ Line 46: / Line 46: @@
 : ''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.
+The SagePay/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 SagePay/Protx integration in your X-Cart store. To do it, you should apply the corresponding patch.
-If you use the older version of X-Cart, you need to update your store and apply the attached patches.
+'''For v.4.1.12, v.4.2.0 and v.4.2.1:'''
-'''For v4.2.1 and v4.2.0:'''
+You can find the patch by the following path in the "File area" section of your Qualiteam account:
-* upload the attached [http://help.qtmsoft.com/index.php?title=File:Func.cc_protx_common.php func.cc_protx_common.php] file to the <u>include/func</u> directory of your store. Make sure that the file name does not start with a capital letter, otherwise Protx payment method will not work after the patch has been applied.
+: 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 [http://help.qtmsoft.com/index.php?title=File:Protx_direct_42x.diff protx_direct_42x.diff] patch. If you use Protx Form, apply the [http://help.qtmsoft.com/index.php?title=File:Protx_form_42x.diff protx_form_42x.diff] patch
+: 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
-'''For 4.1.x:'''
+NOTE: 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.
-* upload the attached [http://help.qtmsoft.com/index.php?title=File:Func.cc_protx_common.php func.cc_protx_common.php] file to the <u>include/func</u> directory of your store. Make sure that the file name does not start with a capital letter, otherwise Protx payment method will not work after the patch has been applied.
+'''If you use older versions''', please contact our support team.
 [[Category:API updates]]
 [[Category:X-Cart user manual]]

@@ Line 40: / Line 40: @@
 '''How this affects you:'''
-We are implementing an update to the Sage Pay integration protocol on Friday the 29th of May 2009.
+: ''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
+: ''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
+: ''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.

@@ Line 3: / Line 3: @@
 A Sage Pay rep said:
-<div>: ''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 URL end points changes]''<ins>.</ins></div>
+: ''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 URL end points changes]''
 : ''But it is not an urgent change as both old and new URL end points will be active for the next 6 months.''