Data processing agreement in Payment processing
Without a published DPA you cannot review the contract before you talk to sales.
7 of 33 companies we measured here publish it, that is 21%. Last checked 2026-10-16.
21% here against 11% across every category we measure. Payment processing sits above the overall share for this criterion.
This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.
Back to Data processing agreement across all categories, or to Payment processing.
- Found7
- Not found at checked addresses26
- Not measured4
37 companies in total. Unmeasured companies are excluded from the published share.
Published
Published and readable without a login.
| Vendor | What we found |
|---|---|
| Adyen | https://www.adyen.com/legal/data-processing-agreementChecked |
| Creem | https://www.creem.io/dpaChecked |
| GoCardless | https://gocardless.com/legal/gdprChecked |
| Lemon Squeezy | https://www.lemonsqueezy.com/dpaChecked |
| Maxio | https://www.maxio.com/dpaChecked |
| Mollie | https://www.mollie.com/legal/data-processing-agreementChecked |
| Paddle | https://www.paddle.com/legal/data-processing-addendumChecked |
No data processing agreement found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| Airwallex | 8 addresses checkedChecked |
| Aria Systems | 8 addresses checkedChecked |
| Bolt | 8 addresses checkedChecked |
| CFS MerchantXpress | 8 addresses checkedChecked |
| Chargebee | 8 addresses checkedChecked |
| Checkout.com | 8 addresses checkedChecked |
| CORE Cashless | 8 addresses checkedChecked |
| Klarna | 8 addresses checkedChecked |
| Mangopay | 8 addresses checkedChecked |
| Nexi | 8 addresses checkedChecked |
| Novalnet | 8 addresses checkedChecked |
| Nuvei | 8 addresses checkedChecked |
| Payoneer | 8 addresses checkedChecked |
| Payrexx | 8 addresses checkedChecked |
| Rapyd | 8 addresses checkedChecked |
| Razorpay | 8 addresses checkedChecked |
| Recurly | 8 addresses checkedChecked |
| Square | 8 addresses checkedChecked |
| Stancer | 8 addresses checkedChecked |
| Stripe | 8 addresses checkedChecked |
| SumUp | 8 addresses checkedChecked |
| Teller | 8 addresses checkedChecked |
| Unzer | 8 addresses checkedChecked |
| Worldline | 8 addresses checkedChecked |
| zendit | 8 addresses checkedChecked |
| Zuora | 8 addresses checkedChecked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
| Vendor | What we found |
|---|---|
| Computop | The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked |
| FastSpring | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked |
| Paystack | The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked |
| Xendit | The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked |
Other criteria in Payment processing
- Subprocessor list
- Data location stated
- Status page with history
- Public pricing
- Certifications named
- HTTPS enforced with HSTS
- No third-party tracking before consent
- security.txt (RFC 9116)
- Notice before subprocessors change
- Named privacy contact
Data processing agreement in related categories
Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.