X-Payments:API - Revision history

Dohtur: /* See also */

2019-01-03T09:52:18Z

‎See also

Dohtur at 14:13, 28 June 2018

2018-06-28T14:13:12Z

Dohtur at 14:21, 23 April 2018

2018-04-23T14:21:44Z

Dohtur: /* API versions supported */

2018-04-23T14:15:47Z

‎API versions supported

Dohtur at 16:51, 29 June 2017

2017-06-29T16:51:51Z

Dohtur at 15:53, 23 January 2017

2017-01-23T15:53:05Z

Dohtur at 09:53, 27 December 2016

2016-12-27T09:53:14Z

Dohtur at 09:26, 27 December 2016

2016-12-27T09:26:42Z

Dohtur: /* Code samples */

2016-12-07T10:59:18Z

‎Code samples

Dohtur: /* Code samples */

2016-12-02T15:44:34Z

‎Code samples

@@ Line 231: / Line 231: @@
 ==See also==
-* [http://lu53.crtdev.local/%7Emixon/google-cache-w.php?q=/index.php?title=X-Cart:X-Payments_Connector X-Cart:X-Payments Connector]
+* [https://www.x-payments.com/help/Main_Page#X-Payments_connection_manuals X-Payments connection manuals]
 [[Category:X-Payments Developer Guide]]

@@ Line 110: / Line 110: @@
 TTL should be specified depending on the performance of the server where X-Payments is installed. The recommended value is 120 seconds.
-Use the latest TLSv1.2, since the previous protocols and implementations contain security vulnerabilities, and thus must not be used according to PA-DSS.
+Use the latest TLSv1.2, since the previous protocols and implementations contain security vulnerabilities, and thus must not be used according to PCI DSS.
 <div id="DataTypes"></div>

@@ Line 10: / Line 10: @@
 '''API v1.7''': X-Payments 3.0.2 (August 2016)<br />
 '''API v1.8''': X-Payments 3.1.0 (July 2017)<br />
 <div id="APIrequests"></div>

@@ Line 9: / Line 9: @@
 '''API v1.6''': X-Payments 3.0.0 (June 2016)<br />
 '''API v1.7''': X-Payments 3.0.2 (August 2016)<br />
 <div id="APIrequests"></div>
 ==API requests==

@@ Line 202: / Line 202: @@
 :* To simplify the code, some sensitive information (like the private key and the private key passphrase) was hard-coded in the script. This way, storing the keys "as is" is ''strongly not recommended''. Instead, the keys should be stored encrypted in some way.
 :* For the salt generation, the openssl_random_pseudo_bytes() function is used. However, it has known issues; make sure it generates a cryptographically secure sequence. Please check: https://bugs.php.net/bug.php?id=70014. If necessary, you may use another way to generate a cryptographically secure random string. See: http://stackoverflow.com/questions/31492921/cryptographically-secure-random-string-function.
-:* The keys hard-coded in the sample are taken from the X-Payments installation at https://demo.x-checkout.com. So some operations work out of the box, e.g. [[X-Payments:Payment_initialisation_request | payment initialization]], [[X-Payments:Payment_information_request | payment information]], [[X-Payments:Test_connection_request | test request]], [[X-Payments:Payment_configurations_list_request | obtaining payment configurations]], etc. But some operations will give an error, since the actual payment information on the demo stand can be changed. This applies to secondary operations: [[X-Payments:Capture_authorized_transaction_request | capture]], [[X-Payments:Void_authorized_transaction_request | void]], [[X-Payments:Refund_captured_transaction_request | refund]], etc. To see the successful result, you should change the '''txnId''' fields hard-coded in the scripts.
+:* The keys hard-coded in the sample are taken from the X-Payments installation at https://demo.xpayments.com. So some operations work out of the box, e.g. [[X-Payments:Payment_initialisation_request | payment initialization]], [[X-Payments:Payment_information_request | payment information]], [[X-Payments:Test_connection_request | test request]], [[X-Payments:Payment_configurations_list_request | obtaining payment configurations]], etc. But some operations will give an error, since the actual payment information on the demo stand can be changed. This applies to secondary operations: [[X-Payments:Capture_authorized_transaction_request | capture]], [[X-Payments:Void_authorized_transaction_request | void]], [[X-Payments:Refund_captured_transaction_request | refund]], etc. To see the successful result, you should change the '''txnId''' fields hard-coded in the scripts.

@@ Line 67: / Line 67: @@
 where:
-  - CART_ID is the Store ID;
+  - <CART_ID> is the Store ID;
-  - REQUEST is the encrypted XML
+  - <REQUEST> is the encrypted XML

@@ Line 175: / Line 175: @@
 To use the code samples:
-# Download the [[File:x-payments.api.samples.zip | archive with code samples]].
+# Download the [http://s.x-cart.com/xp_api_samples archive with code samples].
 # Upload it on the server.
 # Extract the files and execute the script as follows:

@@ Line 211: / Line 211: @@
 :* To simplify the code, some sensitive information (like the private key and the private key passphrase) was hard-coded in the script. This way, storing the keys "as is" is ''strongly not recommended''. Instead, the keys should be stored encrypted in some way.
 :* For the salt generation, the openssl_random_pseudo_bytes() function is used. However, it has known issues; make sure it generates a cryptographically secure sequence. Please check: https://bugs.php.net/bug.php?id=70014. If necessary, you may use another way to generate a cryptographically secure random string. See: http://stackoverflow.com/questions/31492921/cryptographically-secure-random-string-function.
-:* The keys hard-coded in the sample are taken from the X-Payments installation at https://demo.x-checkout.com. So some operations work out of the box, e.g. payment initialization, payment information, test request, obtaining payment configurations, etc. But some operations will give an error, since the actual payment information on the demo stand can be changed. This applies to secondary operations: capture, void, refund, etc. To see the successful result, you should change the txnId fields hard-coded in the scripts.
+:* The keys hard-coded in the sample are taken from the X-Payments installation at https://demo.x-checkout.com. So some operations work out of the box, e.g. [[X-Payments:Payment_initialisation_request | payment initialization]], [[X-Payments:Payment_information_request | payment information]], [[X-Payments:Test_connection_request | test request]], [[X-Payments:Payment_configurations_list_request | obtaining payment configurations]], etc. But some operations will give an error, since the actual payment information on the demo stand can be changed. This applies to secondary operations: [[X-Payments:Capture_authorized_transaction_request | capture]], [[X-Payments:Void_authorized_transaction_request | void]], [[X-Payments:Refund_captured_transaction_request | refund]], etc. To see the successful result, you should change the '''txnId''' fields hard-coded in the scripts.
 <div id="AppendixAStatusCodes"></div>
 ==Appendix A. Status codes.==