Salesforce Commerce Cloud

This document describes version 18.1.0 of the Adyen LINK cartridge. For version 17.1.0, click here.

Adyen offers a LINK cartridge to integrate with Salesforce Commerce Cloud for ecommerce platforms. You can integrate your in-store payments through any of our POS integrations to offer a full omni-channel experience.

Create a merchant account in the Customer Area, to know more read Get started with Adyen.

Adyen offers the following integrations:

  • Using the Adyen API, if you want to support cards only. 
  • Using the Redirect model for cards and local payment methods.

Some items that need to be configured in the Customer Area for the Adyen Integration to work correctly.

Parameter Name


HMAC256 key

Secret key used to calculate a signature over the payment fields sent to Adyen. This should match what is used in the Adyen configuration settings in your Commerce Cloud site.


Code of the skin you want to use. You can use different skins, each having a different configuration, style, language, etc.

Notification URL and test page

URL where Adyen should send notification messages to. The script at this URL should always reply with [accepted]; otherwise, Adyen keeps sending messages.

The Notification URL and its response can be tested from within the CA.

Payment Methods

You can select which payment methods should be displayed by configuring your skin. This can also be influenced with the 'allowedMethods' parameter that can be sent to Adyen for each payment.

Test HPP and skin

The skin and HPP can be tested from within the CA, to check the look and feel, translations, configured payment methods, etc.

Settings for the PAL adapter

To send Credit Card payments directly (without redirecting to the HPP) you can use the PAL adapter. The user, password and location can be configured here.

Notifications User Name

The username used by the Adyen notification system in order to authenticate the calls with Commerce Cloud. Should be the same as the one set in Commerce Cloud system under "Adyen Notifications User" preference. (Found under: Settings > Notifications > User Name)

Notifications Password

The password used by the Adyen notification system in order to authenticate the calls with Commerce Cloud. Should be the same as the one set in Commerce Cloud system under "Adyen Notifications Password" preference. (Found under: Settings > Notifications > Password)

  • Successful payment authorizations lead to a Paid order status and Ready for Export status.
  • Refused payment authorizations lead to a 'Not Paid' order payment status, and 'Not Exported' export status.
  • Cancels and refunds lead to a 'Not Paid' order payment status (even if the status was 'Paid' before), and 'Not Exported' export status.
  • Refused payments have the status 'Refused' in the Adyen CA, but 'AUTHORISATION' Eventcode in Business Manager.
  • In the cartridge these API methods are implemented: 'Capture', 'Cancel Before Capture', and 'Cancel Or Refund'. The statuses require custom integration into the end site, they are optional functions and are not described in this document from a position of integration.
  • The cartridge makes use of the Adyen Hosted Client-Side Encryption library, other methods require additional customization.

Use cases

Registered and unregistered shoppers will be able to follow the standard Site Genesis flow with the following changes:

  • Adyen redirect, Adyen API and Gift Certificates (GC) will be the only payment options if Adyen redirect is enabled:
    • no entering of credit card details on the Billing page is possible when the user selects this payment method (as this is done on the Adyen HPP) and Directory Lookup feature is disabled
    • the possibility to choose one of the predefined payment methods on the Billing page with further redirection to Adyen HPP, if Directory Lookup is enabled and the user selected Adyen payment method
    • a redirect to Adyen HPP after clicking the 'SUBMIT ORDER' button on the Order Confirmation page (only if no GCs are used and/or they don't cover the whole amount)
    • a return to the Order Summary page after successful payment authorization
    • a return to the Order Confirmation page, if the user cancelled the payment on Adyen HPP
    • a return to the Order Confirmation page with an error message displayed, if the payment was refused
  • If Adyen API payments are enabled:
    • credit card details are entered and stored in your Commerce Cloud shop
    • for the other payment methods you can still redirect to the Adyen HPP, but can disable credit cards via the configuration of your skin

Privacy, payments

  • If only the redirect method is used, all payment data is entered into the Adyen HPP by the shopper and no Credit Card data will be stored inside Commerce Cloud (except the brand of used card)
  • The shoppers email address and shopper ID used in Commerce Cloud are sent to Adyen to allow 'recurring' and/or 'one-click' payment


The integration is based on the Site Genesis demo store provided by Commerce Cloud.


  • Commerce Cloud 17.1.0 and higher
  • SiteGenesis 103.1.3 and higher


In case of problems with the integration or connection to Adyen, contact the Support Team or your Adyen account manager.

Supply as much information as possible: your merchant account, skin code, time, order number, PSP reference, etc.