Skip to main content
A complete, card-network-compliant Terms of Service for Pancake merchants. Pick your billing model, replace the bracketed placeholders, publish.
This is a template, not legal advice. Have a lawyer review before publishing if your jurisdiction or business model is unusual.

Pick your billing model

Each model maps to its own billing-specific block (sections 4–7) further down. Pick the card that matches how you charge — it jumps straight to the matching block.

V1 — Subscription

Monthly or yearly recurring. Auto-renews until canceled.

V2 — Credits

Buy credit packs and spend them. Optional auto top-up.

V3 — Hybrid

A plan with credits and extra packs sold separately.

Before you publish

🔴 items are what wins or loses disputes. 🟡 items materially strengthen your defense.
1

🔴 Must be done

  • Legal name filled in (company: legal entity + registered address; individual / sole trader: legal name only — no business address needed)
  • Recurring / auto-top-up authorization in place (if you charge automatically)
  • In-product cancel flow exists (not email-only)
  • Refund policy filled in and shown at checkout
  • Third-party AI providers declared (if you use them)
  • Prohibited-uses list matches your actual product
  • Payment processor named: Waffo Pancake
  • Every contact channel listed is real and monitored
2

🟡 Strongly recommended

  • Billing descriptor set so customers recognize the name on their card statement — the #1 chargeback cause is “I don’t recognize this charge”
  • Annual subscribers get a renewal reminder ~7 days out
  • Free-trial users get a “trial converting” reminder ~7 days out
  • V2/V3 — credits-about-to-expire reminder
3

Final pass

  • Every [placeholder] is replaced with real text
  • Version number and effective date filled in
  • V3 — picked one option from each of the three refund choices
  • Deleted the sections that don’t apply (V1 users remove V2/V3 blocks, etc.)
On the refund policy display: in Pancake, save the refund policy in your store settings — the checkout picks it up automatically. You don’t need to keep two copies in sync.

Template

Copy the common sections below, then pick the billing-specific block that matches your model and slot it in between Section 3 and Section 8. Replace every [placeholder] with your real text.
The template is in English. Translate or localize as your market requires.

Common — sections 1–3 and 8–16

Sections 1–3 & 8–16 (use in every version)

Billing-specific — sections 4–7

Pick the one block that matches your billing model and slot it between Section 3 and Section 8. Delete the other two.

V1 — Subscription

V1 — Subscription (sections 4–7)

V2 — Credits / Top-up

V2 — Credits / Top-up (sections 4–7)

V3 — Hybrid

V3 — Hybrid (sections 4–7)

Section-by-section reference

Each section shows its tier (🔴 load-bearing · 🟡 strongly recommended · ⚪ optional), a one-line summary, and the matching template snippet. Sections 4–7 vary by billing model — pick the one block (V1, V2, or V3) that matches how you charge.

1. Introduction & Acceptance

🔴 load-bearing Names the seller — a company gives its legal entity + registered address; a sole trader / individual gives their legal name only, no business address needed. A brand name alone won’t do. Fill [Legal Name], [Country/Region], [Brief service description], [Website URL]; companies also fill [Legal Registered Address].
Section 1 (common)

2. Service Description

🔴 load-bearing “Digital SaaS, delivered immediately on payment” — the line that pushes back when customers claim non-delivery. Fill [Legal Name], [describe core functionality]. Keep 2.3 only if you depend on third-party AI providers.
Section 2 (common)

3. Account Registration & Eligibility

🔴 load-bearing Establishes that the account holder is responsible — blocks “someone else used my login.” Fill [security@company.com].
Section 3 (common)

4–7. Billing block — V1 Subscription

🔴 load-bearing Plans, recurring authorization, in-product cancel, and refund policy for recurring subscriptions. Section 5.1 is the clause card networks care about most — the customer must explicitly authorize recurring charges. Don’t go with “no refunds”; at minimum give first-time buyers 7 days. Prices stay on your pricing page, not here.
V1 — Subscription (sections 4–7)

4–7. Billing block — V2 Credits / Top-up

🔴 load-bearing Credit packs, one-time purchase authorization, validity, and refunds. Include 5.2 only if you offer auto top-up. State explicitly that consumed credits are non-refundable; allow a 7-day refund on untouched credits.
V2 — Credits / Top-up (sections 4–7)

4–7. Billing block — V3 Hybrid

🔴 load-bearing Subscription plus separately-sold credits. Combines recurring and one-time authorization. Refund section 7.3/7.4/7.5 has three picks (rollover, post-cancellation validity, consumption order) — choose one option each and delete the rest. Explain your choice on your help center too.
V3 — Hybrid (sections 4–7)

8. Billing Disputes

🔴 load-bearing Where customers reach you before going to their bank. Fill [billing@company.com].
Section 8 (common)

9. AI Output & Intellectual Property (if you ship AI)

🔴 load-bearing Customer owns outputs; you have a limited license to process inputs; you don’t train on inputs without consent. Fill [Legal Name] in 9.2; add 9.3 if you use OpenAI / Anthropic / Google or similar.
Section 9 (common)

10. Acceptable Use Policy

🔴 load-bearing What customers can’t do, including AI-specific prohibitions (no competing models, no deepfakes, no impersonating professionals). No placeholders — read the list and make sure it covers your product. For a fuller content policy, pair this with the AUP template.
Section 10 (common)

11. Data, Privacy & Security

🔴 load-bearing PCI-DSS handling plus a privacy-policy link. Pancake merchants: name Waffo Pancake as the processor. Fill [privacy policy URL] (point it at your published privacy policy) and [90] days.
Section 11 (common)

12. Disclaimers & Limitation of Liability

🔴 load-bearing As-is disclaimer + AI-output disclaimer + a 12-month liability cap. Fill [LEGAL NAME] (all caps) and [12] months. Keep §12.2 — it’s the clause that protects you when customers act on AI output and lose money.
Section 12 (common)

13. Term & Termination

🔴 load-bearing When you can suspend, and how customers delete their account. Fill [support@company.com].
Section 13 (common)

14. Governing Law & Dispute Resolution

⚪ optional Jurisdiction + an optional arbitration clause. Fill [Country / State / Region] and [legal@company.com]. The arbitration sentence is optional — confirm with a lawyer if unsure.
Section 14 (common)

15. General Provisions

🔴 load-bearing Boilerplate with a 14-day minimum notice for terms changes. Fill [14] days (30 is friendlier).
Section 15 (common)

16. Contact Information

🔴 load-bearing Six channels by default. Better to list fewer real ones than six unmonitored — every channel here is checked during dispute handling. If you can only commit to one reliably, use it for every row.
Section 16 (common)
After publishing, store the T&C URL, version number, and effective date together. When you change terms, notify existing users at least 14 days in advance — and keep a version log so you can prove what was active at any past point in time.