Plugins

Introduction

This page gives you a convenient overview of currently installed plugins in Saleor. Saleor provides the possibility to add various extensions to it so you can create your own configuration.

The plugin page is used to display general information about installed plugins, along with their activation status (active or not active).

If you choose to, you can use the plugin window to display the basic configuration to allow dashboard users to manage the elemental settings of existing plugins.

For more detailed information about plugins and our Extension Manager, see the Extending topic in the chapter for developers.

Saleor arrives with the following plugins already integrated.

• Used to configure taxes in Saleor:

  • Avalara

  • Vatlayer

• Used to process payments (all supported payment gateways in Saleor come as plugins):

  • Adyen

  • Braintree

  • Razorpay

  • Stripe

• Used to provide certain core features:

  • Invoicing

  • Webhooks

In all cases of plugin configuration, you need to provide your credentials. Depending on the gate you are configuring, there might be additional setup required.

Adyen

Enabling the Adyen integration

Go to Configuration -> Plugins -> Adyen and fill in the fields:

• Merchant Account: your Adyen account identifier as described in the getting started with Adyen guide

• Supported currencies: your currency as an ISO 4217 3-letter code (eg. USD, EUR, GBP)

• Client Key: The client key is a public key that uniquely identifies a web service. See Adyen docs.

• Live: Leave it blank if you want to use the test environment. See Adyen docs for production environments.

• Assume all authorizations are automatically captured by Adyen: All authorized payments will be marked as captured. This should only be enabled if Adyen is configured to auto-capture payments. Saleor doesn’t support the delayed capture Adyen feature.

• Automatically capture funds when a payment is made: If enabled, Saleor will automatically capture funds. If disabled, the funds are blocked but need to be captured manually.

• HMAC secret key: key used to check if a received notification comes from Adyen. The key should be the same as on the Adyen side. Generate a new key in the Adyen customer area and copy it here. See Adyen docs.

• Notification user: In addition to checking request signatures, you can confirm received notification by checking the provided user in the notification. Provide a user in the Authentication section of your Adyen customer area and copy it here. See Adyen docs.

• Notification password: In addition to checking request signatures, you can confirm received notification by checking the provided user’s password in the notification . Provide a password in the Authentication section of your Adyen customer area and copy it here. See Adyen docs.

• Enable native 3D Secure: Saleor uses 3D Secure redirect authentication by default. If you want to use native 3D Secure authentication, enable this option. For more details see Adyen documentation: native 3D Secure 2, redirect 3D Secure 1 and 2

Below you can find an example configuration of the Adyen plugin:

Activating the Adyen notification

Adyen uses a notification system. Enabling it is required for proper work of payment gateway.

1. Follow the Adyen docs about notifications.
   • For URL use https://<your-backend-url>/plugins/mirumee.payments.adyen/webhooks/.
   • For SSL Version use the newest one.
   • For Method use JSON.
2. To protect your notification follow the Adyen docs about security.
   • Copy the HMAC key into the Saleor's HMAC secret key field. (See Saleor configuration fields.)
   • Copy the username from Authentication section and paste it to Saleor field Notification user. (See Saleor configuration fields.)
   • Copy the password from Authentication section and paste it to Saleor field Notification password. (See Saleor configuration fields.)
3. To test your configuration check the Adyen docs about testing the configuration.