# Adyen Dispute Webhook

How to provide Forter access to your Adyen Dispute Webhooks. To enable Forter to process your chargebacks, please integrate your PSP with Forter by following these steps.

## [Required Keys (Fraud Management Uncovered)](https://docs.forter.com/adyen-dispute-webhook#required-keys-fraud-management-uncovered) Required Keys (Fraud Management _Uncovered_)

1. Webhook + HMAC Key

## [Required Keys (Fraud Management Covered or Chargeback Recovery)](https://docs.forter.com/adyen-dispute-webhook#required-keys-fraud-management-covered-or-chargeba) Required Keys (Fraud Management _Covered_ or Chargeback Recovery)

*If you are leveraging Forter's Chargeback Recovery__**or**__Coverage services, you will also need to set up_[Adyen Additional Disputes Webhook for Covered/Chargeback Recovery](https://docs.forter.com/adyen-additional-disputes-webhook-for-chargeback-recovery) _and an_[Adyen API Key](https://docs.forter.com/adyen-api-key) *

1. Webhook + HMAC Key (this guide)
2. API Key (see here [Adyen API Key](https://docs.forter.com/adyen-api-key) )
3. Merchant Account Codes (see here [Adyen Additional Disputes Webhook for Covered/Chargeback Recovery](https://docs.forter.com/adyen-additional-disputes-webhook-for-chargeback-recovery)

**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 [Adyen Payment Webhook](https://docs.forter.com/adyen-payment-webhook) , you can skip this step.

Partial code example

```json
{
  "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",
      "processorName": "ADYEN_CREDIT"
    },
    "fullResponsePayload": {}
  }
}
```

**Log into the Adyen Portal**  
Log into the Adyen chargeback portal: [https://ca-live.adyen.com/ca/ca/login.shtml](https://ca-live.adyen.com/ca/ca/login.shtml "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 [Credentials section of Forter Portal](https://portal.forter.com/app/integration/credentials/ "Credentials section of Forter Portal")  
**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 [Credentials section of Forter Portal](https://portal.forter.com/app/integration/credentials/ "Credentials section of Forter Portal").  
**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 [upload it securely to your S3 folder](https://portal.forter.com/app/integration/docs/secure-file-transfer "upload it securely to your S3 folder"). 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.

**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.