X-Payments:Accept potentially fraudulent transaction request
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 Payment information request, Detailed payment information request and the 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:
- Kount Antifraud screening service;
- NoFraud screening;
- Internal fraud screening by the gateway (PayPal, PayFlow PRO, etc);
- Internal fraud screening by X-Payments.
|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.|
<txnId>e7f398cee98ec062abac0d2c937da181</txnId> <target>payment</target> <action>accept</action>
|status||integer, 1||Operation status code|
|message||string, 65536||Gateway transaction message|
|payment||container||(Only API 1.9) Container with Payment information|
<data> <status>1</status> <message>Success</message> <error></error> <error_message></error_message> </data>