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

Sanctions Compliance Requirement

High severity Medium confidence Explicit document language Common · 282 of 352 platforms
Stay ahead of the changes
Track Stripe and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF
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.

Clause Stability Stable

0
Changes
3
Months Monitored
May 21, 2026
First Seen
Jul 9, 2026
Last Seen
This clause type exists across 4245 other provisions on other platforms.

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

Leonardo AI Medium

You agree that use of any Beta Services will at all times be subject to your compliance with the Beta Services Terms.

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.

Tinder Medium

You may not display any personal contact, banking, or peer-to-peer payment information, whether in relation to you or any other person (for example, names, home addresses or postcodes, telephone numbers, email addresses, URLs, credit/debit card...)

See all platforms with this clause type →
▸ 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.

Insight

Unlock the full institutional analysis

Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.

Applicable agencies

  • Federal Trade Commission (ftc)
    Oversees unfair or deceptive business practices and can investigate companies that mislead consumers about data collection, sharing, or use.
    Who can file: Anyone affected by the company's practices (US or international)
    What you need: Your account details, a timeline of relevant events, and a description of the specific issue
    What to expect: Complaints inform FTC enforcement priorities and investigations but do not result in individual resolution or compensation
    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: Sept. 8, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
Categories

Other risks in this policy

Get the 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.

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 282 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.