Adult Payment Processor Skill
You are an expert on adult content payment processing. You know every major processor, their requirements, integration patterns, and fallback strategies.
Processors — Ranked by Approval Ease
1. CCBill (most common for SaaS adult tools)
- Approval: 3–10 business days. Requires: gov ID, business registration docs, website screenshot, content description
- Fees: 10–14% + $0.30 per transaction for consumer; lower for high volume
- Webhook:
https://api.acaption.com/ccbill-webhook — POST with subscriptionId, clientAccnum, clientSubacc, timestamp, transactionId, billedAmount, billedCurrency
- Compliance docs needed: 2257 statement (US performers), GDPR policy, privacy policy with data retention, explicit content policy
- Contact: milit@ccbill.com (technical), merchant-support@ccbill.com (onboarding)
- Test environment: sandbox.ccbill.com — test cards available after approval
2. SegPay (good for subscriptions)
- Approval: 5–14 days. US-based. Similar docs to CCBill
- Fees: 12–15% depending on chargeback history
- Strong for: recurring subscriptions, upsells, cascade billing
- Weakness: less developer-friendly API than CCBill
3. AllSecure / AllCard (EU-friendly)
- Approval: 7–21 days. EU company — easier for non-US merchants
- Fees: negotiated; typically 8–12%
- Good for: EU VAT handling, SEPA cards, GDPR compliance
- Integration: REST API with tokenisation; supports 3DS2
4. Epoch (legacy, still active)
- Approval: 5–10 days
- Use case: impulse purchases, one-click upsells
- Weakness: dated interface, lower conversion on mobile
5. Paxum (payouts, not consumer billing)
- Not for checkout — used for paying adult performers/affiliates, not for charging customers
Fallback Strategies (while waiting for approval)
Telegram Stars (ACTIVE — Acaption)
- Already live at acaption.com via Telegram bot
- Bot: immediate licence fulfilment on payment
- Limitation: requires Telegram account; not suitable for mainstream consumers
- Conversion: lower than web checkout but zero processor fees (Telegram takes 30%)
Stripe B2B/Agency (ACTIVE)
- Manual invoice via Stripe — works for B2B/agency orders
- Stripe ToS prohibits consumer adult content sales but allows B2B software invoicing
- Keep this path active even after CCBill approval — agencies prefer invoices
Crypto (optional fallback)
- BTCPay Server (self-hosted, no fees) or Coinbase Commerce
- 48h price lock for volatile assets
- Low conversion but zero chargebacks and zero processor dependency
- Add as "Pay with crypto" secondary button — do not make it primary
Lemon Squeezy / Paddle (NOT viable for adult)
- Both explicitly prohibit adult content in ToS — do not apply
Application Process — Step by Step
CCBill Application
- Go to ccbill.com/contact → "Become a Merchant"
- Documents needed:
- Valid government-issued photo ID
- Business registration certificate or Articles of Incorporation
- Screenshot of website with "Members Area" shown
- Written description: "Software SaaS tool for adult content creators — captions/tags generation, no hosted media"
- 2257 compliance statement (for tools that handle user-uploaded content)
- After approval:
- Get
clientAccnum and clientSubacc from dashboard
- Set webhook URL in CCBill Merchant Dashboard → Postback URL
- Use FlexForms for checkout (hosted) or Direct Post API (integrated)
- Test with sandbox before going live
2257 Statement (required for tools that process adult imagery)
Even for SaaS tools that don't host content, include:
This website is not a producer of sexually explicit content. We provide software tools to
content creators. Records required by 18 U.S.C. §2257 are maintained by the primary producer.
Webhook Integration Pattern (CCBill)
# Flask example — adapt to your framework
@app.route('/ccbill-webhook', methods=['POST'])
def ccbill_webhook():
data = request.form # CCBill sends form-encoded POST
event_type = data.get('eventType') # 'NewSaleSuccess', 'Cancellation', 'RenewalSuccess'
subscription_id = data.get('subscriptionId')
amount = float(data.get('billedAmount', 0))
currency = data.get('billedCurrency', 'USD')
# Verify with CCBill's digest
# md5(clientAccnum + clientSubacc + subscriptionId + transactionId + billedAmount + billedCurrency + salt)
if event_type == 'NewSaleSuccess':
# provision licence
pass
elif event_type == 'Cancellation':
# revoke licence
pass
elif event_type == 'RenewalSuccess':
# extend expiry
pass
return 'OK', 200
Compliance Checklist (before going live)
Pricing Strategy for Adult SaaS
- Higher than universal equivalents — adult buyers expect premium pricing; ~20–30% above comparable universal tool
- Annual vs monthly: monthly has higher chargeback rate; push annual with 2-month discount
- One-time licence: lower chargeback risk than subscriptions; preferred by adult buyers who distrust recurring billing
- Refund window: 3 days visible in checkout reduces chargebacks (buyers who intend to dispute often give up if they see a refund path)
1---2name: adult-payment-processor3description: Guide for adult content payment processor selection, merchant account application, compliance, webhook integration, and fallback strategies (CCBill, SegPay, AllSecure, Epoch, Telegram Stars, crypto)4---5
6# Adult Payment Processor Skill
7
8You are an expert on adult content payment processing. You know every major processor, their requirements, integration patterns, and fallback strategies.
9
10## Processors — Ranked by Approval Ease
11
12### 1. CCBill (most common for SaaS adult tools)
13- **Approval**: 3–10 business days. Requires: gov ID, business registration docs, website screenshot, content description
14- **Fees**: 10–14% + $0.30 per transaction for consumer; lower for high volume
15- **Webhook**: `https://api.acaption.com/ccbill-webhook` — POST with `subscriptionId`, `clientAccnum`, `clientSubacc`, `timestamp`, `transactionId`, `billedAmount`, `billedCurrency`
16- **Compliance docs needed**: 2257 statement (US performers), GDPR policy, privacy policy with data retention, explicit content policy
17- **Contact**: milit@ccbill.com (technical), merchant-support@ccbill.com (onboarding)
18- **Test environment**: sandbox.ccbill.com — test cards available after approval
19
20### 2. SegPay (good for subscriptions)
21- **Approval**: 5–14 days. US-based. Similar docs to CCBill
22- **Fees**: 12–15% depending on chargeback history
23- **Strong for**: recurring subscriptions, upsells, cascade billing
24- **Weakness**: less developer-friendly API than CCBill
25
26### 3. AllSecure / AllCard (EU-friendly)
27- **Approval**: 7–21 days. EU company — easier for non-US merchants
28- **Fees**: negotiated; typically 8–12%
29- **Good for**: EU VAT handling, SEPA cards, GDPR compliance
30- **Integration**: REST API with tokenisation; supports 3DS2
31
32### 4. Epoch (legacy, still active)
33- **Approval**: 5–10 days
34- **Use case**: impulse purchases, one-click upsells
35- **Weakness**: dated interface, lower conversion on mobile
36
37### 5. Paxum (payouts, not consumer billing)
38- **Not for checkout** — used for paying adult performers/affiliates, not for charging customers
39
40---
41
42## Fallback Strategies (while waiting for approval)
43
44### Telegram Stars (ACTIVE — Acaption)
45- Already live at acaption.com via Telegram bot
46- Bot: immediate licence fulfilment on payment
47- Limitation: requires Telegram account; not suitable for mainstream consumers
48- Conversion: lower than web checkout but zero processor fees (Telegram takes 30%)
49
50### Stripe B2B/Agency (ACTIVE)
51- Manual invoice via Stripe — works for B2B/agency orders
52- Stripe ToS prohibits consumer adult content sales but allows B2B software invoicing
53- Keep this path active even after CCBill approval — agencies prefer invoices
54
55### Crypto (optional fallback)
56- BTCPay Server (self-hosted, no fees) or Coinbase Commerce
57- 48h price lock for volatile assets
58- Low conversion but zero chargebacks and zero processor dependency
59- Add as "Pay with crypto" secondary button — do not make it primary
60
61### Lemon Squeezy / Paddle (NOT viable for adult)
62- Both explicitly prohibit adult content in ToS — do not apply
63
64---
65
66## Application Process — Step by Step
67
68### CCBill Application
691. Go to ccbill.com/contact → "Become a Merchant"
702. Documents needed:
71 - Valid government-issued photo ID
72 - Business registration certificate or Articles of Incorporation
73 - Screenshot of website with "Members Area" shown
74 - Written description: "Software SaaS tool for adult content creators — captions/tags generation, no hosted media"
75 - 2257 compliance statement (for tools that handle user-uploaded content)
763. After approval:
77 - Get `clientAccnum` and `clientSubacc` from dashboard
78 - Set webhook URL in CCBill Merchant Dashboard → Postback URL
79 - Use FlexForms for checkout (hosted) or Direct Post API (integrated)
804. Test with sandbox before going live
81
82### 2257 Statement (required for tools that process adult imagery)
83Even for SaaS tools that don't host content, include:
84```
85This website is not a producer of sexually explicit content. We provide software tools to
86content creators. Records required by 18 U.S.C. §2257 are maintained by the primary producer.
87```
88
89---
90
91## Webhook Integration Pattern (CCBill)
92
93```python
94# Flask example — adapt to your framework
95@app.route('/ccbill-webhook', methods=['POST'])
96def ccbill_webhook():
97 data = request.form # CCBill sends form-encoded POST
98
99 event_type = data.get('eventType') # 'NewSaleSuccess', 'Cancellation', 'RenewalSuccess'
100 subscription_id = data.get('subscriptionId')
101 amount = float(data.get('billedAmount', 0))
102 currency = data.get('billedCurrency', 'USD')
103
104 # Verify with CCBill's digest
105 # md5(clientAccnum + clientSubacc + subscriptionId + transactionId + billedAmount + billedCurrency + salt)
106
107 if event_type == 'NewSaleSuccess':
108 # provision licence
109 pass
110 elif event_type == 'Cancellation':
111 # revoke licence
112 pass
113 elif event_type == 'RenewalSuccess':
114 # extend expiry
115 pass
116
117 return 'OK', 200
118```
119
120---
121
122## Compliance Checklist (before going live)
123- [ ] Age verification page / disclaimer on entry
124- [ ] Clear adult content warning in metadata and footer
125- [ ] Privacy policy with: data collected, retention period, GDPR rights, xAI/third-party disclosure
126- [ ] Refund policy (3–7 day money-back is standard; CCBill requires one)
127- [ ] 2257 statement (even for tool SaaS)
128- [ ] DMCA takedown contact in footer
129- [ ] No minors clause in Terms of Service
130
131---
132
133## Pricing Strategy for Adult SaaS
134- **Higher than universal equivalents** — adult buyers expect premium pricing; ~20–30% above comparable universal tool
135- **Annual vs monthly**: monthly has higher chargeback rate; push annual with 2-month discount
136- **One-time licence**: lower chargeback risk than subscriptions; preferred by adult buyers who distrust recurring billing
137- **Refund window**: 3 days visible in checkout reduces chargebacks (buyers who intend to dispute often give up if they see a refund path)