Historical Data

why forter asks for your historical data 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 order and account data, including actual fraud outcomes, in order to provide you with better accuracy from day 1 to provide the best results, we require comprehensive historical data including many of the data points that are required for a live integration the timeframe for the requested data will depend on your traffic volume and the solutions you are leveraging this helps us to understand both new and established buyer patterns if for any reason you're unable to provide us with data covering the specified timeframe, you should notify your dedicated implementation manager who will provide guidance on a suitable path forward download a template below, you will find details on what historical data is relevant to share with forter, including a csv example that may serve as a template each header column in the template maps to a parameter in our api, so you can use the api reference https //docs forter com/reference for formatting requirements and enum options for each field a few fields that are specific to historical data are defined below upload file securely forter processes your historical order data offline using batch files in a csv format to ensure secure transmission of this data, please format your extracted data in the csv format provided and upload to a dedicated aws s3 folder that we have created for your account you can find instructions on how to set up your credentials and access the folder here https //portal forter com/app/integration/docs/secure file transfer order history forter requires 12 months of order data to account for spikes in traffic, promotional and seasonality effects order history should include traffic from payment methods even if they are excluded from decisioning, as well as any order attempts that resulted in payment authorization failure, were declined for fraud, or otherwise canceled the required data points include buyer information, cart items, payment methods, promotions used, as well as billing and shipping details, using the same fields as the order api the model also needs to know the fulfillment status of each order, as well as any declined transactions and related chargebacks or fraud notifications while fulfillment status would normally be provided in a subsequent call to the order status api in your live integration, please include it along with your order history under historicaldata status enum options are completed, canceled by merchant, canceled by customer in the case of transactions that were declined for suspicion of fraud, mark the order as historicaldata status = canceled by merchant and historicaldata fraud = declined for fraud in the case of transactions that were processed but a chargeback or fraud notification was later received, mark the order as historicaldata status = completed and use one of the following enums for historicaldata fraud fraud chargeback dispute submitted by the customer with a reason code of fraud, or a retrieval request otherwise known as a “soft chargeback” service chargeback dispute submitted by the customer for item not received or for not meeting the quality standard expected pre chargeback alert notification of an incoming dispute from a third party fraud refund complaint of fraud by the customer without a formal dispute if your fraud data is not available in the same system as your order history, you may upload this information separately please refer to the instructions below for dispute history build your template for order history, the specific columns to send to forter vary based on your particular integration to create a customized template, you can use the csv base template below and add the relevant columns for your relevant vertical and any payment methods base example order data (csv) accountowner accountid,accountowner created,accountowner email,accountowner firstname,accountowner lastname,cartitems\[0] basicitemdata name,cartitems\[0] basicitemdata quantity,cartitems\[0] basicitemdata category,cartitems\[0] basicitemdata price amountlocalcurrency,cartitems\[0] basicitemdata price amountusd,cartitems\[0] basicitemdata price currency,checkouttime,connectioninformation customerip,historicaldata fraud,historicaldata orderstatus,orderid,ordertype,payment\[0] billingdetails address address1,payment\[0] billingdetails address address2,payment\[0] billingdetails address city,payment\[0] billingdetails address country,payment\[0] billingdetails address region,payment\[0] billingdetails address zip,payment\[0] billingdetails personaldetails email,payment\[0] billingdetails phone\[0] phone,payment\[0] billingdetails personaldetails fullname,payment\[0] billingdetails personaldetails firstname,payment\[0] billingdetails personaldetails lastname,payment\[0] creditcard bin,payment\[0] creditcard expirationmonth,payment\[0] creditcard expirationyear,payment\[0] creditcard lastfourdigits,payment\[0] creditcard nameoncard,payment\[0] creditcard verificationresults ecivalue,payment\[0] creditcard verificationresults processorresponsecode,payment\[0] creditcard verificationresults processorresponsetext,primarydeliverydetails deliverymethod,primarydeliverydetails deliverytype,primaryrecipient personaldetails email,primaryrecipient phone\[0] phone,totalamount amountlocalcurrency,totalamount amountusd,totalamount currency e520 ba9a 367 60b,1415273168,john s\@test com,john,smith,white genericbrand handbag,1,apparel and accessories,105 55,99 95,cad,1699916780,10 0 0 127,service chargeback,completed,4306795,web,235 montgomery st ,ste 1110,san francisco,us,ca,2157 08 23,john s\@test com,15557654321,john smith,john,smith,42424242,3,2018,4242,john r h smith,5,d23,stolen card,usps ground mail,physical,john s\@test com,15557654321,105 55,99 95,cad add relevant columns for cart item details, based on the type of goods you sell retail primaryrecipient address address1,primaryrecipient address address2,primaryrecipient address city,primaryrecipient address zip,primaryrecipient address country,primaryrecipient address region 235 montgomery st ,ste 1110,san francisco,94104,us,ca gift cards cartitems\[0] beneficiaries\[0] personaldetails email,cartitems\[0] beneficiaries\[0] personaldetails firstname,cartitems\[0] beneficiaries\[0] personaldetails lastname,cartitems\[0] beneficiaries\[0] phone\[0] phone john s\@test com,john,smith,15557654321 tickets cartitems\[0] itemspecificdata ticketsandevents eventtime,cartitems\[0] itemspecificdata ticketsandevents eventname,cartitems\[0] itemspecificdata ticketsandevents eventvenuename,cartitems\[0] itemspecificdata ticketsandevents eventlocation address1,cartitems\[0] itemspecificdata ticketsandevents eventlocation zip,cartitems\[0] itemspecificdata ticketsandevents eventlocation city,cartitems\[0] itemspecificdata ticketsandevents eventlocation region,cartitems\[0] itemspecificdata ticketsandevents eventlocation country,cartitems\[0] itemspecificdata ticketsandevents eventtype,cartitems\[0] seller sellerdetails selleraccountcreationdate,cartitems\[0] seller sellerdetails sellerlastloginip ip,cartitems\[0] seller sellerdetails sellerpersonaldetails accountid,cartitems\[0] seller sellerdetails sellerpersonaldetails email 1420070400,fifa world cup final,maracana stadium,235 montgomery st ,94104,san francisco,ca,us,sports,1415273168,10 0 0 128,,john s\@test com accomodation cartitems\[0] itemspecificdata accommodation accommodationname,cartitems\[0] itemspecificdata accommodation numberofguests,cartitems\[0] itemspecificdata accommodation type,cartitems\[0] itemspecificdata accommodation accommodationaddress address1,cartitems\[0] itemspecificdata accommodation accommodationaddress address2,cartitems\[0] itemspecificdata accommodation accommodationaddress city,cartitems\[0] itemspecificdata accommodation accommodationaddress country,cartitems\[0] itemspecificdata accommodation accommodationaddress region,cartitems\[0] itemspecificdata accommodation accommodationaddress zip,cartitems\[0] itemspecificdata accommodation duration enddate,cartitems\[0] itemspecificdata accommodation duration startdate,cartitems\[0] itemspecificdata accommodation location city,cartitems\[0] itemspecificdata accommodation location country,cartitems\[0] itemspecificdata accommodation location region forter boutique hotel,2,hotel,235 montgomery st ,ste 1110,san francisco,us,ca,94104,2014 11 15,2014 10 28,san francisco,us,ca transportation cartitems\[0] itemspecificdata transport\[0] carrier,cartitems\[0] itemspecificdata transport\[0] duration endtime,cartitems\[0] itemspecificdata transport\[0] duration starttime,cartitems\[0] itemspecificdata transport\[0] endpoint roughlocation airportcode,cartitems\[0] itemspecificdata transport\[0] endpoint roughlocation city,cartitems\[0] itemspecificdata transport\[0] endpoint roughlocation country,cartitems\[0] itemspecificdata transport\[0] endpoint roughlocation region,cartitems\[0] itemspecificdata transport\[0] endpoint roughlocation seaportcode,cartitems\[0] itemspecificdata transport\[0] leg,cartitems\[0] itemspecificdata transport\[0] startpoint roughlocation airportcode,cartitems\[0] itemspecificdata transport\[0] startpoint roughlocation city,cartitems\[0] itemspecificdata transport\[0] startpoint roughlocation country,cartitems\[0] itemspecificdata transport\[0] startpoint roughlocation region,cartitems\[0] itemspecificdata transport\[0] startpoint roughlocation seaportcode,cartitems\[0] itemspecificdata transport\[0] type forter airlines,1420294711,1412345911,jfk,anytown,dk,new york,usnyc,2,jfk,anytown,dk,new york,usnyc,air travel marketplace cartitems\[0] seller sellerdetails selleraccountcreationdate,cartitems\[0] seller sellerdetails sellerlastloginip ip,cartitems\[0] seller sellerdetails sellerpersonaldetails accountid,cartitems\[0] seller sellerdetails sellerpersonaldetails email 1415273168,10 0 0 128,,john s\@test com food cartitems\[0] itemspecificdata food restaurantaddress address1,cartitems\[0] itemspecificdata food restaurantaddress address2,cartitems\[0] itemspecificdata food restaurantaddress city,cartitems\[0] itemspecificdata food restaurantaddress country,cartitems\[0] itemspecificdata food restaurantaddress region,cartitems\[0] itemspecificdata food restaurantaddress zip,cartitems\[0] itemspecificdata food restaurantid,cartitems\[0] itemspecificdata food restaurantname,primaryrecipient address address1,primaryrecipient address address2,primaryrecipient address city,primaryrecipient address zip,primaryrecipient address country,primaryrecipient address region 235 montgomery st ,ste 1110,san francisco,us,ca,94104,eh674df9,ron's steak house,235 montgomery st ,ste 1110,san francisco,94104,us,ca include relevant payment methods for your integration credit card is already included in the base csv apple pay payment\[0] applepay bin,payment\[0] applepay expirationmonth,payment\[0] applepay expirationyear,payment\[0] applepay lastfourdigits,payment\[0] applepay nameoncard ,3,2018,4242,john r h smith google pay payment\[0] androidpay bin,payment\[0] androidpay expirationmonth,payment\[0] androidpay expirationyear,payment\[0] androidpay lastfourdigits,payment\[0] androidpay nameoncard ,3,2018,4242,john r h smith paypal payment\[0] paypal payeremail,payment\[0] paypal payerid,payment\[0] paypal paymentstatus john s\@test com,fd000a45p,completed tokenized card payment\[0] tokenizedcard bin,payment\[0] tokenizedcard expirationmonth,payment\[0] tokenizedcard expirationyear,payment\[0] tokenizedcard lastfourdigits,payment\[0] tokenizedcard verificationresults processorresponsecode,payment\[0] tokenizedcard verificationresults processorresponsetext,payment\[0] tokenizedcard verificationresults ecivalue,payment\[0] tokenizedcard token ,3,2018,4242,d23,stolen card,5,tkn 77620c360132856a103477d2959967ab orders with multiple cart items for orders that have multiple cart items or multiple payment methods, which are represented in arrays, please follow one of the patterns below orderid,cartitems\[0] basicitemdata name,cartitems\[0] basicitemdata quantity,cartitems\[0] basicitemdata category,cartitems\[0] basicitemdata price amountusd,cartitems\[1] basicitemdata name,cartitems\[1] basicitemdata quantity,cartitems\[1] basicitemdata category,cartitems\[1] basicitemdata price amountusd,cartitems\[2] basicitemdata name,cartitems\[2] basicitemdata quantity,cartitems\[2] basicitemdata category,cartitems\[2] basicitemdata price amountusd,totalamount amountusd 4306795,white genericbrand handbag,1,apparel and accessories,99 95,brown genericbrand wallet,1,apparel and accessories,39 95,green genericbrand duffel,1,apparel and accessories,69 95,209 85orderid,cartitems\[] basicitemdata name,cartitems\[] basicitemdata quantity,cartitems\[] basicitemdata category,cartitems\[] basicitemdata price amountusd,totalamount amountusd 4306795,white genericbrand handbag,1,apparel and accessories,99 95,209 85 4306795,brown genericbrand wallet,1,apparel and accessories,39 95,209 85 4306795,green genericbrand duffel,1,apparel and accessories,69 95,209 85 dispute history forter requires 12 months of historical dispute data covering all of the order data provided most claims are issued within 90 days from the time of transaction as a result, dispute history is not expected to match the order history time frame perfectly if you were able to include dispute data in the historicaldata fraud field in your order history, you may skip this step if not, please share this data in an additional csv that includes the orderid from your order history file along with the reason string that was provided by the processor or claim source example dispute data (csv) orderid,reason 4306795,fraudulent transaction card not present environment signup history forter requires 6 to 12 months of historical account signup data signup history should contain the information provided by the customer as part of the registration process as well as data captured in the background such as account id, timestamp, and connection information the required data points use mostly the same fields as the signup api https //docs forter com/reference/signup given that the accounts could have been closed or suspended in that timeframe, forter also requests that you provide us with the current status of the account, though in your live integration this will be shared via account status api https //docs forter com/reference/account status the enum options for accountdata status are active, suspended, closed, guest, pending example signup data (csv) accountid,eventtime,signupstatus,connectioninformation customerip,connectioninformation useragent,connectioninformation merchantdeviceidentifier,accountdata personaldetails firstname,accountdata personaldetails lastname,accountdata personaldetails email,accountdata type,accountdata status e520 ba9a 367 60b,1415287568000,success,10 0 0 127,"mozilla/5 0 (windows nt 6 1; wow64) applewebkit/537 36 (khtml, like gecko) chrome/47 0 2526 73 safari/537 36",hgj7512345h3,john,smith,john s\@test com,business,active login history forter requires 6 months of historical account login data login history should contain all the information collected during login, such as the inputs entered by the customer, as well as data captured in the background such as timestamp, connection information, and the existing account details the required data points use mostly the same fields as the login api https //docs forter com/reference/login your dataset should include login attempts that resulted in failure, so that our models can learn from these as well the enum options for loginstatus are success, failed, blocked by merchant, account does not exist given that the accounts could have been closed or suspended since the login event, forter also requests that you provide us with the current status of the account, though in your live integration this will be shared via account status api https //docs forter com/reference/account status the enum options for accountdata status are active, suspended, closed, guest, pending example login data (csv) accountid,eventtime,connectioninformation customerip,connectioninformation useragent,connectioninformation merchantdeviceidentifier,loginmethodtype,loginstatus,userinput inputtype,userinput email,userinput phone,accountdata personaldetails firstname,accountdata personaldetails lastname,accountdata personaldetails email,accountdata created,accountdata type,accountdata status e520 ba9a 367 60b,1471171293,10 0 0 127,"mozilla/5 0 (windows nt 6 1; wow64) applewebkit/537 36 (khtml, like gecko) chrome/47 0 2526 73 safari/537 36",hgj7512345h3,password,success,email,john s\@test com,15557654321,john,smith,john s\@test com,1415287568000,business,closed compensation history forter requires 6 months of historical compensation request data compensation request history should contain the status and total compensation amount granted for the order, as well as details on each item included in the request note that the fields match the data structure in the order status api https //docs forter com/reference/order status , though you may be utilizing the compensation request api https //docs forter com/reference/compensation request in your live integration for orders that have multiple cart items, please follow one of the patterns below example compensation with items in columns (csv) orderid,eventtime,updatedstatus,compensationstatus totalgrantedamount amountusd,compensationstatus totalgrantedamount amountlocalcurrency,compensationstatus totalgrantedamount currency,compensationstatus itemstatus\[0] basicitemdata quantity,compensationstatus itemstatus\[0] basicitemdata price amountusd,compensationstatus itemstatus\[0] basicitemdata price amountlocalcurrency,compensationstatus itemstatus\[0] basicitemdata price currency,compensationstatus itemstatus\[0] basicitemdata productid,compensationstatus itemstatus\[0] basicitemdata name,compensationstatus itemstatus\[0] basicitemdata type,compensationstatus itemstatus\[0] statusdata updatedstatus,compensationstatus itemstatus\[0] statusdata compensationtypegranted,compensationstatus itemstatus\[0] statusdata reasoncategory,compensationstatus itemstatus\[1] basicitemdata quantity,compensationstatus itemstatus\[1] basicitemdata price amountusd,compensationstatus itemstatus\[1] basicitemdata price amountlocalcurrency,compensationstatus itemstatus\[1] basicitemdata price currency,compensationstatus itemstatus\[1] basicitemdata productid,compensationstatus itemstatus\[1] basicitemdata name,compensationstatus itemstatus\[1] basicitemdata type,compensationstatus itemstatus\[1] statusdata updatedstatus,compensationstatus itemstatus\[1] statusdata compensationtypegranted,compensationstatus itemstatus\[1] statusdata reasoncategory 2356fdse0rr489,1415287568000,sent,120 45,134 15,cad,1,99 95,105 55,cad,ag54352r7768kko,white genericbrand handbag,tangible,accepted by merchant,refund,wrong item,1,99 95,105 55,cad,ab54352r7768kko,black socks,tangible,accepted by merchant,refund,wrong item example compensation with items in rows (csv) orderid,eventtime,updatedstatus,compensationstatus totalgrantedamount amountusd,compensationstatus totalgrantedamount amountlocalcurrency,compensationstatus totalgrantedamount currency,compensationstatus itemstatus\[0] basicitemdata quantity,compensationstatus itemstatus\[0] basicitemdata price amountusd,compensationstatus itemstatus\[0] basicitemdata price amountlocalcurrency,compensationstatus itemstatus\[0] basicitemdata price currency,compensationstatus itemstatus\[0] basicitemdata productid,compensationstatus itemstatus\[0] basicitemdata name,compensationstatus itemstatus\[0] basicitemdata type,compensationstatus itemstatus\[0] statusdata updatedstatus,compensationstatus itemstatus\[0] statusdata compensationtypegranted,compensationstatus itemstatus\[0] statusdata reasoncategory 2356fdse0rr489,1415287568000,sent,120 45,134 15,cad,1,99 95,105 55,cad,ag54352r7768kko,white genericbrand handbag,tangible,accepted by merchant,refund,wrong item 2356fdse0rr489,1415287568000,sent,120 45,134 15,cad,1,20 5,28 6,cad,ab54352r7768kko,black socks,tangible,accepted by merchant,refund,wrong item