Adyen

Configure Adyen in Sana Admin

When the Adyen payment provider is installed and configured in the Adyen BackOffice it should be also configured in Sana Admin.
 
To configure Adyen:
 
Step 1: In Sana Admin click: Setup > Ordering & checkout > Payment methods > Configuration > Adyen Payment.

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 the test/ live account.

The table below provides description of the Adyen payment provider settings.

Field	Description
Merchant account	The merchant account identifier you want to process the (transaction) request with. You can find your merchant account on the Accounts page.
Skin code	A unique code to identify the skin that you want to apply to the hosted payment page which processes the transaction.     You can create a skin for your hosted payment page to make it consistent with your brand guidelines. You can create multiple skins in your merchant account to provide tailored branding experiences to your shoppers.
Skin HMAC signature	The signature in Base64 encoded format. The signature is generated by concatenating the values of a number of the payment session fields, and by computing the HMAC using the shared secret, as configured in the skin. To generate the skin HMAC key, open the Skins page, edit your skin, and then click Generate new HMAC Key.
Notification service 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, click: Settings > Server Communication. Find the Standard Notification setup and click Edit & Test. You can generate new HMAC key in the Additional Settings.
Session validity	Number of days for the payment deadline; the payment needs to occur within the specified time value. This is especially useful for tickets and reservations, where you want to hold items for sale for a short or limited period of time.      Should not be less than 0 or greater than 365.
Ship before date	Number of days for the ordered goods or services to be shipped or provided to the buyer when the order is placed.      Should not be less than 0 or greater than 365.