Important Data

for forter to make the strongest decision on whether a transaction is fraud, abuse, or requires additional verification measures, there are five (5) key areas of information to provide about the transaction at checkout if you're unable to provide any of these data points at checkout, reach out to your forter solutions consultant or implementation engineer to discuss the impact to your integration 1\ basic transaction details data point parameter notes order id orderid order channel ordertype website, mobile app, etc checkout datetime checkouttime order amount totalamount promotions applied totaldiscount or discounts important for abuse prevention whether payment authorization has been requested authorizationstep 2\ who is placing the order? accountowner the accountowner object should include information about the ordering customer, even if the customer is checking out as a guest data point parameter notes name fullname or firstname and lastname email email account id accountid not applicable to guest checkout account creation datetime created not applicable to guest checkout connectioninformation we also collect information about how the user is interacting with your site in the connectioninformation object data point parameter notes frontend token fortertokencookie or fortermobileuid ip address customerip user agent useragent 3\ what are they purchasing? cartitems list the items the customer is purchasing is included in the cartitems array data point parameter notes item name basicitemdata name item quantity basicitemdata quantity item price basicitemdata price item type basicitemdata type whether the item is tangible/physical or intangible/digital product id basicitemdata productid important for abuse prevention in addition to the basic details on the cart items, include additional vertical specific details in the itemspecificdata object with each item if the item is sold through a marketplace, include details on the seller as well complete objects can be found in the order api https //docs forter com/reference/order v3 reference 4\ where will the items be sent? deliverydetails if the order will have a single delivery type and destination, use the primarydeliverydetails object at the order level if the order will be split into multiple delivery types or destinations, list the details at the item level in cartitems deliverydetails data point parameter notes delivery type primarydeliverydetails deliverytype or cartitems deliverydetails deliverytype whether the delivery is physical or digital or a combination delivery channel primarydeliverydetails deliverymethod or cartitems deliverydetails deliverymethod ground shipping, same day delivery, email, store pickup, etc primaryrecipient / beneficiaries if there is one recipient for the entire order, you can use the primaryrecipient object at the order level if the order has multiple recipients, list them at the item level in the cartitems beneficiaries this is particularly relevant for items like air travel tickets, where each ticket is assigned to a passenger even if the order is delivered to a single email address data point parameter notes shipping email primaryrecipient personaldetails email or cartitems beneficiaries personaldetails email for digital deliveries to an email shipping address primaryrecipient address or cartitems beneficiaries address for physical deliveries; use store address for store pickup shipping phone primaryrecipient phone or cartitems beneficiaries phone for courier deliveries and digital deliveries via sms 5\ how are they paying? payment include an object in the payment array for each payment method used along with the amount charged to that method depending on the type of payment method, you'll need to include different information within the object the following applies to creditcard and digital wallets with credit card as the underlying payment method, such as applepay and androidpay data point parameter notes bin bin last four card digits lastfourdigits expiration date expirationmonth and expirationyear name on card nameoncard for paypal payments, include payeremail and payerid billingdetails include billingdetails within each payment method object since they may differ from the customer initiating the purchase and the recipient data point parameter notes billing address address billing phone phone verificationresults if you are requesting a decision post authorization, also include the authorization results from the payment processor within the payment method object orders where payment was rejected by the processor (no auth orders) should still be sent to forter in order to include these attempts in the decision model, though they will automatically receive a "not reviewed" decision from forter data point parameter notes payment processor paymentprocessordata processorname processor transaction id paymentprocessordata processortransactionid important for tracking disputes authorization code verificationresults authorizationcode or processorresponsecode or processorresponsetext avs result verificationresults avsfullresult or avsstreetresult and avszipresult in countries where address is verified cvv result verificationresults cvvresult 3ds status verificationresults threedsstatus or ecivalue or cavvvalue for paypal payments, include paymentstatus