Abuse Prevention Overview 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

Overview of Abuse Prevention at Checkout Integration

In order to integrate Abuse Prevention at checkout, you will to provide Forter with the relevant data as outlined in the Fraud Management Integration Guide.

Each policy type will require data to be provided

1. 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.) include the CompensationStatus Object, via the Order Status API.
   1. This is critical to be able to define targeted refund/ returns policies based on specific conditions even if applied at checkout.
   2. For INR policies related to service chargebacks - send chargeback data along with appropriate reason code via Dispute API.
2. Limited Item Abuse: To create policies related to limiting items, send BasicItemData Object as part of the Order API
3. Promotion Abuse: To create policies related to Promotions, send Discounts Object as part of Order API.
   1. Discounts Object allows you to send a single or multiple promotion/coupon codes in a single transaction.
4. Reseller Abuse: To create policies related to Resellers, no incremental data is required outside the Fraud Management integration.
   1. Confirm sending the following objects: paymentBilling, accountOwner, cartItems, paymentRecipient, payment
5. Reshipper Abuse:To create policies related to Reshippers, no incremental data is required outside the Fraud Management integration.
   1. Confirm sending the following fields: paymentRecipient.address.zip, cartItems.beneficiaries.address
6. 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.) include the CompensationStatus Object, via the Order Status API.
   1. This is critical to be able to define targeted refund/ returns policies based on specific conditions even if applied at checkout.
   2. For Returns policies related to service chargebacks - send chargeback data along with appropriate reason code via Dispute API.