Payment Processors and Erotica

This is the part of publishing erotica that nobody signs up for. A platform's content policy can say explicit fiction is welcome and the payments can still stop, because the company moving the money has its own list and that list was not written with novelists in mind. The page sticks to what processors and platforms publish, which is also the rule across this section for writers. Nothing here describes what any company does in practice when it is not writing it down.

What the processors publish

Stripe is the one that matters most in this niche, because it is the processor behind several of the platforms where erotica writers take money. Its prohibited and restricted businesses page lists, among prohibited businesses, pornography and other mature audience content designed for the purpose of sexual gratification, and the parenthesis is the part writers need to read: it names literature alongside imagery and other media. A separate entry covers AI-generated content meeting the same criteria. The page was last updated on 22 September 2026.

Mastercard's published position comes from a 2021 statement describing what it requires of banks whose merchants sell adult content: clear, unambiguous and documented consent, documented age and identity verification for people depicted and for people uploading, content review before publication, a complaints process and an appeals process. The rule text sits in its security rules for specialty merchant registration. Read carefully, most of that is about real people rather than fiction, so it falls hardest on platforms hosting audio or images of performers rather than on a writer selling a novel. We have not read Visa's adult-merchant requirements from a primary source and so state none.

PayPal is a deliberate blank. Its acceptable use policy was fetched and came back truncated, so no wording is recorded and none is published here. That is unsatisfying and it is better than paraphrasing a policy we could not read.

How a processor's rule becomes a platform's

The mechanism is simple and it is documented. A platform that does not move money itself has to agree to the rules of whoever does, and then passes those rules down to its creators as its own terms.

Ream's entry is the most unusual thing in this section, because the subject is normally not discussed at all. A platform telling erotica authors, in a help article, that it is watching its processor and has a plan if the position changes is a different posture from a platform that mentions processors only in a warning.

The ebook stores sit outside this mechanism. Amazon, Apple, Google, Kobo and Barnes & Noble take the reader's money themselves and pay you afterwards, so there is no processor account of yours to close. The equivalent risk there is the content rule, and it has teeth of its own: Amazon's terms let it refuse or recover royalties on a book it decides breached its guidelines, and Google's publisher policies list suspending payments, temporarily or permanently, among its enforcement actions. Those are covered on where erotica is banned.

One writer's account, with its dates

There is one first-hand account in our research, published by the author herself, and it is worth reading as an example rather than as a rule. In October 2023 Cornelia Quick wrote on her own newsletter that Stripe was beginning to enforce its adult-content rule, that the word literature in the rule was the problem for erotica writers, and that she was weighing a move to another subscription platform; she described her newsletter, Medium and Ream as small income streams next to her book sales but valuable for discoverability. In December 2023 she wrote that Stripe had told her the account was in violation of its services agreement for selling adult content and would be closed later that month unless an appeal succeeded. She disabled the paid link, made the series free, and moved paid access to other platforms. The outcome of the appeal is not stated on the pages we read, and her current newsletter About page says stories are not offered to subscribers there.

That is one author's experience of one closure in one year, not evidence of a pattern, and nothing in it says what any company would do today. What it does show is the shape of the risk: the notice came from the processor rather than the platform, it arrived with a deadline, and the fix was to move the paid link rather than to change the writing. Her full record is on her author page.

What a writer can do with published facts

Three things follow from the documentation and none of them requires guessing.

First, know whose account the money sits in. On Ream's Direct integration the payouts run through the author's own Stripe account, which means Stripe's list applies to you directly rather than to the platform. On Substack the platform holds the relationship, since its payouts article names Stripe as its sole payment provider, and Patreon runs its own payout methods on top of its processors. Ko-fi and Payhip both describe payments through PayPal or Stripe without the pages we read saying whose account the money lands in first. Neither arrangement is safer in the abstract, but they fail differently, and knowing which one you are in tells you who would send the notice.

Second, prefer the routes with more than one way to pay you. Patreon documents four payout methods, Draft2Digital four, and Amazon three; Substack documents one. A single route is a single point of failure, and the fee differences between them are on what the platforms charge.

Third, keep the store routes and the direct routes separate in your planning. The stores carry content risk but no processor risk for you, and the direct platforms carry the reverse. A writer with books on one and a membership on the other is not exposed to both failures at once, which is also the practical argument in subscription against pay per story.

What this page will not tell you

We cannot see which processor handles your account at any of these platforms, and the payment relationship is not published per creator, so no platform is matched to a rule here. We have not read Visa's requirements or PayPal's policy wording from a primary source, so neither is described. And we will not characterise what any company does when it is not writing it down, which is the whole of the available commentary on this subject elsewhere. Where the documentation runs out, so does this page.