Provision record
Stripe · Stripe Acceptable Use Policy · View original document ↗

Sanctions Compliance Requirement

High severity Medium confidence Explicitdocumentlanguage Common · 287 of 352 platforms
Get alerted the next time Stripe changes these terms. Follow Stripe →
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity Stripe recorded 2 documented changes in the last 30 days.
Follow Stripe →
Monitor governance changes for Stripe Monitor emails you the same day this changes. The archive stays free.
Follow Stripe →

Get the weekly research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.

Document Record

What it is

The agreement requires users to comply with prohibitions imposed by relevant sanctions authorities and prohibits use of the End User Services in violation of applicable sanctions regimes.

This analysis describes what Stripe'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)

This provision establishes that users are contractually obligated to comply with applicable sanctions requirements, which may include obligations imposed by U.S. OFAC, EU sanctions authorities, UK OFSI, and other relevant bodies depending on the user's jurisdiction and the nature of transactions conducted.

Interpretive note: The phrase 'relevant sanctions authorities' is not defined in the document, and the scope of applicable sanctions regimes depends on the user's jurisdiction, counterparties, and transaction type.

Consumer impact (what this means for users)

Under this clause, users operating in or transacting with sanctioned jurisdictions or parties may be in breach of the agreement regardless of whether they are directly subject to the relevant sanctions authority's jurisdiction. The phrase 'relevant sanctions authorities' is not defined and may encompass multiple international regimes.

How other platforms handle this

NVIDIA NIM Medium

Customer must comply with any additional terms, restrictions, or limitations (e.g., limitations on the total amount of usage) for a promotional offering as described in the corresponding offer terms.

Upwork Medium

You agree to comply with all applicable local, state, federal and/or international laws or regulations, including those related to AI systems, privacy, and data protection.

McDonald's Medium

Please take steps to secure your access credentials such as login name and password, and do not share them with anyone.

See all platforms with this clause type →

Monitoring

Stripe has changed this document before.

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

Follow Stripe → Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
You must not, and must not allow others to: Use the End User Services in a way that violates prohibitions relevant sanctions authorities impose.

Excerpt from Stripe's Acceptable Use Policy

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

1. REGULATORY LANDSCAPE: This provision directly engages U.S. OFAC sanctions programs, EU Common Foreign and Security Policy sanctions, UK OFSI sanctions, and potentially UN Security Council sanctions regimes. The phrase 'relevant sanctions authorities' is deliberately broad and may encompass multiple overlapping regimes. Non-compliance with OFAC requirements can result in civil and criminal penalties under the International Emergency Economic Powers Act and the Trading With the Enemy Act. 2. GOVERNANCE EXPOSURE: High. The provision places affirmative compliance obligations on users without specifying which sanctions regimes apply or what due diligence is required. Organizations with international operations or cross-border transactions face heightened exposure given the multiplicity of potentially applicable sanctions regimes. 3. JURISDICTION FLAGS: EU users are subject to EU Council regulations implementing sanctions, which may differ from U.S. OFAC programs in scope and covered parties. UK users are subject to OFSI-administered sanctions following Brexit. Users in jurisdictions with limited access to sanctions compliance resources may face practical difficulties meeting the compliance standard implied by this clause. 4. CONTRACT AND VENDOR IMPLICATIONS: For B2B relationships, this clause may require downstream contract amendments to ensure that partners and vendors using Stripe's End User Services in connection with shared workflows are similarly restricted. Procurement teams should assess whether existing vendor agreements adequately address sanctions compliance obligations. 5. COMPLIANCE CONSIDERATIONS: Legal and compliance teams should conduct a sanctions screening review of all counterparties and jurisdictions involved in activities conducted through the End User Services. Where operations span multiple jurisdictions, a multi-regime sanctions compliance program may be required to satisfy the 'relevant sanctions authorities' standard.

Full institutional analysis

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

Applicable agencies

  • FTC
    The FTC may have jurisdiction over consumer protection aspects of sanctions-related restrictions on consumer-facing payment services, though primary enforcement authority over sanctions violations rests with OFAC and equivalent non-U.S. authorities.
    File a complaint →

Applicable regulations

CFAA
United States Federal

Provision details

Document information
Document
Stripe Acceptable Use Policy
Entity
Stripe
Document last updated
May 20, 2026
Tracking information
First tracked
May 21, 2026
Last verified
July 9, 2026
Record ID
CA-P-012837
Document ID
CA-D-00873
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
5abf89f56508f5c9fb041bb2637fd678a25058aac530eca6a3bc24baf4767482
Analysis generated
May 21, 2026 02:06 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Stripe
Document: Stripe Acceptable Use Policy
Record ID: CA-P-012837
Captured: 2026-05-21 02:06:26 UTC
SHA-256: 5abf89f56508f5c9…
URL: https://conductatlas.com/platform/stripe/stripe-acceptable-use-policy/provision/CA-P-012837/sanctions-compliance-requirement/
Accessed: July 25, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
Categories

Other risks in this policy

Governance intelligence across arbitration, AI governance, data rights, indemnification, and retention

Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.

Frequently Asked Questions

What does Stripe's Sanctions Compliance Requirement clause do?

This provision establishes that users are contractually obligated to comply with applicable sanctions requirements, which may include obligations imposed by U.S. OFAC, EU sanctions authorities, UK OFSI, and other relevant bodies depending on the user's jurisdiction and the nature of transactions conducted.

How does this clause affect you?

Under this clause, users operating in or transacting with sanctioned jurisdictions or parties may be in breach of the agreement regardless of whether they are directly subject to the relevant sanctions authority's jurisdiction. The phrase 'relevant sanctions authorities' is not defined and may encompass multiple international regimes.

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 287 platforms. See the full comparison.

Is ConductAtlas affiliated with Stripe?

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