Stripe Dispute Webhook

how to provide forter access to your stripe dispute webhooks to enable forter to process your chargebacks, please integrate your psp with forter by following these steps required keys api key secret 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 paymentintent id (the value that starts with pi ) to the processortransactionid field in your order api or order status api request, when you send forter the payment authorization details the charge id (ch ) is also supported as a legacy alternative 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" "pi 3m7nab2ck0ffgl3iabc1defg", // paymentintent id assigned by stripe (recommended) "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 under "restricted keys", click + create restricted key typically, the key that is generated will start with rk live or sk live for your production environment set the following permissions charges → read customers → read files → write paymentintents → read paymentmethods → read invoices → read subscriptions → read disputes → write (under all core resources save the api key secret key to a txt file with the file naming convention "jcbr yoursitename processorname" (e g "jcbr tshirtsexpress stripe") keep this txt file open as you will add the webhook keys to it in the next steps 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 credentials section of forter portal https //portal forter com/app/integration/credentials/ copy the webhook signing secret after saving, click on your newly created webhook destination reveal and copy the signing secret (starts with whsec ) save the signing secret to a txt file that you had in step 3 "jcbr yoursitename processorname" (e g "jcbr tshirtsexpress stripe") 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 your forter implementation engineer will securely add your secret key to the forter database and let you know when this step is complete 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