Adyen

Sana Commerce 9.3
Your connector

Set up Adyen Account

 NOTE

When the Adyen payment provider is installed, it should be configured in the Adyen BackOffice and in Sana Admin. To configure the Adyen payment provider and payment methods you should have the Adyen test/live account with all the necessary data.

Currently, the Adyen BackOffice has two user interfaces - new and old. It can be changed in the preferences of your Adyen account. Therefore, the settings described below are located in different places depending on whether you are using a new or old user interface.

Activate company and merchant accounts

Make sure that your company and merchant accounts are activate.

New look:

Click: Accounts > Users. Click on the user name link. You can find the company and merchant accounts at the bottom of the "Edit Web Service User" page.

Old look:

Click: Settings > Users. Click on the user name link. You can find the company and merchant accounts at the bottom of the "Edit Web Service User" page.

Create a new skin

A skin is an interface overlay that is applied to the Adyen Hosted Payment Page (HPP) to customize it according to your brand guidelines and create a seamless consumer checkout experience. The Skin is comprised of a set of custom HTML/JavaScript fragments, images and CSS.

New look:

Click: Account > Skins. On the page "Skins for the Payment Pages", click Create a new skin.

Old look:

Click Skins. On the page "Skins for the Payment Pages", click Create a new skin.

Fill in the required skin details as described in the table below. Use the default values for all other skin settings.

Settings Value
Description A description of your skin to easily identify it if you have multiple skins.
HMAC Key Specify the HMAC Key for each environment. The key is used to compute the merchant signature. The same key cannot be used for both, test and live environments.

For more information about how to create and set up customized skins for the Adyen hosted payment pages, see "Skin" on the Adyen support web site.

For more information, see "Hosted Payment Page".

Publishing the skin to live

After you have finished creating and configuring a skin in the Adyen test environment, you should publish it to the live environment. The process of publishing does not change any settings, it just copies the skin as it is in the test environment to the live environment.

Step 1: Open the skin and ensure that the live HMAC Key is set up correctly in the skin.

Step 2: On the Publish tab, click Publish to Live.

For more information, see "Publishing the skin to live".

Set up standard notification settings

New look:

Click: Account > Server communication. Find Standard Notification and click Add. Configure standard notification settings as described in the table below. Use the default values for all other standard notification settings.

Old look:

Click: Settings > Server Communication. Find Standard Notification and click Add. Configure standard notification settings as described in the table below. Use the default values for all other standard notification settings.

Settings Values
URL Enter the URL in the following format: {domain name}/confirm/payment/Adyen

Replace {domain name} with your web store domain name.
Example: https://sanastore.com/confirm/payment/Adyen

SSL Version Select the SSL version. It should match the one used to secure your Sana web store.
Active Select the checkbox to activate notification.
Service Version Select "1".
Method Select "HTTP POST".
Authentication Enter user name and password for the HTTP authentication. You will also need to enter these credentials in the settings of the Adyen add-on in Sana Admin.

    If you don't set up authentication settings, HTTP authentication will not be used for notifications. It is recommended to use alphanumeric characters of the English language in the HTTP authentication user name and password. For example, the character "ä" which is available in the German language is not supported. Please, contact Adyen support for more information.
Merchant Accounts Add your merchant account.
Additional Settings Generate HMAC key for the standard notification.

 

Notifications troubleshooting

In some cases, Sana may not receive notifications from Adyen. This can occur because of the following reasons:

  • Security issues of the notification. For example, HMAC was changed and the one in Sana Admin does not match the HMAC key in Adyen.
  • Adyen cannot update the payment status of the order in Sana for some reason, for example because of the connection issues or the Web server is down.

You can see your notification instances set up for Sana in the Adyen BackOffice. All notifications are queued. The notifications which Sana does not accept will be highlighted with red color.

If Sana does not accept the notification sent from Adyen due to the reasons listed above, then Adyen will retry sending the notification until it is accepted. Retry attempts happen regularly for up to 7 days.

In case the HMAC key was changed and the one in Sana does not match the HMAC key in Adyen, then Sana will not accept the notifications containing the old HMAC key. Therefore, these notifications need to be discarded in the queue in Adyen. Adyen will resend every notification one by one over a course of 7 days.

If you need to fix the notification immediately, you can manually accept it. Click the button Troubleshoot on the necessary notification and then click Manually accept notification. Adyen will not send this notification to Sana again and the payment status will not be updated based on this notification.

It is highly recommended not to accept notifications manually without verifying the reasons of failure. You can also use the error log to detect the issues.