Braintree Dispute Webhook

include the braintree id value in payment auth details a unique identifier is generated by the braintree gateway and will typically be a 6 10 digit alphanumeric string that differs from your orderid this is required to map the dispute back to the original transaction map the braintree id value to the processortransactionid field in your order or order status api request, when you send forter the payment authorization details partial code example "payment" \[ { "billingdetails" {}, "creditcard" { "nameoncard" "jane smith", "bin" "442757", "lastfourdigits" "5149", "expirationmonth" "11", "expirationyear" "2024", "verificationresults" {}, "cardtype" "debit", "countryofissuance" "usa", "paymentprocessordata" { "processorname" "braintree", "processortransactionid" "gk1m4r2j" // unique id assigned by braintree } } } ] generate api key after logging into your braintree account, click on the small "gear" icon on the upper right hand corner and select "api" from the menu in the keys tab of the api page, click on the generate new api key button to generate a new set of keys including private key public key merchant id save all three credentials to a txt file with the file naming convention "jcbr yoursitename processorname" (e g "jcbr tshirtsexpress braintree") 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 create a webhook endpoint after uploading your api keys to your s3, click on the webhooks tab in your api settings and click on the create new webhook button add a new webhook endpoint with the following url https //api forter secure com/webhooks/braintree/\<your forter site id> using the site id from the credentials section of forter portal https //portal forter com/app/integration/credentials/ please make sure to add the siteid that corresponds to the braintree environment you're adding the webhook to (i e forter production site id to braintree production account, forter sandbox site id to braintree sandbox account) select the following options under the "disputes" section lost open won accepted disputed expired enable paypal chargebacks (if relevant) if you use braintree to process paypal transactions, please take the following additional steps to ensure we receive your paypal chargebacks through braintree click on the (gear) icon in the top right corner of the control panel click processing from the drop down menu scroll to the payment methods section next to paypal, click the options link check the box next to manage paypal disputes in the braintree control panel click edit next to each linked paypal account and check the box next to manage paypal disputes in the braintree control panel setting please enable this setting for each relevant paypal account to learn more, please see this braintree support article https //developer paypal com/braintree/articles/guides/payment methods/paypal/disputes on paypal disputes test the webhook once forter has confirmed that your webhook keys have been added, return to the webhooks section of your braintree admin and click on the "check url" option next to your webhook you should receive a 200/success response from the forter endpoint if you receive a 4xx response, please take a screenshot of your webhook settings and send to your forter implementation engineer know so that they can provide further troubleshooting instructions