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

# Adyen

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

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

**STEP 1**

**ADYEN ACCOUNT**

1. Obtain **Merchant\_Accoun**t, **API\_Key** and **API\_URL** from Adyen. The integration is using Classic API V52, so the **API\_URL** should end in /v52/. Be sure to include the ending slash.
   1. [Live endpoints | Adyen Docs](https://docs.adyen.com/development-resources/live-endpoints#classic-payments-endpoints)
   2. The URL should be structured as: https\://**\[prefix]**-pal-live.adyenpayments.com/pal/servlet/Payment/v52/
2. Have your account set for LIVE API/PCI role, which may require submitting the CheckoutChamp PCI documentation. Please contact your account manager if this is needed.
3. Have your account set to “immediate” capture for “sale” or “delay” capture for “authorize”
4. Discuss with Adyen if you need to enable recurring orders

<figure><img src="/files/WoQ2bXulajVuSHXb9BWV" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Q2AiyMU0s1nhF9ZkwfBC" alt=""><figcaption></figcaption></figure>

**STEP 2**

In the CRM, go to Gateways >Gateway Integrations, Scroll down to Adyen and click the logo. Then click the Activate button.

<figure><img src="/files/T7SfU0CRrkQ01AS2Ou57" alt=""><figcaption></figcaption></figure>

**STEP 3**

Fill the fields below. Select “No” on **Secure3DS** if it is for Non-3DS.

<figure><img src="/files/RUZm7CwrUlRMwOnH8d8U" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
Skip steps 4-6 if using CheckoutChamp hosted pages
{% endhint %}

**STEP 4**

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

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

**STEP 5**

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

```
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>
```

**STEP 6**

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

[Basic 3DS Instructions](/crm/gateway-setup/direct-api-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.checkoutchamp.com/crm/gateway-setup/gateway-integrations/adyen.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.