Pricing & Billing Terms
Paid plans once launched: prices, currencies, tax/VAT/GST/sales-tax display, billing intervals, renewals, failed payments, invoices, credit notes, business/customer type. No checkout exists today.
Draft for legal review
This document is an implementation draft written to match how the product actually behaves. It has not been reviewed by a qualified lawyer and must not be relied on as legal advice. Items marked or are unresolved.
1. Prices, currencies and what the total includes
Supported display currencies: USD, EUR, GBP, CAD, AUD, JPY, SGD, INR, BRL, plus others as required by the payment/tax provider. The checkout shows the currency of your region before you pay, the unit price, interval, any setup fee, and whether tax/VAT/GST/sales tax is included or added — plus the exact total you will be charged. Drip pricing (adding fees at the last step) and hidden pricing are prohibited by the dark-pattern rulebook.
Tax treatment example: '₹999/month + 18% GST = ₹1,178.82 charged monthly until cancelled' (illustrative; actual provider-calculated). Where reverse-charge or business-customer rules apply, the checkout collects the tax identifier and explains the treatment.
2. Subscriptions, renewals and the payment button
Recurring plans renew automatically for the same period at the disclosed price unless cancelled before the renewal date. Before you pay we disclose product/service, total price, currency, tax treatment, interval, renewal behaviour/price, trial duration/conversion, cancellation method, refund rules, delivery/access conditions, support contact and legal links. The final button clearly states the paid obligation (e.g. 'Pay ₹1,178.82/month, renews automatically until cancelled').
Subscription consent evidence (price, interval, trial, renewal accepted + terms version + timestamp + source) is stored. Pre-checked renewal acceptance is never used.
3. Payment processing, security and what we never store
Processor: [PLACEHOLDER — none integrated — OWNER INPUT REQUIRED]. Hosted/tokenised flow only (e.g. Stripe/Paddle/Razorpay or equivalent qualified provider). We do not store raw card numbers and never store CVV. Webhooks are signature-verified; payment metadata (charge ID, amount, currency, status) is retained per retention-matrix.md; secrets never in logs. PCI scope is delegated to the processor; we do not claim PCI certification we do not hold.
4. Failed payments, grace, retry and invoices
[PLACEHOLDER — define retry schedule (e.g. Day 1/3/5), grace (e.g. 7 days full access), downgrade (Free, data retained), termination notice, reactivation. Must be set before paid launch.] Invoices: provider-issued with billing address, currency, tax amount, tax-inclusive/exclusive display, refund/credit-note linkage, business/customer type. Records retained for tax/audit per law.
5. Taxes: we delegate to a qualified engine
Global tax logic is not built in-house. A qualified tax engine/provider (e.g. the payment provider's tax module) determines registration, nexus, rates, exemptions and filing. [PLACEHOLDER — provider + registrations.] Do not invent tax calculations.
6. Version
Version 0.9.0-draft, last updated 2026-10-02, next review 2026-12-01, LEGAL REVIEW REQUIRED. No checkout exists; this is forward-looking.
Sources
This document is derived from the following entries in our legal source registry: EU-CRD, US-FTC-ACT, EU-UCPD. See for the full citations and the date each source was last verified.