Adyen Connector

Connect Adyen so Applied can look up payment context and run guided payment workflows such as refunds.

Use this Connector when support conversations depend on Adyen payment status, merchant accounts, or post-payment actions that should happen only after a customer or teammate confirms the request.

Common use cases

Look up Adyen payment and refund context.
Issue a refund after approval.
Track refund, failed refund, and reversed refund webhook events.
Route payment issues to the right team with the Adyen payment reference.

For money-moving actions, start with test credentials and use a Flow that captures approval before calling Adyen.

Before you begin

Before connecting Adyen, make sure:

You can access the Adyen Customer Area.
Your Adyen user has permission to manage API credentials.
You know the merchant account Applied should use.
You know whether this Connector should use the test or live environment.
If using live mode, you know the live URL prefix for Checkout API calls.

If your company has multiple merchant accounts, create one Connector per merchant account that Applied should operate against.

Get an Adyen API key

Adyen API keys are managed in Customer Area API credentials.

In Adyen Customer Area, select your company account.
Go to Developers > API credentials.
Open the Payments or Platforms tab.
Select the API credential username, or create a new web service user.
Under Server settings > Authentication, open the API key tab.
Generate and copy the API key.
Save the credential changes.

Copy the key immediately. Adyen does not show the full API key again after you leave the page.

Configure Adyen access

Adyen controls API access through roles on the API credential. Use the narrowest roles that cover the workflows Applied will run.

Common roles include:

Merchant PAL webservice role for payment API requests.
Checkout webservice role for Checkout API operations.
Merchant Recurring role only if Applied needs saved or recurring payment details.
Management API - Account read if Applied needs to list merchant accounts.
Management API - Webhooks read and write if Applied support helps manage webhook configuration.

Also confirm the API credential account scope. A credential created at the company account can access linked merchant accounts; a merchant-account credential is limited to that merchant account.

For live Adyen connections, get the live URL prefix from Developers > API URLs in the live Customer Area. Paste only the prefix value, not the full URL.

Connect Adyen in Applied

Open Connectors.
Click New.
Choose Adyen.
Enter the merchant account.
Choose test or live for the environment.
If using live mode, enter the live URL prefix.
Paste the Adyen API key into the API token field.
Create the connection.

Applied uses the merchant account and environment to send Checkout API requests to the correct Adyen endpoint.

Validate the connection

After setup:

Use a test payment or low-risk record to confirm Applied can reach Adyen.
Confirm the merchant account in the result matches the intended account.
If refund actions are enabled, run a test refund in the Adyen test environment before using live credentials.
If webhooks are enabled, confirm refund events are received in Applied.

Do not validate refunds against live payments unless your team is ready for the refund to happen.

Common issues

Adyen says the API key is invalid

Confirm the key was copied from Developers > API credentials and that the Connector environment matches the Customer Area where the key was created. Test and live Adyen credentials are separate.

Live requests fail

Check the live URL prefix. The Connector needs the prefix from Adyen’s live API URLs page, not the entire Checkout API URL.

Refunds or lookups fail with permission errors

Review the API credential roles and merchant-account scope. The credential must have the roles for the specific Adyen API operation and access to the merchant account entered in Applied.