Strong avoid for MVP
Stripe, PayPal, and Lemon Squeezy are poor first choices because their official policy/terms pages create direct adult-content friction for this use case.
Payment provider decision matrix
Choose the processor by evidence, not convenience.
Nocturne needs a payment partner that can explicitly support synthetic adult digital content, recurring access, one-time passes, disputes, privacy-preserving hosted checkout, and jurisdiction/tax requirements without forcing the platform to build an identity dossier.
Research checkpoint: June 18, 2026
Provider-neutral code remains default
Hosted checkout preferred
No raw webhook payload storage
Decision rule
Do not implement a provider-specific checkout, webhook endpoint, or subscription adapter until the provider confirms the exact content category, AI/synthetic posture, account jurisdiction, subscription/pass model, dispute handling, and tax/VAT packaging.
The current codebase already has the correct foundation: provider-neutral checkout sessions, stale-session expiry cleanup, a payment proof ledger, linked entitlements, and a replayable webhook inbox that stores provider/event/reference identifiers and normalized payment state without storing card data, raw payloads, payment customer identity, raw IP addresses, or user-agent strings. Browser success/cancel returns are recorded only as checkout state and never grant access.
Short answer
Recommended payment direction
Primary outreach shortlist
CCBill and Verotel are the clearest source-backed adult/high-risk digital-content candidates in this pass. Treat them as outreach targets, not guaranteed approvals.
Manual confirmation lane
Segpay, Epoch, RocketGate, and other adult/high-risk processors can be evaluated only after current official policy or direct sales/legal confirmation is captured.
Current implementation stance: keep Nocturne provider-neutral. The local checkout skeleton may create internal pending sessions, non-authoritative return states, and local expiry cleanup, but hosted checkout redirects, provider adapters, public webhook endpoints, and signature verification remain blocked until written approval; otherwise the project risks building integration code for a processor that rejects the business.
Fit criteria
Provider scoring dimensions
| Dimension | Required MVP answer | Why it matters |
|---|---|---|
| Adult digital content support | Provider explicitly permits paid access to adult images/videos in the intended niche. | Mainstream processors often prohibit or restrict this category; ambiguous approval is not enough. |
| AI/synthetic content posture | Provider confirms synthetic adult media is permitted, including the platform's AI-generated content disclosure model. | Some policies now call out AI-generated adult content directly; adult-friendly does not automatically mean AI-friendly. |
| Subscription + pass model | Supports recurring $20/month membership and/or a one-time 30-day pass. | The current entitlement model supports both; public packaging should follow provider and tax realities. |
| Hosted checkout/tokenization | Provider owns card entry, token storage, and PCI-heavy surfaces. | Nocturne should not touch card data or build payment identity records. |
| Webhooks and replay | Signed webhook events with stable event IDs, order/session references, refunds, chargebacks, voids, cancellations, expiry, and replay safety. | The existing replay inbox is designed around idempotent normalized events and linked entitlement revocation. |
| Dispute/chargeback tooling | Clear dispute notification, chargeback threshold rules, evidence expectations, and account-risk escalation. | Adult memberships can be dispute-prone; access revocation must be fast and narrow. |
| EU/entity/tax fit | Supports the chosen entity, settlement location, VAT/MoR responsibilities, and prohibited-country rules. | Public launch readiness depends on jurisdiction and tax/accounting packaging, not only API shape. |
| Privacy fit | Nocturne can store only pseudonymous member ID, plan, provider label, provider order/session/event references, amount/currency, status, timestamps, optional note, and payload digest. | The processor may know payment identity; Nocturne should not duplicate it unless a specific legal/accounting need exists. |
| Operational durability | Documented onboarding, support channel, reserve policy, payout timing, account termination triggers, and migration/export path. | A sudden processor shutdown is an existential risk for a single-creator paid platform. |
Decision matrix
Provider candidates and current stance
| Provider | Official evidence captured | Risk read | Current stance |
|---|---|---|---|
| Stripe | Restricted Businesses page places adult content/services and mature sexual-gratification media in the restricted/prohibited area and explicitly reaches AI-generated content that meets the adult-content criteria. | Very high rejection/account-risk for this project. | Avoid for MVP. Do not build against Stripe unless counsel and Stripe approval create a written exception. |
| PayPal | Acceptable Use Policy has a mature-audience-content section covering adult digital delivery, including VOD/webcam-style categories, with jurisdiction restrictions. | High policy and account-freeze risk. | Avoid for MVP. Do not make PayPal the core entitlement rail. |
| Lemon Squeezy | Terms prohibit illegal or age-restricted products including sexually oriented or pornographic content and products restricted by payment-processing partners. | Poor fit despite merchant-of-record convenience. | Avoid for MVP. MoR simplicity does not overcome the adult-content prohibition. |
| CCBill | Official site advertises subscription processing, adult business support, and content creator platform payments for mainstream and adult content platforms. | Promising adult-capable processor; AI/synthetic policy and privacy-fit details still need written confirmation. | Primary outreach shortlist. Ask for approval covering synthetic adult images/videos, subscription/pass flows, EU/entity fit, chargebacks, and webhook semantics. |
| Verotel | Official site positions Verotel as an Internet Payment Service Provider for high-risk webmasters, digital content, entertainment websites, and adult-related payments. | Promising adult/high-risk digital-content candidate; AI/synthetic and integration terms still need written confirmation. | Primary outreach shortlist. Validate hosted checkout, recurring/pass support, webhook coverage, EU/tax posture, and privacy/data minimization fit. |
| Segpay | Automated official-site retrieval was blocked during this pass, so no current official excerpt is captured here. | Possible adult/high-risk candidate, but evidence confidence is too low for implementation decisions. | Manual confirmation only. Contact directly or capture current official policy before scoring. |
| Epoch | Official homepage confirms online payment processing positioning, but this pass did not capture explicit adult or AI-adult policy language. | Potential processor only if direct policy confirmation supports this category. | Secondary outreach. Do not prioritize code integration without written content-category approval. |
| RocketGate / other high-risk gateways | No sufficiently current official adult/AI-adult evidence was captured in this pass. | Unknown fit; may be useful only through direct sales/legal confirmation. | Backlog candidate. Evaluate after CCBill/Verotel and any directly confirmed adult specialist. |
Vendor questionnaire
Questions to answer before integration
- Will you approve a private paid membership site for clearly labeled AI-generated adult images and videos in a transgender/futanari synthetic niche?
- Do your prohibited-content rules allow fully synthetic adult fantasy content when the platform prohibits CSAM, age ambiguity, coercion, non-consensual framing, real-person likeness targeting, user-uploaded adult media, and creator marketplace activity?
- Can you support a $20 monthly subscription and a one-time 30-day pass, both through hosted checkout?
- Which payment identity fields must Nocturne store, if any, beyond provider order/session/event references and normalized status?
- Do webhook events include signed payloads, stable event IDs, checkout/order references, subscription lifecycle events, refund/void/chargeback events, retry metadata, and replay guidance?
- Do you require Nocturne to store raw webhook payloads, customer email, customer name, raw IP address, user-agent string, ID documents, or other payment identity fields?
- Can the account be under the planned legal entity and hosting jurisdiction, and which countries/regions must be blocked or unsupported?
- Who handles VAT/sales tax/digital-services tax, invoices/receipts, descriptors, refunds, reserves, chargeback evidence, and payout reporting?
- What are the age-assurance expectations for adult digital content, and can Nocturne satisfy them with self-attestation or pass/fail third-party proof rather than storing ID documents?
- What would trigger account termination, reserves, rolling holds, content review, or retroactive rejection?
Approval artifact: save the provider's written approval, prohibited-content interpretation, webhook docs, tax position, and data-retention requirements before writing provider-specific adapter code.
Implementation guardrail
Provider-neutral adapter shape
| Boundary | Allowed Nocturne data | Rejected by default |
|---|---|---|
| Checkout create | member_id, plan_key, nonce/CSRF proof, return URL, provider label, internal checkout_session_id. | Card data, billing identity, browser fingerprint, raw IP-ledger, tracking pixels. |
| Checkout return | Internal checkout ID, provider checkout/session/order reference when approved, generic success/pending/failure state, and local expiry state when stale. | Assuming payment success from the browser return alone or granting access before webhook/proof replay. |
| Webhook ingest | Provider, event ID, event type, provider reference, amount/currency, normalized status, payload digest, signature verification result, replay state. | Raw payload storage, customer identity duplication, raw IP/user-agent persistence. |
| Entitlement sync | Linked payment proof ID and linked entitlement ID with exact grant/revoke timestamps. | Broad member lockouts when only one payment reference is reversed. |
| Dispute handling | Status update, event note, linked entitlement revocation, minimal evidence reference. | Permanent behavior dossiers or public shaming/leaderboards. |
Evidence artifact
Record provider fit without leaking processor data
After written provider evidence exists, generate a local payment-provider review artifact and verify it before recording payment_provider_review deployment evidence. The artifact is checklist/result metadata only; raw approval emails, contracts, processor dashboards, provider credentials, webhook secrets, card data, customer identity, raw payloads, IP addresses, and user-agent strings stay outside git and chat.
cargo run -- payment-provider-review-plan \
--artifact-file deployment_evidence/payment-provider-review.txt \
--provider manual \
--review-result passed
cargo run -- payment-provider-review-artifact-check \
--artifact-file deployment_evidence/payment-provider-review.txtThe plan supports ccbill, verotel, segpay, epoch, rocketgate, crypto, manual, and other provider postures. A pending artifact is useful as a checklist but is intentionally not recordable evidence; use passed, warning, or failed only after the written review is complete.
Boundary: this flow does not contact processors or approve a provider. It only makes the human provider decision auditable, repeatable, and safe to hash into deployment evidence.
Sources
Official source pages reviewed
| Provider | Source | Evidence confidence |
|---|---|---|
| Stripe | Stripe Restricted Businesses | High — official policy page fetched. |
| PayPal | PayPal Acceptable Use Policy | High — official policy page fetched. |
| Lemon Squeezy | Lemon Squeezy Terms | High — official terms page fetched. |
| CCBill | CCBill Payment Processing Services and CCBill Industries | Medium-high — official marketing/category pages fetched; direct approval still needed. |
| Verotel | Verotel Homepage | Medium — official site fetched; direct approval and technical docs still needed. |
| Epoch | Epoch Homepage | Low-medium — official site fetched but adult/AI-adult fit not established. |
| Segpay | Segpay Homepage | Low — automated review was blocked; direct confirmation required. |
This page is a planning artifact, not legal advice. Provider policies can change; re-check official pages and obtain written approval before public launch.