What version(s) of TLS does Adyen support?

Recommended: TLS 1.3

We recommend using the latest TLS version, preferably with cipher suites offering 256-bit security. Currently, this is TLS version 1.3. This version has many improvements over TLS 1.2 including faster handshakes and no longer supports older, cryptographically less secure features.

Handshake mode should be ECDH (secp256r1, secp384r1, secp521r1)

Preferred ciphers are:
0x13,0x02 TLS_AES_256_GCM_SHA384

0x13,0x03 TLS_CHACHA20_POLY1305_SHA256

Required: TLS 1.2

All merchant integrations with Adyen must use at least TLS 1.2.

TLS 1.0 mustn’t be used to protect payments data or payments pages after June 30, 2018.

The PCI Security Standards Council (PCI SSC) no longer accepts early TLS (TLS 1.0) as a secure communication protocol for transmitting payment card data, and we have therefore disabled older versions of TLS on our platform.

Note: Integrations such as Java 7 or .NET 4.0 don’t support TLS 1.2 using default configurations. Integrations using Java 6 and below, .NET 3.5 and below, Python 2.7.8 and below, Ruby 1.9.3 and below, OpenSSL 1.0.0 and below, will all be difficult or impossible to configure to use TLS 1.2, and significant migration effort may be required by the merchant. Additionally, shoppers using old browsers (IE8 and IE9 as well as Android versions 4.4 and below) that only support early TLS in combination with Hosted Payment Pages (HPP) and Client Side Encryption (CSE) won’t be able to connect to these services.

The integration security guide

Follow best practices to reduce security risks.

View integration security guide
The illustration of support agent wearing a headset.

Do you need additional help?

Contact our support team

Send us the details of your issue by adding images or screenshots.

Submit a request