Adyen
Payments · adyen.com · last read 2026-11-16
At a glance
- Is Adyen GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Adyen itself publishes, each answer linked to its source and the date we read it.
- Does Adyen have a data processing agreement (DPA)?
- Yes. Adyen publishes a data processing agreement at adyen.com. It describes how a new subprocessor is announced but states no notice period. It promises breach notification "without undue delay", with no number of hours. Source and date
- Which version of the Adyen DPA is current?
- On 2026-11-09, Adyen's DPA at adyen.com printed “Effective from: 1 April 2025”. Source and date
- Does Adyen have a SOC 2 report?
- Adyen states SOC 2 Type 2 on its own page, but does not say there how to get a report. In Adyen's words: “Systems and Organization Controls 2 (SOC 2) Type 2.” We read this on 2026-10-08. Source and date
- How does Adyen transfer personal data out of the EU?
- Adyen's agreement relies on the EU standard contractual clauses. We found no entry for Adyen on the official Data Privacy Framework List. Source and date
- Who are Adyen's subprocessors?
- Adyen lists 4 third-party subprocessors; 0 of them name at least one processing country outside the EEA. We last read the list on 2026-10-08. Source and date
- How do you report a security vulnerability to Adyen?
- Adyen publishes a security.txt at www.adyen.com naming responsibledisclosure@adyen.com. The file falls short of RFC 9116: expired 2025-12-31. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Adyen N.V. |
|---|---|
| HQ | NL |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | — |
| US CLOUD Act reach | Not determined from the sources read |
| Source | adyen.com · 2026-10-08 |
Data location
No data-location observation recorded yet.
The same question for every vendor: where SaaS vendors store EU data.
Adyen's subprocessor list names AWS, Microsoft, Google and Oracle for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
4 third parties · 11 of the vendor's own group companies · 0 with a country outside the EEA · all read 2026-10-08
| Subprocessor | Country | Purpose |
|---|---|---|
| Amazon Web Services, Inc. | — | Cloud services, including cloud infrastructure, storage, compute, and networking |
| Google LLC | — | Cloud services, including cloud infrastructure, storage, compute, and networking |
| Microsoft Corporation | — | Cloud services, including cloud infrastructure, storage, compute, and networking |
| Oracle Corporation | — | Cloud services, including cloud infrastructure, storage, compute, and networking |
Adyen's own group companies listed as subprocessors (11)
| Company | Country | Purpose |
|---|---|---|
| Adyen Australia Pty Ltd | AU | — |
| Adyen Canada Ltd. | CA | — |
| Adyen do Brasil Instituição de Pagamento Ltda. | BR | — |
| Adyen India Tech Hub Pvt. Ltd. | IN | — |
| Adyen India Technology Services Pvt. Ltd. | IN | — |
| Adyen Japan K.K. | JP | — |
| Adyen MEA FZ-LLC | AE | — |
| Adyen Mexico SA de CV | MX | — |
| Adyen N.V. (San Francisco Branch) | US | — |
| Adyen N.V. UK Branch | GB | — |
| Adyen Singapore Pte. Ltd. | SG | — |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · adyen.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | SCC module 1 |
| Transfer mechanism | SCC module 3 |
| Notice of new subprocessors | Processor notifies Controller of intended changes to Sub-Processors; advance notice period not stated |
| If you object to one | Object in writing with reasons within 30 days of notification; if Processor does not address the objection, the sole remedy is immediate termination of the Merchant Agreement and DPA |
| Obligations passed to subprocessors | same material data protection obligations as in this DPA imposed on Sub-Processors, in particular appropriate technical and organizational measures |
| Breach notification | without undue delay after becoming aware |
| Deletion when the service ends | On termination or expiration, return or delete Personal Data at Controller's request and confirm in writing; no deletion where retention is legally mandatory or required by Scheme Owners (data then blocked and stored securely); may anonymise instead where deletion is not practically possible |
| Getting your data back | On termination or expiration, return Personal Data at Controller's request, with written confirmation |
| Requests from data subjects | Tells data subjects to contact Controller first and notifies Controller without undue delay of rights requests it receives; does not respond unless authorised; reasonably cooperates and assists |
| Audit | Annual independent third-party ISAE 3402/SOC 2 audit, latest report provided to the controller on request; annual PCI DSS audit, certification shared on request; these audits are the agreed audit method under GDPR Art. 28(3)(h) and SCC Clause 8.8(d) |
| Audit | Cooperation with reasonable assessments/audits by Merchant or its designated assessor, at least once every 12 months; delivery of Adyen's annual ISAE 3402/SOC 2 audit report and PCI DSS Attestation of Compliance satisfies the audit obligation |
| Audit | Third-party report: SOC 2 Type 2 report shareable upon request |
| Processing on your instructions | Processes personal data consistent with the DPA, Controller's Instructions and/or as necessary to provide the Services, in accordance with Applicable Laws; Merchant Agreement and DPA count as Instructions |
| Confidentiality of staff | employees processing Personal Data have signed appropriate confidentiality obligations |
| Security measures | technical and organizational security measures set out in Annex 4; annual independent ISAE 3402/SOC 2 audit |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
On 2026-11-09, the agreement printed: Effective from: 1 April 2025
at adyen.com
In effect from 2025-04-01
This version is in our copies from 2026-10-09.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
Assurance
Does Adyen have a SOC 2 report?
Adyen states SOC 2 Type 2 on its own page, but does not say there how to get a report. We read this on 2026-10-08.
Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| PCI-DSS · PCIDSS | Claimed | our product and payment platform | adyen.com | 2026-10-08 |
| Systems and Organization Controls 2 (SOC 2) Type 2 · SOC2T2 | Claimed | Adyen’s information systems relevant to security, availability, confidentiality, and privacy | adyen.com | 2026-10-08 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Adyen; Adyen N.V.
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Adyen; Adyen N.V.
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Adyen; Adyen N.V.
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Adyen; Adyen N.V.
- Data Privacy Framework List (US): checked 2026-11-16, no entry under Adyen; Adyen N.V.
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Adyen; Adyen N.V.
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Adyen; Adyen N.V.
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under Adyen; Adyen N.V.
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Adyen; Adyen N.V.
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Adyen; Adyen N.V.
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
What an entry on the Data Privacy Framework List covers, and which vendors hold one: EU-US Data Privacy Framework.
Support window
| Product | Support period | State | SBOM | Source | Observed |
|---|---|---|---|---|---|
| Adyen (service) | — | Service only | unknown | adyen.com | 2026-10-11 |
Vulnerability reporting: responsibledisclosure@adyen.com (security.txt, expired 2025-12-31; read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-10-08 |
| dpa | Public | full | 200 | 2026-10-09 |
| subprocessors | Public | full | 200 | 2026-10-08 |
History
Nothing has moved since we started watching this vendor on 2026-10-08. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.