Mollie
Payments · mollie.com · last read 2026-11-16
At a glance
- Is Mollie GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Mollie itself publishes, each answer linked to its source and the date we read it.
- Does Mollie have a data processing agreement (DPA)?
- Yes. Mollie publishes a data processing agreement at mollie.com. It gives 10 days' notice before a new subprocessor is added. It promises breach notification "without undue delay", with no number of hours. Source and date
- Does Mollie have a SOC 2 report?
- Mollie states SOC 2 Type 2 on its own page, but does not say there how to get a report. In Mollie's words: “SOC 2 Type 2 Our security, availability, and confidentiality controls are independently assessed against the AICPA's Trust Services Criteria.” We read this on 2026-10-08. Source and date
- How does Mollie transfer personal data out of the EU?
- Mollie's agreement relies on the EU standard contractual clauses and the UK transfer addendum. We found no entry for Mollie on the official Data Privacy Framework List. Source and date
- How do you report a security vulnerability to Mollie?
- Mollie publishes a security.txt at www.mollie.com naming https://hackerone.com/mollie or responsible-disclosure@mollie.com or security@mollie.com. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Mollie B.V. |
|---|---|
| HQ | NL |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | — |
| US CLOUD Act reach | Not determined from the sources read |
| Source | mollie.com · 2026-10-08 |
Data location
No data-location observation recorded yet.
The same question for every vendor: where SaaS vendors store EU data.
Subprocessor chain
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · mollie.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | SCC (module not stated) |
| Transfer mechanism | UK Addendum |
| Transfer mechanism | UK IDTA |
| Transfer mechanism | other |
| Notice of new subprocessors | Prior notice with at least 10 calendar days to object; for expedited engagements (to protect data or avoid material service disruption), notice as soon as reasonably practicable |
| If you object to one | At least ten calendar days to object before a new sub-processor is engaged, except where Mollie reasonably believes an expedited engagement is needed; then notice as soon as reasonably practicable |
| If you object to one | Written objection on reasonable data protection grounds within 5 calendar days after notice (to privacy@mollie.com); parties discuss in good faith; if unresolved, customer's sole and exclusive remedy is to terminate the DPA for convenience |
| Obligations passed to subprocessors | written agreement with each Sub-processor requiring obligations equivalent to those in this DPA, after due diligence |
| Breach notification | without undue delay after discovery |
| Deletion when the service ends | On termination, at Controller's request, deletes Personal Data unless EU or member state law requires retaining a copy |
| Getting your data back | On termination, at Controller's request, returns Personal Data to Controller or to a processor Controller nominates |
| Requests from data subjects | Advises the data subject to submit the request to Controller and/or forwards it to Controller; on request and at Controller's expense, provides reasonable assistance where Controller cannot fulfil requests independently |
| Audit | audit reports on request upon reasonable notice, by written request to privacy@mollie.com; confidential, not shared externally |
| Processing on your instructions | only in accordance with Controller's documented instructions; persons under its authority process only on Controller's instructions |
| Confidentiality of staff | Employees, agents, officers and contractors with access are contractually bound to keep Personal Data confidential |
| Security measures | appropriate technical and organisational procedures, considering state of the art, costs, nature/scope/context/purposes and risk |
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
We found no version number or date in the agreement as we read it.
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 Mollie have a SOC 2 report?
Mollie 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.
- Claimed “SOC 2 Type 2 Our security, availability, and confidentiality controls are independently assessed against the AICPA's Trust Services Criteria”
Source: mollie.com, 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 |
|---|---|---|---|---|
| ISAE 3402 Type 2 | Claimed | operational controls audited annually by an external auditor | mollie.com | 2026-10-08 |
| Licensed Institution | Claimed | fully licensed financial and e-money institution in both the EU and UK, regulated by the Dutch Central Bank (DNB) and the UK's Financial Conduct Authority (FCA) | mollie.com | 2026-10-08 |
| PCI-DSS Level 1 · PCIDSS | Claimed | processing card payments; Attestation of Compliance (AoC) referenced but not linked | mollie.com | 2026-10-08 |
| SOC 2 Type 2 · SOC2T2 | Claimed | security, availability, and confidentiality controls independently assessed against the AICPA's Trust Services Criteria | mollie.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 Mollie; Mollie B.V.
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Mollie; Mollie B.V.
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Mollie; Mollie B.V.
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Mollie; Mollie B.V.
- Data Privacy Framework List (US): checked 2026-11-16, no entry under Mollie; Mollie B.V.
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Mollie; Mollie B.V.
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Mollie; Mollie B.V.
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under Mollie; Mollie B.V.
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Mollie; Mollie B.V.
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Mollie; Mollie B.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 |
|---|---|---|---|---|---|
| Mollie (service) | — | Service only | unknown | mollie.com | 2026-10-11 |
Vulnerability reporting: hackerone.com, responsible-disclosure@mollie.com, security@mollie.com (security.txt, expires 2027-09-01; 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 |
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.