Stripe Dispute Webhook

include stripe id value in payment auth details a unique identifier is generated by stripe during payment authorization that differs from your orderid this is required to map the dispute back to the original transaction map stripe's charge object id (the value that starts with ch ) to the processortransactionid field in your order or order status api request, when you send forter the payment authorization details partial code example "creditcard" { "nameoncard" "john smith", "bin" "424242", "lastfourdigits" "4242", "countryofissuance" "us", "expirationmonth" "03", "expirationyear" "2025", "verificationresults" { "authorizationcode" "a33244", "avsfullresult" "y", "processorresponsecode" "188502", "processorresponsetext" "authorised" }, "cardbrand" "visa", "paymentprocessordata" { "processortransactionid" "ch 1ev3dh2ck0ffgl3ixy4cutmw", // unique id assigned by stripe "processorname" "stripe" }, "fullresponsepayload" {}, } alternatively, you can include the fullresponsepayload object with the id key partial code example "fullresponsepayload" { "id" "ch 1ev3dh2ck0ffgl3ixy4cutmw", "object" "charge", "amount" 2295, "amount refunded" 0, "application" null, "application fee" null, "application fee amount" null, "balance transaction" "txn 1ev3di2ck0ffgl3iirzyhb40", "billing details" {} } go to the developers tab log into your stripe admin account and go to the developers tab generate an api key and share with forter generate a secret key that will be used by forter to authenticate the source of the data this key should have write permissions for (1) disputes (2) files resources typically, the key that is generated will start with rk live or sk live for your production environment to generate this key, click on the “api keys” section under the developers tab and go to the restricted keys section save the signing secret to a txt file with the file naming convention "jcbr yoursitename processorname" (e g "jcbr tshirtsexpress stripe") and https //portal forter com/app/integration/docs/secure file transfer please notify your forter implementation engineer once you have uploaded these files your forter implementation engineer will securely add your secret key to the forter database and let you know when this step is complete configure a new webhook navigate to the webhooks section and select add endpoint add a new webhook endpoint with the following url https //api forter secure com/webhooks/stripe/``\<site id> using the site id from the https //portal forter com/app/integration/credentials/ test the endpoint after your forter team has encrypted and added your stripe secret key to the forter database, please test the endpoint url to confirm a 200/success response from the forter server if you're able to set up a sandbox stripe webhook for your forter sandbox environment, you can reference stripe's list of test cards and procedure to generate a dispute in their sandbox please place an order with one of their test cards to test a dispute in sandbox