Most platforms that use Stripe have read the restricted businesses list once, during onboarding, and never returned to it. That is understandable. The list reads like it is about your business. But if you pay out to creators, sellers, or any third parties, section 6.3 is not primarily about your business at all. It is about theirs. And the gap between those two readings is where platforms get surprised.

This article walks through what Stripe's restricted businesses list covers, how it applies to a platform that pays out to creators, and why the practical risk almost always sits with the people you pay rather than with the platform itself.

What section 6.3 actually is

Stripe publishes a list of businesses and activities it either prohibits outright or restricts to specific conditions. It lives in Stripe's Services Agreement and its linked restricted businesses page, and section 6.3 is the clause that binds you to it. When you agreed to Stripe's terms, you agreed that you would not use the service — directly or indirectly — for any of the listed activities.

The phrase that matters most there is indirectly. A platform does not have to sell a prohibited product itself to breach section 6.3. If it processes payments that flow to a prohibited activity, that is enough. For a platform that pays out to creators, every creator is a potential indirect use of your Stripe account.

The categories that matter for creator platforms

The full list is long and covers everything from unlicensed money transmission to specific regulated industries. A handful of categories account for most of the real exposure in the creator economy:

Intellectual property infringement. This is the big one. It covers pirated media, unlicensed streaming, counterfeit goods, and the sale of content someone else owns. A creator selling access to pirated streams or knock-off merchandise falls squarely here, even if their storefront describes something entirely innocent.

Adult content. Stripe permits some adult content under specific conditions and prohibits other categories entirely. The lines are precise and jurisdiction-dependent, which makes this an area where good-faith creators and platforms can drift offside without realizing it.

Regulated and controlled substances. Products that are legal in some places and not others, or that require licensing the seller does not have, fall here. The category is broader than illegal drugs; it reaches into supplements, certain wellness products, and anything with a regulatory gate.

Weapons, gambling, and multi-level marketing. Each has its own conditions. Unlicensed gambling and pyramid-style MLM schemes are prohibited; certain weapons sales are restricted rather than banned.

The common thread is that none of these are obvious from a creator's public profile. A creator does not label their storefront "prohibited." The violation is usually in what they actually sell, where their buyers come from, and what they link to — not in their stated business.

Why the risk sits with your creators

Here is the structural problem. Your platform did its own compliance review when it signed up with Stripe. Your business is clean. But section 6.3 does not stop at your business. It extends to every payout, and you did not run a Stripe-grade compliance review on each of your creators. You almost certainly cannot, at least not manually, once you are past a few hundred of them.

This is the policy-versus-reality gap. Your terms of service almost certainly prohibit the same things Stripe prohibits. On paper, you are covered. But a term of service is only as strong as its enforcement, and content-level enforcement misses the cases that matter most — the creator whose on-platform storefront is spotless and whose actual business is visible only off-platform.

A creator can present a storefront selling recipe bundles while directing buyers of pirated streams to pay through that same profile. Nothing in the on-platform content trips a filter. The violation is real, it is a section 6.3 breach, and it is your Stripe account that carries the exposure.

What enforcement looks like

When Stripe identifies a restricted-business violation tied to your account, the response can range from a request for information, to a hold on funds, to an increased reserve requirement, to termination in serious or repeated cases. Fine amounts vary widely with the processor and the severity of the violation, commonly landing anywhere from the low tens of thousands to well over a hundred thousand dollars.

The more durable cost is not the individual fine. It is what a pattern of violations does to your standing — higher reserves that constrain cash flow, closer monitoring, and, in the worst case, termination that can lead to a MATCH listing and years of difficulty securing a replacement processor. The enforcement cascade is designed so that each stage is more expensive than the last.

The practical takeaway

Reading section 6.3 as a description of your own business is the mistake. Read it instead as a description of every payout you make. The question it poses is not "is my platform compliant?" but "is every creator I pay compliant, and can I see the cases where they are not?"

That second question is the hard one, because the answer lives in signals that content moderation and manual review do not reach: what a creator actually sells versus what they claim, where their traffic comes from, and where their outbound links point. Catching a section 6.3 violation before the payout that triggers it is the difference between a non-event and the first step of the enforcement cascade.

This article is provided for general educational purposes and is not legal or compliance advice. It is not endorsed by or affiliated with Stripe. Consult Stripe's official restricted businesses list and Services Agreement, and qualified counsel, for definitive requirements. Tumban provides advisory risk guidance and does not guarantee compliance outcomes.