Difference between revisions of "X-Payments:Accept potentially fraudulent transaction request"

From X-Payments Help
Jump to: navigation, search
m
m
Line 37: Line 37:
 
</pre>
 
</pre>
  
===Response example===
+
===Response specification===
  
 
{| cellspacing="0" cellpadding="2" border="1"
 
{| cellspacing="0" cellpadding="2" border="1"
Line 53: Line 53:
 
|}
 
|}
  
Response example <pre><data>
+
===Response example===
 +
<pre>
 +
<data>
 
<status>1</status>
 
<status>1</status>
 
<message>Success</message>
 
<message>Success</message>

Revision as of 16:37, 17 November 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

Request specification

Field Required Type Description
target Y string, 128 Must equal payment
action Y string, 128 Must equal accept
txnId Y string, 32 Unique payment ID
api_version Y string Must equal one of the following: 1.2, 1.3, 1.4, 1.5 etc.

Request example

<txnId>e7f398cee98ec062abac0d2c937da181</txnId>
<target>payment</target>
<action>accept</action>

Response specification

Field Type Description
status integer, 1 Operation status code
message string, 65536 Gateway transaction message

Response example

<data>
<status>1</status>
<message>Success</message>
<error></error>
<error_message></error_message>
</data>