X-Payments:Decline potentially fraudulent transaction request - Revision history

Dohtur at 12:05, 24 April 2018

2018-04-24T12:05:16Z

Dohtur at 10:38, 21 November 2016

2016-11-21T10:38:01Z

Dohtur at 10:36, 21 November 2016

2016-11-21T10:36:27Z

Dohtur: Dohtur moved page X-Payments:Blocked by gateway transaction decline request (Decline) to X-Payments:Decline potentially fraudulent transaction request

2016-11-17T12:47:33Z

Dohtur moved page X-Payments:Blocked by gateway transaction decline request (Decline) to X-Payments:Decline potentially fraudulent transaction request

Dohtur at 13:44, 26 July 2016

2016-07-26T13:44:22Z

Dohtur: Created page with "===Request specification=== {| cellspacing="0" cellpadding="2" border="1" | colspan="1" | '''Field''' | colspan="1" | '''Required''' | colspan="1" | '''Type''' | colspan="1"..."

2016-07-20T08:35:19Z

Created page with "===Request specification=== {| cellspacing="0" cellpadding="2" border="1" | colspan="1" | '''Field''' | colspan="1" | '''Required''' | colspan="1" | '''Type''' | colspan="1"..."

New page

===Request specification===

{| cellspacing="0" cellpadding="2" border="1"
| colspan="1" | '''Field'''
| colspan="1" | '''Required'''
| colspan="1" | '''Type'''
| colspan="1" | '''Description'''
|-
| colspan="1" | target
| colspan="1" | Y
| colspan="1" | string, 128
| colspan="1" | Must equal payment
|-
| colspan="1" | action
| colspan="1" | Y
| colspan="1" | string, 128
| colspan="1" | Must equal decline
|-
| colspan="1" | txnId
| colspan="1" | Y
| colspan="1" | string, 32
| colspan="1" | Unique payment ID
|-
| colspan="1" | api_version
| colspan="1" | Y
| colspan="1" | string
| colspan="1" | Must equal one of the following: 1.2, 1.3, 1.4, 1.5 etc.
|}

===Request example===

<pre>
<txnId>e7f398cee98ec062abac0d2c937da181</txnId>
<target>payment</target>
<action>decline</action>
</pre>

===Response specification===

{| cellspacing="0" cellpadding="2" border="1"
| colspan="1" | '''Field'''
| colspan="1" | '''Type'''
| colspan="1" | '''Description'''
|-
| colspan="1" | status
| colspan="1" | integer, 1
| colspan="1" | [[#Operation status codes|Operation status code]]
|-
| colspan="1" | message
| colspan="1" | string, 65536
| colspan="1" | Gateway transaction message
|}

===Response example===

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

@@ Line 6: / Line 6: @@
 Currently, there are four cases that can put a transaction in the "potentially fraudulent" state:
- - [[X-Payments:KOUNT_Antifraud_screening|Kount Antifraud screening service]];
+:* [[X-Payments:KOUNT_Antifraud_screening|Kount Antifraud screening service]];
- - NoFraud screening;
+:* NoFraud screening;
- - Internal fraud screening by the gateway (PayPal, PayFlow PRO, etc);
+:* Internal fraud screening by the gateway (PayPal, PayFlow PRO, etc);
- - Internal fraud screening by X-Payments.
+:* Internal fraud screening by X-Payments.
 {{Note|Please contact your antifraud service provider for recommendations on how to handle transactions marked as potentially fraudulent. Deciding which transactions to accept and which to decline is a serious matter, and you must fully understand what you are doing before you accept anything.}}

← Older revision		Revision as of 10:36, 21 November 2016
Line 1:		Line 1:
	<noinclude>{{XP_API_TOC}}</noinclude>		<noinclude>{{XP_API_TOC}}</noinclude>
		+	In some cases, a transaction is considered potentially fraudulent, and the final decision as to whether it should be accepted or not has to be taken by the merchant. Or, in some cases, the information about the final result is sent to the merchant later by the anti-fraud checking service.
		+
		+	Such a state of the transaction is indicated by the isFraudStatus flag in the [[X-Payments:Payment_information_request\|Payment information request]], [[X-Payments:Detailed_payment_and_transaction_information_request\|Detailed payment information request]] and the [[X-Payments:Callback_request_with_service_payment_information\|callback request received from X-Payments]]. As of API 1.7, the detailed information on fraud check is sent in the fraudCheckData container.
		+
		+	Currently, there are four cases that can put a transaction in the "potentially fraudulent" state:
		+
		+	- [[X-Payments:KOUNT_Antifraud_screening\|Kount Antifraud screening service]];
		+	- NoFraud screening;
		+	- Internal fraud screening by the gateway (PayPal, PayFlow PRO, etc);
		+	- Internal fraud screening by X-Payments.
		+
		+	{{Note\|Please contact your antifraud service provider for recommendations on how to handle transactions marked as potentially fraudulent. Deciding which transactions to accept and which to decline is a serious matter, and you must fully understand what you are doing before you accept anything.}}
		+
	===Request specification===		===Request specification===

← Older revision		Revision as of 13:44, 26 July 2016
Line 1:		Line 1:
		+	<noinclude>{{XP_API_TOC}}</noinclude>
	===Request specification===		===Request specification===

@@ Line 64: / Line 64: @@
 | colspan="1" | string, 65536
 | colspan="1" | Gateway transaction message
 |}

← Older revision	Revision as of 12:47, 17 November 2016
(No difference)