User Guide

Customizing Websites to use Fraud Management Filters
Detecting Pending Transactions Using the PayPal API
36 June 23, 2009 Fraud Management Filters
SOAP Example
The SOAP response would contain PaymentStatus set to Pending and the response would
also contain the following fields:
...
<ack>
<__value__>
<m__value>SuccessWithWarning</m__value>
</__value__>
</ack>
...
<errors>
<com.paypal.soap.api.ErrorType>
<shortMessage>Payment Pending your review in Fraud Management
Filters</shortMessage>
<longMessage></longMessage>
<errorCode>
<m__value>11610</m__value>
</errorCode>
<severityCode>
<__value__>
<m__value>Warning</m__value>
</__value__>
</severityCode>
<____hashCodeCalc>false</____hashCodeCalc>
</com.paypal.soap.api.ErrorType>
</errors>
...
Detecting Pending Transactions Using the PayPal API
You must detect an acknowledgment status of SuccessWithWarning and an error code of
11610 to identify a pending transaction. The payment status should be Pending.
The following simple example modifies the DoExpressCheckoutPayment.jsp sample in
the NVP SDK to support Fraud Management Filters. It does not handle the possibility that
more than one error code can be returned. The changes to the sample are noted: