User Guide

Customizing Websites to use Fraud Management Filters
Migration From Risk Controls
40 June 23, 2009 Fraud Management Filters
{
// Useful information to be kept:
// DPRes.FMFDetails.DenyFilters[x].Description;
// DPRes.FMFDetails.DenyFilters[x].Id;
// DPRes.FMFDetails.DenyFilters[x].Name;
}
}
}
}
else
{
// Unexpected ACK type. Log response and inform the buyer that the
// transaction must be manually investigated.
}
Migration From Risk Controls
Unlike Risk Controls, Fraud Management Filters do not return risk-related error codes for the
DoAuthorization and DoCapture API operations. If you have previously programmed
checks for risk controls after these operations, you may need to change your business logic.
You must handle error codes related to FMF in the response of the DoDirectPayment,
DoExpressCheckoutPayment, DoReferenceTransaction, and BillUser API
operations. These error codes are different than error codes associated with Risk Controls.