Dispute Notifications

notifying forter of chargebacks and fraud alerts is extremely important because it enables forter’s system to learn and continually improve future decisions, tailoring our system to your company’s needs it is also required for chargeback recovery and coverage services to make sure forter knows which chargebacks have been submitted and should be reimbursed or appealed include processor specific ids in your order api request when your psp sends the dispute information to forter, they will generally include an unique id specific to their system and may not include the same order id that was provided in the initial call to forter's order api be sure that your order api request includes this processor specific id in the paymentprocessordata object this will allow forter to connect the dispute to the existing order in our system setup a webhook per psp for each of your psps, follow the instructions to set up a dispute webhook webhook configurations are mandatory for processors that offer webhook capabilities forter can accept dispute webhook notifications from adyen https //docs forter com/adyen dispute webhook , braintree https //docs forter com/braintree dispute webhook , checkout com hub https //docs forter com/checkout hub dispute webhook , checkout com nas https //docs forter com/checkout nas platform dispute webhook , paypal https //docs forter com/paypal dispute webhook primer https //docs forter com/primer dispute webhook , and stripe https //docs forter com/stripe dispute webhook once implemented, save the webhook credentials to a txt file with the file naming convention "jcbr yoursitename processorname" (e g "jcbr tshirtsexpress primer") and upload it securely to your s3 folder https //portal forter com/app/integration/docs/secure file transfer please notify your forter implementation engineer once you have uploaded these files send notification via dispute api if any of your psps are not supported through webhooks, use the dispute api https //docs forter com/reference/dispute to send each notification key fields in the requests include orderid/matching transaction id the id that corresponds to the original transaction that forter received amount of the claim claim currency the currency the claim is generated in reason code the code provided by the payment processor (from the list of card scheme codes) to determine if the chargeback is due to fraud or service issues processorchargebackcaseid the unique identifier of the claim that can be used for disputing it type of claim (e g chargeback, fraud alert) additionalcost any supplementary fees associated with the chargeback status of the claim (e g open / won / lost) sourcetype of the claim (e g processor cb) and sourcedetails (e g worldpay) issue date of the chargeback due date to dispute the chargeback dispute api request example { "orderid" "4306795", "processorchargebackcaseid" "cb 4343343219", "status" "open", "externalclaimstatus" "pending merchant response", "amount" { "amountusd" "99 95", "amountlocalcurrency" "105 55", "currency" "cad" }, "additionalcost" { "amountusd" "99 95", "amountlocalcurrency" "105 55", "currency" "cad" }, "type" "chargeback", "sourcetype" "processor cb", "sourcedetails" "ups", "reasontype" "fraud", "reason" "fraudulent transaction card not present environment", "reasoncode" "83", "issuedate" "2016 01 20", "duedate" "2016 01 30", "goodsrecovered" false, "wasrefunded" false, "invoiceurl" "mystore com/invoices/abc123", "comments" "contacted customer via phone" } ' dispute api response the response details whether or not the dispute was received successfully chargebacks will also show on the original transaction in the forter portal and can be included in relevant claims reporting in the portal as well