Checkout.com · Checkout.com Terms · View original document ↗

Data Processing and Payment Card Data Handling

High severity Low confidence Inferredfromcontext Unique · 0 of 325 platforms
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for Checkout.com Create a free account to receive the weekly governance digest and monitor one platform for governance changes.
Create free account No credit card required.
Document Record

What it is

Checkout.com processes payment card data and personal data on behalf of merchants, which creates obligations under PCI DSS and applicable data protection laws including GDPR. Merchants are typically required to enter into a data processing agreement as part of the onboarding process.

This analysis describes what Checkout.com's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

As a payment processor handling card data, Checkout.com's data practices directly affect how sensitive financial information belonging to end customers is stored, processed, and protected.

Interpretive note: The specific data processing terms were not rendered in the truncated document; this analysis is based on standard regulatory requirements applicable to Checkout.com's business model and the document's references to privacy policies in its legal hub navigation.

Consumer impact (what this means for users)

End customers whose card details are processed through Checkout.com have their payment data subject to Checkout.com's security and data protection practices, making the adequacy of those practices material to cardholder security.

How other platforms handle this

Oura Medium

If you access or use any of Oura's location-based services, such as by enabling GPS-based activity tracking through our Services, Oura may process the approximate or precise location of your device while the service is active. This data may be obtained via your device's service provider network ID, ...

AWS Bedrock Medium

AWS processes Customer Content you submit to Amazon Bedrock in accordance with the AWS Customer Agreement and applicable data protection terms. AWS does not use Customer Content processed by Amazon Bedrock to train Amazon's foundation models without your consent.

Dun & Bradstreet Medium

We process many types of data to support business decisioning, including data about people, businesses, organizations, places, economic activity, sustainability, legal, and other significant business events, and third-party risks. Some of the data we process is considered personal data. Some of the ...

See all platforms with this clause type →

Monitoring

Checkout.com has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.

Start Watcher free trial Or create a free account →
ConductAtlas Analysis

Institutional analysis (Compliance & governance intelligence)

(1) REGULATORY LANDSCAPE: Payment card data handling engages PCI DSS as the primary technical standard, GDPR and UK GDPR for personal data processed about EU and UK data subjects, and the Payment Card Industry Security Standards Council's requirements. The UK ICO and EU data protection authorities enforce GDPR compliance. In the US, state privacy laws including CCPA may apply depending on the cardholder's location. (2) GOVERNANCE EXPOSURE: High. As a data processor for merchants, Checkout.com's data processing agreement must satisfy GDPR Article 28 requirements. Merchants act as data controllers and bear accountability for ensuring the processor agreement is adequate. Failure to execute a compliant DPA creates regulatory exposure for the merchant, not just Checkout.com. (3) JURISDICTION FLAGS: EU and UK merchants face mandatory DPA requirements under GDPR and UK GDPR. California merchants and those serving California residents should assess CCPA data sharing implications. Cross-border data transfers outside the EEA require appropriate transfer mechanisms such as Standard Contractual Clauses. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams must obtain and review Checkout.com's data processing addendum prior to go-live. The DPA should specify data retention periods, sub-processor lists, breach notification timelines, and data subject rights support obligations. (5) COMPLIANCE CONSIDERATIONS: Data mapping exercises should document the flow of payment and personal data through Checkout.com's infrastructure. Breach notification procedures should be aligned with Checkout.com's stated timelines and applicable regulatory requirements of 72 hours under GDPR.

Full compliance analysis

Regulatory citations, enforcement risk, and due diligence action items.

Track 1 platform — free Try Watcher free for 14 days

Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.

Applicable agencies

  • FTC
    The FTC oversees data security practices of payment processors serving US consumers and has authority over unfair or deceptive data handling practices
    File a complaint →

Applicable regulations

CCPA/CPRA
California, USA
ePrivacy Directive
European Union
FCRA
United States Federal
FTC Act Section 5
United States Federal
GDPR
European Union
GLBA
United States Federal

Provision details

Document information
Document
Checkout.com Terms
Entity
Checkout.com
Document last updated
May 5, 2026
Tracking information
First tracked
May 7, 2026
Last verified
May 10, 2026
Record ID
CA-P-008565
Document ID
CA-D-00662
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
b7bcf1d02b7a882de41fec813b6d8003150951ca3da3369ec07660cc5c1ab538
Analysis generated
May 7, 2026 20:58 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Checkout.com
Document: Checkout.com Terms
Record ID: CA-P-008565
Captured: 2026-05-07 20:58:42 UTC
SHA-256: b7bcf1d02b7a882d…
URL: https://conductatlas.com/platform/checkoutcom/checkoutcom-terms/data-processing-and-payment-card-data-handling/
Accessed: May 13, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
Categories

Other risks in this policy

Related Analysis

Professional Governance Intelligence

Need to monitor specific governance provisions?

Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Start Professional free trial

Or start with Watcher →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does Checkout.com's Data Processing and Payment Card Data Handling clause do?

As a payment processor handling card data, Checkout.com's data practices directly affect how sensitive financial information belonging to end customers is stored, processed, and protected.

How does this clause affect you?

End customers whose card details are processed through Checkout.com have their payment data subject to Checkout.com's security and data protection practices, making the adequacy of those practices material to cardholder security.

Is ConductAtlas affiliated with Checkout.com?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Checkout.com.