Adyen Dispute Webhook

include pspreference value in payment auth details a unique identifier is generated by adyen during payment that differs from your orderid this is required to map the dispute back to the original transaction map adyen's pspreference to the processortransactionid field in your order or order status api request, when you send forter the payment authorization details if you are integrating pre auth and using the docid 4gnezu8tkl9dgt7vx0mul , you can skip this step 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" "6525704706182988", // unique id assigned by adyen "processorname" "adyen credit" }, "fullresponsepayload" {}, } log into the adyen portal log into the adyen chargeback portal https //ca live adyen com/ca/ca/login shtml set up a standard webhook notification once you have logged in, go to the developer tab and select the "webhooks" option and then click on the "create new webhook" button on the webhook options, select "standard notification" and click on the "add" button enable by default, the notification will be disabled click on the small toggle next to "disabled" so that the webhook is enabled configure the webhook under the description field, add a descriptive title such as "forter claims" under server configurations, use url https //api forter secure com/webhooks/adyen/\<your forter site id> using the site id from the https //portal forter com/app/integration/credentials/ method json encryption protocol tlsv1 2 in the events section, click on the "show all events" toggle on the upper right hand corner of the box this should automatically enable all standard events add authentication in the basic authentication section, enter username use the secret key provided by forter in the https //portal forter com/app/integration/credentials/ password the password value should be an empty string "" generate hmac key and share with forter in the hmac key section, click the "generate" button and then click on the "apply" button save the webhook credentials to a txt file with the file naming convention "jcbr yoursitename processorname" (e g "jcbr tshirtsexpress adyen") and https //portal forter com/app/integration/docs/secure file transfer please notify your forter implementation engineer once you have uploaded these files after you copy your hmac key, scroll to the bottom of the page and click on the save changes button test configuration after your forter implementation engineer has added your adyen hmac secret key, click on the "test configuration" button on the bottom of the same page from there, you can select the adyen account you would like to test you can select any test event from the dropdown "event" menu to test after clicking the "test" button, you should see a screen that shows a 200 ok response code and message that the event delivered successfully please let your forter implementation engineer know once you've successfully placed a test notification multiple adyen accounts if you have multiple instances of your website on your adyen account and a single forter portal site, please link all instances to the same webhook chargeback recovery if you are leveraging forter's chargeback recovery or coverage services, you will also need to set up and an docid\ qoc9pdghyxf5xkbh2xj78