Adobe Commerce troubleshooting

If you are experiencing a problem with your Adobe Commerce integration, there are several ways how you can troubleshoot the issue yourself. Before you contact our Support Team:

• Make sure that you set up the plugin correctly.
• Check our FAQ.
• Follow the steps below.

Step 1: Clear the cache

The Adyen Payment plugin makes use of the Adobe Commerce cache system to speed up some of the backend processes.

When troubleshooting, clear your cache storage and full page cache system, including accelerators such as Varnish. Not clearing the cache can result in payment methods not correctly showing up, or not working as expected.

Step 2: Disable third-party plugins

The Adyen Payment plugin is often used in combination with other Adobe Commerce plugins that can impact your checkout flow or the backend processes. Commonly used plugins are for example One Step Checkout, or modules that generate the Adobe Commerce Order ID.
When troubleshooting our plugin, make sure to temporarily disable any third party plugins.

Step 3: Check Adobe Commerce logs

Errors are logged by Adobe Commerce in the following files:

The var/log/exception.log file also contains non-Adyen-specific logs. If you have permissions to access exception.log, you can see Adyen-specific errors by using the following command:

grep -i adyen var/log/exception.log

Information about the plugin activity is logged in the following files:

Step 4: Check common errors

Use the Adobe Commerce logs to troubleshoot common errors including:

• Order status not updating
• Errors when placing orders
• Payment methods not showing up

Order status is not updated

If the order status in Adobe Commerce is not being updated, this is usually because one of the following reasons:

• The OFFER_CLOSED webhook is not enabled. This is needed to close abandoned orders.

To enable this webhook, follow the instructions to set up webhooks by changing the settings in your Customer Area.

• The Adobe Commerce platform is not receiving, accepting, or storing the webhooks in the database.
• The Adobe Commerce cron job is not processing the webhooks, or is not updating the order status in Adobe Commerce.

To debug these issues, use the Adyen Customer Area, the notification logs, or the Adobe Commerce notifications overview.

Adyen Customer Area

In the Customer Area, you can verify if there are any issues with the endpoint:

Your server must acknowledge webhooks with a successful HTTP response status code (like 202).

1. Log in to your Customer Area.
2. Select Developers > Webhooks.
3. Select the webhook to test.
   The Webhook details panel includes information about the configuration. Under Events, you can find the configured event codes that you can test for this webhook.
4. Select the edit icon
5. Select Test configuration.
6. If you are on a company account, select a Merchant account from the dropdown list.
7. In the Event dropdown list, select the event code to test webhooks for.

If the test webhook failed, you get an error message with the reason. Troubleshoot the problem.

If you receive an error, some of the possible reasons are:

• HMAC is not generated.
• The notification username and password within the Adobe Commerce required settings do not match the authentication credentials within Adyen. Mixing the live and test credentials usually causes this.
• IP address validation or server issues (often results to a 302 or 401 error).

Notification logs

In the logs, you can check if Adobe Commerce is receiving notifications and if the cron job is running.

• To check if you are receiving notifications, look into the var/log/adyen/notification.log. If this doesn't include the expected notifications, refer to Adobe Commerce does not receive notifications for possible causes and solutions.

• To check if the Adobe Commerce cron job is processing notifications, look into the var/log/adyen/cronjob.log. If you notice an issue, check your cron log.

Adobe Commerce notifications overview

In your admin panel, you can check if the notifications are queued.

1. Go to System > Adyen > Notifications overview.
2. If the notifications are queued and the Processing and Done columns are set to No, contact your technical team to restart the cron job.
3. To pick up the queued notifications again, your technical team can also update the adyen_notification table to set the Processing and Done columns from 1 to 0. For notifications older than 5 days, you also need to update the creation date to less than 5 days.

Errors when placing orders

A common error thrown when placing an order is:

"Error with payment method, please select a different payment method"

This error can be thrown for several reasons. For more information on what caused the error, check the var/log/adyen/info.log for the /payments API response JSON.

Some common error scenarios are described below:

{
  "status":500,
  "errorCode":"905",
  "message":"Payment details are not supported",
  "errorType":"configuration"
}

If you find the above error, make sure that the payment method is set up correctly. If the issue persists, contact our Support Team.

{
  "status":422,
  "errorCode":"135",
  "message":"Billing address problem (StateOrProvince)",
  "errorType":"validation"
}

If you find the above error, make sure that you send the StateOrProvince as part of the billing address.

Payment methods not showing up

If a payment method is not showing up in your checkout, check the following:

• Does this payment method require any additional set up?
• Does the /paymentMethods API request include the correct country/region and currency combination for the payment method? Use the var/log/adyen/info.log file to look this up.
• Is the payment method included in the /paymentMethods API response? Use the var/log/adyen/info.log file to look this up.

For more information, refer to Why are Adyen alternative payment methods not showing up in Adobe Commerce?.

Step 5: Check for customizations

If you applied any customizations to the plugin, the error might be related to the customization. Before raising an issue, make sure that your error is not a customization issue, and check if it persists on a cleanly installed plugin. If you cannot reproduce the issue with a clean version, it is most likely an issue introduced by the customization.

Step 6: Check our release notes

Check if your current error is a known issue in the plugin, and resolved in a later version. You can find the known issues and fixes either in our technical release notes on GitHub, or in our commercial release notes.

To find out which version of the plugin you are using:

1. Log in to your Customer Area.
2. Go to Transactions > Payments, and select the PSP reference of any payment.
   This opens the Payment Details page.
3. Go to the Application Info section.
   The plugin version is shown under Payment Device Version.

Alternatively, you can look into the var/log/adyen/info.log to see the merchantApplication.version sent in every API request.

Step 7: Check open issues in GitHub

Go to the open issues in our GitHub, and see if there is an open issue related to your error. If that is the case, you can leave a comment there to have direct contact with our dev teams.

Step 8: Contact us

If the problem still persists after you have followed the above steps, you can either:

• Create a GitHub issue if you found a bug.
• Contact our Support Team, providing your plugin version and other relevant information, for example screenshots or logs.

See also