Integrating Adyen

Setting up Adyen as a payment provider involves the following tasks:

Creating Adyen Account

In order to use Adyen as a payment provider, you need a valid Adyen account. To get going, refer to Adyen's Get started guidelines.

To integrate with JustOn Cash Management, your Adyen account requires

Configuring Merchant Account

To configure a dedicated merchant account (see Merchant accounts):

  1. Request a new merchant account.

    1. In the Adyen Customer Area, proceed to Settings > Merchant accounts, and click Request new merchant account.
    2. In the field Desired account code, specify a name for the merchant account.

      You need this name for the integration configuration in JustOn Cash Management.

    3. In the field Channel, select to use the account for processing ecommerce transactions.

    4. Click Submit.

    For details, see Request a new merchant account.

  2. Enable the automatic capture.

    1. In your merchant account, navigate to Settings > Account settings > General.
    2. In the Capture delay field, select immediate.

    For details, see Delayed automatic capture.

  3. Enable the intended payment methods.

    1. In your merchant account, navigate to Settings > Payment methods > Request payment methods.
    2. Start typing the name of the intended payment method, then select it from the produced list.
    3. Click Submit.

    For details, see Add payment methods to your account.

Configuring API Credential

To set up a dedicated API credential for JustOn Cash Management:

  1. Create an API credential of the type Web service user.

    In the Adyen Customer Area, proceed to Developers > API credentials > Create new credential. For details, see Create an API credential.

  2. Generate an API key and save it for the Adyen configuration in JustOn Cash Management.

    In the Adyen Customer Area, proceed to Developers > API credentials > Credentials > Server settings > Authentication > API key > Generate API key. For details, see Generate an API key.

    Make sure to copy your API key and to save it for the integration configuration in JustOn Cash Management.

  3. Generate a client key and save it for the Adyen configuration in JustOn Cash Management.

    In the Adyen Customer Area, proceed to Developers > API credentials > Credentials > Client settings > Authentication > Client key > Generate client key. For details, see Get your client key.

    Make sure to copy your client key and to save it for the integration configuration in JustOn Cash Management.

  4. Add the JustOn Cash Management payment page as an allowed origin.

    In the Adyen Customer Area, proceed to Developers > API credentials > Credentials > Allowed origins. Specify https://payment.juston.cloud and click Add. For details, see Manage allowed origins.

Enabling Notification Webhooks

To enable notification webhooks for JustOn Cash Management:

  1. Add a webhook of the type Standard notification.

    In the Adyen Customer Area, proceed to Developers > Webhooks > + Webhook. For details, see Set up notifications in your Customer Area.

  2. Add the JustOn Cash Management webhook server URL.

    Navigate to Server configuration and specify

    https://payment.juston.cloud/webhooks/payment/payment-provider/adyen/:tenant/
    

    where :tenant is the URI alias of your organization.

  3. Generate an HMAC key and save it for the Adyen configuration in JustOn Cash Management.

    Navigate to Security > HMAC Key > Generate. For details, see Enable HMAC signatures.

    Make sure to copy your HMAC key and to save it for the integration configuration in JustOn Cash Management.

Configuring Adyen Integration

To configure the Adyen integration with JustOn Cash Management:

  1. Create a payment provider configuration record as necessary.

    Make sure to select Adyen in the Type field.

    For details, see Creating Payment Provider.

  2. Open the relevant payment provider record.

  3. Click Edit Provider Data.

    1. Modify the Adyen-specific public information as necessary.

      The public information required for Adyen includes:

      Field Description
      Environment The region-specific part of the Adyen API URL, part of the configuration sent to the Web Drop-in. The available values include test, live, live-apse, live-au, live-us.
      Find your endpoint URLs in the Adyen Customer Area under Developers > API URLs > API URLs and Response.
      For details, see Live endpoints structure.
      API Prefix The API prefix used with calls to the Adyen API.
      This field is only visible if the environment is not test or None. Find your prefix in the Adyen Customer Area under Developers > API URLs > Prefix.
      For details, see Live URL prefix.
      Merchant Account The name of your merchant account, sent to Adyen with every request.
      Creating a merchant account is part of the Adyen account setup.
      Client Key The client key used by the Web Drop-in to authenticate requests from your JustOn Cash Management instance.
      Generating the client key is part of the Adyen account setup.
      Capture Immediately Makes JustOn Cash Management treat each AUTHORIZATION notification webhook as a CAPTURE notification webhook. Selected by default.
      Corresponds to the automatic capture setting in your merchant account (see Adyen account setup).
    2. Modify the Adyen-specific secret information as necessary.

      The secret information required for Adyen includes:

      Field Description
      API Key The key to authenticate requests to the Adyen API from your JustOn Cash Management instance.
      Generating the API key is part of the Adyen account setup.
      HMAC Key The key used to verify webhook messages.
      Generating the HMAC key is part of the Adyen account setup.

      The dialog does not disclose existing secret data.

  4. Click Save.

    This completes the screen flow, saving the specified information as required, and returns you to Payment Provider detail view.

    Once the Adyen-specific data is complete, the Adyen configuration is fully functional and available to payment users.