Difference between revisions of "X-Payments:Test connection request"

From X-Payments Help
Jump to: navigation, search
(Created page with "Use this request to test the connection between the store and X-Payments. It can also help to detect the version of the X-Payments installation and the API version supported b...")
 
m
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
<noinclude>{{XP_API_TOC}}</noinclude>
 
Use this request to test the connection between the store and X-Payments. It can also help to detect the version of the X-Payments installation and the API version supported by X-Payments.
 
Use this request to test the connection between the store and X-Payments. It can also help to detect the version of the X-Payments installation and the API version supported by X-Payments.
  
Line 34: Line 35:
  
 
<pre>
 
<pre>
<testCode>123</testCode>
 
<api_version>1.5</api_version>
 
 
<target>connect</target>
 
<target>connect</target>
 
<action>test</action>
 
<action>test</action>
 +
<testCode>123</testCode>
 
</pre>
 
</pre>
  
Line 72: Line 72:
  
 
Example of a good response:
 
Example of a good response:
<pre>
+
<pre style="overflow: scroll">
 
<data>
 
<data>
 
   <hashCode>202cb962ac59075b964b07152d234b70</hashCode>
 
   <hashCode>202cb962ac59075b964b07152d234b70</hashCode>
Line 78: Line 78:
 
   <error_message></error_message>
 
   <error_message></error_message>
 
   <is_error_message></is_error_message>
 
   <is_error_message></is_error_message>
   <version>2.2.0</version>
+
   <version>3.0.1</version>
 
</data>
 
</data>
 
</pre>
 
</pre>
  
 
Example of a response with an error:
 
Example of a response with an error:
<pre>
+
<pre style="overflow: scroll">
 
<data>
 
<data>
 
   <error>506</error>
 
   <error>506</error>

Latest revision as of 17:40, 26 July 2016

X-Payments API
  1. API versions supported
  2. Samples
  3. API requests
  4. API Requests from the store to X-Payments
    1. Admin area/X-Payments configuration
    2. Payment creation (Regular payment and tokenization)
    3. Payment information
    4. Actions on payments (secondary actions)
  5. Callback requests (web-hooks) from X-Payments to the store
  6. Browser-related
  7. Appendix A. Status codes.
  8. See also

Use this request to test the connection between the store and X-Payments. It can also help to detect the version of the X-Payments installation and the API version supported by X-Payments.

Request specification

Field Required Type Description
target Y string, 128 Must equal connect
action Y string, 128 Must equal test
testCode Y string, 128 Any string
api_version Y string Must equal one of the following: 1.2, 1.3, 1.4, 1.5 etc.


Request example

<target>connect</target>
<action>test</action>
<testCode>123</testCode>

Response specification

Field Type Description
hashCode string MD5 hash of the sent code
error string Error code (if any)
error_message string Error message
is_error_message string Flag indicating the error message presence
version string X-Payments version


Response example

Example of a good response:

<data>
  <hashCode>202cb962ac59075b964b07152d234b70</hashCode>
  <error></error>
  <error_message></error_message>
  <is_error_message></is_error_message>
  <version>3.0.1</version>
</data>

Example of a response with an error:

<data>
  <error>506</error>
  <error_message>Your X-Payments connector module supports API version "1.9". This X-Payments supports the following API versions only: "1.1, 1.2, 1.3, 1.4, 1.5, 1.6".</error_message>
  <is_error_message></is_error_message>
</data>