Abuse Prevention

abuse prevention rides on the same checkout order call as fraud there's no separate endpoint or cartridge configuration the cartridge's job is to carry the order data and enforce whatever decision forter returns policies are defined entirely in the forter portal's policy builder a policy type (item not received, limited item, promotion/coupon, reseller, reshipper, or returns) paired with an action (decline or monitor) how each action is enforced decline is enforced exactly like a fraud decline, governed by the same fortercancelorderondecline setting and decline message see post auth flow # and pre auth flow # monitor takes no action the order proceeds, and forter records the policy hit for its own reporting identifying which policy fired when a decline is policy driven, the response includes merchantpolicyid , a guid identifying the policy builder policy that made the call it's stored as order custom fortermerchantpolicyid see getting the decision onto the order # for how decision fields land on the order fortermerchantpolicyid is empty on a fraud decline that wasn't policy driven check it on the order's attributes tab in business manager, under the forter group