Abuse at Checkout

abuse prevention policies at checkout forter supports the following policy types at checkout item not received (inr) abuse limited item abuse promotion abuse reseller abuse reshipper abuse returns inr abuse integration steps include required data in order to integrate abuse prevention at checkout, you will need to provide forter with the relevant data as outlined in the checkout integration docid\ zli8xrrlbmssvw0jlvxqb , post purchase updates docid\ kboks dbapjvvc0r5csre , and dispute notifications docid\ dcfboyebigyyebqkr9yqj sections item not received abuse to create policies related to item not received including appeasements (ie form of compensation to appease an end customer such a free item, store credit, etc ) send an order status api request that includes the compensationstatus object this is critical to be able to define targeted refund/returns policies based on specific conditions even if applied at checkout for inr policies related to service chargebacks, also send chargeback data along with appropriate reason code via dispute api limited item abuse send basicitemdata as part of the order api promotion abuse send the discounts object as part of order api be sure to use the discounts object, and not totaldiscount , in order to include multiple promotion/coupon codes in a single transaction reseller abuse send the following objects as part of order api payment , primarydeliverydetails , primaryrecipient , accountowner , cartitems reshipper abuse send the following fields as part of order api paymentrecipient address zip , cartitems beneficiaries address returns abuse to create policies related to returns including appeasements (ie form of compensation to appease an end customer such a free item, store credit, etc ) send an order status api request that includes the compensationstatus object this is critical to be able to define targeted refund/returns policies based on specific conditions even if applied at checkout for returns policies related to service chargebacks, also send chargeback data along with appropriate reason code via dispute api handle policy decisions from the order api response when creating policies, you can elect to receive a decline decision or a recommendation when a transaction meets the policy criteria, in the api response the recommendation response will vary based on the policy type defined in order to test your handling of abuse policy recommendations, use the corresponding email address below in the accountowner object within the api request customer email order v3 response test limited item solution\@forter com "recommendation" "monitor potential limited item abuse" test coupon solution\@forter com "recommendation" "monitor potential coupon abuse" test item not received solution\@forter com "recommendation" "monitor potential inr abuse" test return solution\@forter com "recommendation" "monitor potential return abuse" the response will also include a merchantpolicyid field the unique id that forter assigns to a policy when a user creates a policy in policy builder the id can be used in downstream systems to have custom flows if the decision was not influenced by a user defined policy, then the field will return a blank string send compensation requests as part of post purchase updates docid\ kboks dbapjvvc0r5csre , include compensation requests in your order status api updates to forter this will not return a decision, but provides valuable information to inform our decision models and enable return/inr policy decisions important data for this purpose includes orderid of the full reservation details sent via order api correlationid to the corresponding compensation request (when applicable) compensationstatus the main object that contains all relevant data about the compensation including the type of compensation that was requested by the consumer (e g replacement, refund, return etc ) the channel through which the request was made, for returns, the items being returned the reason provided for the request (e g changed my mind) the return method granted the return condition of the item back to the merchant distribution center (eg damaged) it is critical to map your internal returns data to forter’s fields and enums on the itemcompensationstatus in order to define targeted refund/ returns policies based on specific conditions dispute notifications docid\ dcfboyebigyyebqkr9yqj confirm that you are sending all disputes to forter through webhooks from your psp or the dispute api forter uses prior chargeback data to evaluate future refund requests as well as enforce item not received and returns policies at checkout and post purchase prepare and upload historical data docid\ y6pmf 8whdvom7pogm7ea to ensure the highest level of accuracy for our decisioning model, forter customizes our model to fit the specific risk profile of each of our customers we achieve this by training the model with your past compensation data in order to provide you with better accuracy from day 1 provide 1 year historical data for returns and inr, where possible, so that inr & returns policies can take effect immediately, and velocity counters take into consideration prior returns/inr refunds