Adyen

Getting started

To successfully configure the integration, there are three data points that will need to be generated in Adyen then transferred to Signifyd. We recommend you have both your Adyen and Signifyd accounts open on separate tabs to make the information transfer as easy as possible. The data you will have to transfer to Signifyd:

Merchant account code
HMAC Key
API Key

💡
Adyen Permissions
Generating API keys requires you to have one of the following user roles within Adyen:
Merchant admin role
Manage API credentials

You'll first need to select the team that you want to configure within Signifyd. Log into your Signifyd account, navigate to the Settings → Integrations page. Select the Signifyd team you want to connect with Adyen using the dropdown in the top right corner of the integrations page.

Need to connect multiple Signifyd teams? See below for more information.

In Adyen, you have a primary company account and one or more sub-accounts referred to as merchant accounts. To properly set up the integration, the following steps must be configured at the merchant account level in Adyen.

Use the dropdown menu at the left to select the merchant account you wish to connect to Signifyd.

1. Merchant account code

At the company account level, select Settings > Account groups

Copy the merchant account and paste it into the Signifyd integrations page

💡
Account code
It is important to note that the merchant account is case sensitive. Please ensure that you copy the account code correctly into Signifyd to prevent the integration from failing.

2. Generate an API Key

Select Developers > API Credentials, and select the user that was created when setting up the Adyen account's API keys for Signifyd.
If you need to create new API credentials, follow the Adyen guidance for generating new API credentials .

Under Server settings > Authentication, click Generate API Key.

Copy the key from Adyen and paste it into the Signifyd integrations page

Setting permissions

When creating a new Configure API there are default permissions already set by Signifyd. To benefit from our dispute automation enhancements you will need to also enable API dispute management which is under the Uncategorized section.

The ability to toggle this feature will depend on the permissions you have been granted in Adyen. Please consult your Adyen admin if you are unable to view this permission in your Customer Area.

3. Generate HMAC key and Webhooks

In the same merchant account within Adyen, go to Developers > Webhooks.
Select + Create new webhook

Under Recommended webhooks > Standard Webhook select Add.

Under Server configuration enter the following information:
URL: https://adyen-webhooks.signifyd.com/dispute
Method: JSON
Encryption protocol: TLSv1.2

Under Additional Settings > Card, please select:
Include Card Holder
Include Card Bin

Generate your HMAC Key within webhook configuration

Under Security > HMAC Key > Select Generate

Copy the key from Adyen and paste it into the Signifyd integrations page.

Select Submit

If you are unable to successfully submit, please refer to our troubleshooting.

Return to Adyen and Save Configuration

Send a Test Notification to Signifyd

Now that we have completed the configuration, you can now test the webhook connection. This will verify the configuration with Signifyd is correct.

Within the webhooks configurations screen, select Test Configuration
Select either

AUTHORISATION
CHARGEBACK_REVERSED

Submit by clicking ‘Test’

Once successfully complete, notify your Implementations Manager to verify the integration is successful.

Connecting your Adyen account to multiple Signifyd teams
You can connect one Adyen user to multiple Signifyd teams by inputting the same merchant account code, HMAC Key and API Key across your chosen Signifyd teams. Simply select the team you wish to configure within Signifyd, copy and paste the credentials from Adyen and save changes. Repeat this process across all the Signifyd teams you wish to connect.

Connecting multiple Adyen accounts to one Signifyd team
If you wish to connect multiple Adyen merchant accounts to one Signifyd team, you will need to input the merchant account code, HMAC Key and API Key for each merchant account. Simply select the team you wish to configure within Signifyd, copy and paste the credentials from Adyen and save changes. Repeat this process for each Adyen merchant account, updating the form each time.

Troubleshooting

Generating new API Keys
If you have an existing integration and new API keys are generated, please ensure that you follow steps 1-3 to update your integration as we require the account code, API key and HMAC key to be updated in the integration page to save successfully.

Webhook Test troubleshooting

401: Unauthorized. Signifyd couldn’t connect because the credentials provided appear to be invalid. Double-check your configuration, and if needed, update or rotate your credentials to resolve the issue.

404: Not Found. Your endpoint could not be accessed. Please verify you are using the correct endpoint https://adyen-webhooks.signifyd.com/dispute when setting up the webhooks.

Invalid merchant account code
If you receive an error message with a response of [invalid merchant account code], this indicates that the account code supplied in Signifyd does not match the account name in Adyen.

How to resolve: Return back to the integrations page within Signifyd and re-enter the account code and API key. It is case sensitive, so it will have to be an exact match with the account name used within Adyen.

Invalid HMAC Key
If you encounter an error message stating [invalid HMAC key], it means there is a mismatch between the HMAC key configured in Signifyd and the HMAC key set up in Adyen, likely due to an input error.

How to resolve:
If you encounter an "Invalid HMAC" error, please generate a new HMAC key in your Adyen account and update it in Signifyd. Additionally, ensure your Merchant Account Code and API Key are correctly entered in Signifyd to resolve the issue.

Bad API Keys
If you are unable to save changes because of an invalid API key. Double-check your configuration, and if needed, update or rotate your credentials to resolve the issue.