Configure Adyen in Sana Admin

NOTE

There is no separate add-on for Adyen. There are several scenarios when you can use Adyen as a payment service provider for the Sana webstore. In this case, the Sana Pay add-on is used to integrate with Adyen, because the basic configuration of Sana Pay and Adyen is identical.

If you use Adyen as your payment service provider to accept online payments, you must configure it in Sana Admin using the Sana Pay add-on. There is no separate add-on for Adyen.

Connect Sana Pay to Adyen

Step 1: In Sana Admin click: Apps > Add-ons. When the Sana Pay add-on is installed, you can configure it from any tab on the Add-ons page by clicking on the Configure button .

Step 2: Choose the appropriate payment integration mode.

There are two modes: test and live. Test mode allows to simulate the payment process as a real payment and helps to make sure that everything will behave the same way when you go live. Live mode implies that a customer makes a real purchase using already configured payment provider and methods.

Step 3: Configure the payment provider by entering the payment provider specific settings of your Adyen test or live account.

The table below provides description of the Sana Pay settings. These settings can be also used to connect Sana Pay to Adyen.

Field	Description
Live endpoint prefix	NOTE This setting is required only for the Live integration mode. To communicate with Adyen, you should submit HTTP POST requests to the corresponding endpoints. These endpoints differ for test and live accounts. To find your Adyen live endpoints: Log in to your live Adyen Customer Area. Go to: Developers > API URLs. On the API URLs page, you can see the configured endpoints for your company account. For example, if your live endpoint URL is: https://1797a841fbb37ca7-AdyenDemo-checkout-live.adyenpayments.com/checkout/v32/payments Then, the live endpoint URL prefix is: 1797a841fbb37ca7-AdyenDemo
API Key	Enter the API Key. The API Key is available in the Adyen Customer Area, click: Developers > API credentials. Open user details, go to Server settings and in the Authentication section click Generate API key. Copy the API key and insert it in Sana Admin.
Client Key	Enter the Client Key. The Client Key is available in the Adyen Customer Area. Click: Developers > API credentials. Open user details, go to Client settings and in the Authentication section copy the Client key.
Merchant account	The merchant account you want to process all your payment transactions with. You can use one merchant account for all payment transactions or different merchant accounts for different payment methods. For more information, see Merchant Accounts. To see your merchant accounts, log in to the Adyen Customer Area and click: Settings > Merchant accounts.

Configure Notification Settings

Notifications are webhooks that are used to inform Sana Commerce Cloud about payment status updates. They notify merchants about authorized, captured and modified payments, as well as other events and ensure that all payment stages have been processed.

First, you need to set up notifications in the Adyen Customer Area.

Field	Description
HMAC signature	A string in Base64 encoded format. The notification signature is generated by concatenating the values of a number of the standard notification fields, and by computing the HMAC using the shared secret, as configured in the standard notification. To generate the standard notification HMAC key, in the Adyen Customer Area click: Developers > Webhooks. Find the Standard notification webhook and click Edit webhook. You can generate new HMAC Key in the Security section.
Authentication username	HTTP authentication username and password of the standard notification. The username and password must be the same as in the Adyen server communication settings. In the Adyen Customer Area click: Developers > Webhooks. Find the Standard notification webhook and click Edit webhook. See Basic authentication in the Security section. NOTE If you don't enter the authentication username and password, HTTP authentication will not be used for notifications. It is recommended to use alphanumeric characters of the English language in the HTTP authentication username and password. For example, the character "ä" which is available in the German language is not supported.
Authentication password

Field

Description

HMAC signature

A string in Base64 encoded format.

The notification signature is generated by concatenating the values of a number of the standard notification fields, and by computing the HMAC using the shared secret, as configured in the standard notification.

To generate the standard notification HMAC key, in the Adyen Customer Area click: Developers > Webhooks. Find the Standard notification webhook and click Edit webhook. You can generate new HMAC Key in the Security section.

Authentication username

HTTP authentication username and password of the standard notification. The username and password must be the same as in the Adyen server communication settings.

In the Adyen Customer Area click: Developers > Webhooks. Find the Standard notification webhook and click Edit webhook. See Basic authentication in the Security section.

NOTE

If you don't enter the authentication username and password, HTTP authentication will not be used for notifications. It is recommended to use alphanumeric characters of the English language in the HTTP authentication username and password. For example, the character "ä" which is available in the German language is not supported.

Authentication password

When Sana Pay is installed and connected to Adyen, you can set up the necessary payment methods in Sana Admin that are supported by Adyen.