> For the complete documentation index, see [llms.txt](https://help.konnektive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.konnektive.com/konnektive-crm/gateway-setup/gateways/adyen-v2.md).

# Adyen V2

<figure><img src="/files/ZD4SNHUD4y6sGAFG0IUj" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
This integration uses Adyen's Checkout API v71
{% endhint %}

{% hint style="info" %}
Adyen supports credit cards and the following [alternate payment methods](/konnektive-crm/gateway-setup/gateways/adyen-v2/adyen-alternate-payments.md)

* Afterpay
* Bancontact
* iDEAL
* Kakao Pay
* Klarna
* MobilePay
* PayByBank
* Riverty
* SEPA
* Swish
* Trustly
* Google Pay
* Apple Pay
  {% endhint %}

**STEP 1**

**ADYEN ACCOUNT**

1. Obtain **merchantAccount** and **apiKey** from Adyen
2. Obtain **liveUrlPrefix** from Adyen. **liveUrlPrefix** is a string composed of a hex-encoded random part and your company name. Get the prefix from your [live Customer Area](https://ca-live.adyen.com/) under Developers > API URLs > Prefix.
3. Enable the “API PCI Payments” role for the API key (Contact the Adyen support to enable this feature). This may require submitting the Konnektive PCI documentation. Please contact your account manager if this is needed.
4. Under Account Settings set your account to “immediate” capture delay.
5. In your Customer Area, go to Developers > Additional data.
   1. Enable the following settings
      1. Acquirer result
      2. Raw acquirer result
      3. Recurring details
      4. Network transaction reference
      5. 3D Secure (optional)
6. Setup a standard webhook. This is required for final resolution of refund and capture requests.
   1. **Server configuration**
      1. URL: <https://api.konnektive.com/billers/adyenv2/notification/>
      2. Method: JSON
      3. Encryption protocol: TLSv1.2
   2. **Security**
      1. HMAC: Generate a new key and added to the **hmacKey** gateway field in Step 2.
   3. **Events**
      1. CAPTURE
      2. REFUND
      3. REFUND\_FAILED
      4. CANCEL\_OR\_REFUND
      5. AUTHORISATION (if using [Alternate Payments](/konnektive-crm/gateway-setup/gateways/adyen-v2/adyen-alternate-payments.md))
      6. EXPIRE
      7. CANCELLATION

&#x20;

**STEP 2**

In the CRM, go to Gateways > Gateway Integrations. Find AdyenV2 and click the tile. Then click the <mark style="color:green;">**+Activate**</mark> button.

<figure><img src="/files/87o9f9cww6f5Uf9wrfZn" alt="" width="375"><figcaption></figcaption></figure>

**STEP 3**

Fill the fields obtained in Step 1.

Select “No” on **secure3DS** if it is for Non-3DS. Use **force3DS** to require 3DS from Adyen.

<figure><img src="/files/bjdsQjWsiKUmD2C8YiPi" alt="" width="375"><figcaption></figcaption></figure>

**STEP 4**

Add the hidden input browserData inside of the same form as the card input.

`<input type="hidden" name="browserData" value="" id="browserData">`

&#x20;

**STEP 5**

Add this script to your page before the closing body tag.

```javascript
Script to get browserData:
<script type="text/javascript">
    const navigator = window.navigator;
    const browserData = {
        acceptHeader: 'application/json',
        colorDepth: screen.colorDepth,
        javaEnabled: navigator.javaEnabled(),
        javaScriptEnabled: true,
        language: navigator.language,
        screenHeight: screen.height,
        screenWidth: screen.width,
        timeZoneOffset: (new Date()).getTimezoneOffset().toString(),
        userAgent: navigator.userAgent
    };
    document.getElementById('browserData').value = JSON.stringify(browserData);
</script>
```

&#x20;

**STEP 6**

For 3DS your checkout page must support the standard 3DS workflow

[Basic 3DS Instructions](/konnektive-crm/gateway-setup/basic-3ds-instructions.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.konnektive.com/konnektive-crm/gateway-setup/gateways/adyen-v2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.