---
title: Adyen Additional Disputes Webhook for Chargeback Recovery
slug: adyen-additional-disputes-webhook-for-chargeback-recovery
docTags: 
createdAt: 2026-06-01T13:20:12.573Z
---

If you are using Forter's Chargeback Recovery service or Coverage for Fraud Management, please set up an additional Dispute Webhook, forwarded to a different URL endpoint. 

:::::WorkflowBlock
:::WorkflowBlockItem
**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)

Be sure to log in to your "Live" account to access your production instance.

::Image[]{src="https://images.archbee.com/dYhsqkppjaUNAqFmds_Ny-_VDnRCzjid06F63HaOJWs-20250613-161845.png" size="46" width="800" height="797" darkWidth="800" darkHeight="797" position="flex-start" showCaption="false"}
:::

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

::Image[]{src="https://images.archbee.com/dYhsqkppjaUNAqFmds_Ny-4-8X0SsN9iVFBUi4b_K4w-20250613-161840.png" size="48" width="800" height="1346" darkWidth="800" darkHeight="1346" position="flex-start" showCaption="false"}

![](https://images.archbee.com/dYhsqkppjaUNAqFmds_Ny-6898C2D7QNKhJoFZ00Q5s-20250613-161842.png)

On the webhook options, select "Standard Notification" and click on the "Add" button

![](https://images.archbee.com/dYhsqkppjaUNAqFmds_Ny-ckt9Dx08OQkQPaYeaQWbB-20250613-161845.png)
:::

::::WorkflowBlockItem
**Configure the webhook**

:::hint{type="warning"}
You must reach out to your Forter Implementation Manager to get the correct URL to use for this webhook.
:::

Under General configuration details click on Server Configuration. Add the URL (provided by your Forter Implementation Manager), Method, Encryption Protocol, outlined in the image below and then click Apply.

![](https://images.archbee.com/dYhsqkppjaUNAqFmds_Ny-uQlTPZUXA-s0k8GlXjgmC-20250613-161841.png)

Click on All Merchant Accounts. Select the relevant merchant accounts and click Apply.

![Image](https://images.archbee.com/dYhsqkppjaUNAqFmds_Ny-b5A9l-ahpCHjGRtWFFfVZ-20250613-161840.png)
::::

:::WorkflowBlockItem
**Send merchant account codes to Forter POC **
:::

:::WorkflowBlockItem
**Select events**

Click on Events and select all on the bottom left corner. Click Apply on the bottom right corner.

![](https://images.archbee.com/dYhsqkppjaUNAqFmds_Ny-d5Fq1XXPzjtANwJ-A7EOx-20250613-161846.png)
:::

:::WorkflowBlockItem
**Set authentication**

In Security configuration: Generate the HMAC key by clicking the generate button and then copy the HMAC key.

![](https://images.archbee.com/dYhsqkppjaUNAqFmds_Ny-IXTfnoMW7zHORawBiMTLj-20250613-161840.png)

Click Apply and Save changes at the bottom of the page.
:::

:::WorkflowBlockItem
Send the HMAC to Forter via secure S3 bucket transfer. 

Ensure the credentials are saved under the file naming convention "JCBR-merchantName-processorName" where processorName is a placeholder for which processor these keys are for (ex. "JCBR-merchantName-Adyen")
:::
:::::