Skip to main content
Who should use this guideThis guide is intended for merchants who:
  • Use Payrails as a payment orchestrator
  • Use Adyen Payments
  • Are approved to process raw card data
We use a server-to-server integration with Adyen, so your account must be enabled to process raw card data. If this isn’t enabled, payments won’t work in production. Please contact your Adyen account manager or support team to activate it._
  1. Email support@adyen.com and copy pcisupport@adyen.com. 2. Optionally copy the Payrails Support team. 3. In your request, confirm that Payrails will act as the payment orchestrator and handle card data processing. 4. Include:
  • The WS user associated with your Adyen account * The Payrails PCI compliance document

​
Create and configure an Adyen integration in Payrails

  1. Log in to the Payrails portal.
  2. Go to Settings → Integrations.
  3. Select Add instance to create a new Adyen integration configuration.
  4. Select the Workspaces where this integration should be available.
About WorkspacesWorkspaces determine where this integration is available. They let you isolate provider setups by region or business line, or share the same configuration across multiple Workspaces.

​
Step 1: Choose the integration type

  • Select Payment and continue to the next step.
A screenshot showing the integration type selection form.

​
Step 2: Choose the provider

  • Select Adyen and continue to the next step.
A screenshot showing the Adyen integration selected.

​
Step 3: Configure your Adyen integration

What you’ll need from AdyenBefore you begin, make sure you have access to:
  • Adyen merchant account name
  • Adyen API key (Web Service User)
  • Prefix (production only)
  • Webhook HMAC key
Log in to your Adyen merchant dashboard to complete this step.

​
Integration instance name

An integration instance is a specific payment provider setup in Payrails. You can create multiple instances for each provider based on region, currency, or business needs. Choose a clear, consistent name, as it is used in routing.
In Payrails
  • Enter an Instance name for your integration.
A screenshot showing the Payrails integration instance name field.

​
Merchant account name

In Adyen
  1. Log in to your Adyen dashboard.
  2. Click the company logo or name in the top-left corner.
  3. From the list of merchant accounts, copy the Merchant account name
    (not the company account).
A screenshot showing the Adyen dashboard menu. In Payrails
  • Paste the value into the Merchant account name field.

​
Prefix (production only)

The prefix is required in production but not in staging. You can leave this field blank in staging environments.
In Adyen
  1. Go to Developers → API URLs.
  2. Copy the Prefix value.
A screenshot showing the Adyen API URLs. In Payrails
  • Paste the value into the Prefix field.

​
API key

Use a dedicated Web Service User API key and store it securely.
In Adyen
  1. Go to Developers → API credentials.
  2. Select Create new credential.
  3. Choose Web Service User.
  4. Create the credential and copy the API key.
A screenshot showing the create a new API credential form. In Payrails
  • Paste the value into the API key field.

​
HMAC key (webhook signing key)

Payrails uses Adyen webhooks to receive asynchronous payment status updates.
Create the webhook in the same environment (test or live) as your Payrails integration.
In Payrails
  • Copy the Notification URL from the webhook section.
A screenshot showing the Payrails integration instance name field. In Adyen
  1. Go to Developers → Webhooks.
  2. Create a new Standard webhook.
  3. Select only the merchant account you are configuring.
  4. Paste the Payrails notification URL into the URL field.
  5. In Security, generate a new HMAC key and copy it.
  6. In Events, enable all standard events.
  7. Save the webhook configuration.
A screenshot showing the Adyen webhook HMAC field. In Payrails
  • Paste the HMAC key into the HMAC key field.
  • Return to the integration overview after your changes are saved.

​
Payment methods

In Payrails
  • Select the payment methods that should be enabled for this integration.
A screenshot showing the Adyen payment methods.

​
Checkout API version (v69 or v72)

About this settingPayrails supports two Adyen Checkout API versions: v69 (default) and v72. The version is set per provider instance, so you can control exactly which integration uses which version.
In Payrails
  • Under your Adyen integration instance, locate the Checkout API version field.
  • Choose v69 (default) or v72.
v72 is not backward compatible with v69Requests that succeed on v69 can fail on v72 if your integration doesn’t send the fields v72 requires. Review the table below and confirm your integration meets these requirements before switching a live instance to v72.
Saving a brand-new card as CardOnFile does not require a CVC — this only applies when charging a card that was previously saved. Subscription and UnscheduledCardOnFile payments never require a CVC.
Recommended rollout
  1. Enable v72 on a staging provider instance first and run your full payment flows end to end (new card, saved card, subscriptions, refunds, MOTO/wallet if used).
  2. In production, create a new Adyen provider instance on v72 rather than switching your existing v69 instance, and route a small share of traffic to it.
  3. Gradually increase traffic to the v72 instance over a few days while monitoring authorization rates and error codes.
RollbackSwitching a provider instance’s Checkout API version back to v69 takes effect on the next payment immediately — no deployment or code change required.

​
Enable the integration

In Payrails
  • Select Save account Save the configuration to enable the integration.
The Enabled status confirms that the Adyen integration is active. A screenshot showing the enabled Adyen integration. Your Adyen integration is now ready to process payments

​
Next steps

  1. Run a test payment using an Adyen test card.
  2. Verify that:
    • The payment appears in Adyen.
    • The payment status updates correctly in Payrails.
  3. Once verified in test mode, repeat the setup in live mode.
→ Continue to: Test a payment
Last modified on September 28, 2026