Billing and commercial model
Billing and commercial model
Billing is backend-owned. The UI presents plans and checkout states, but subscription provisioning, invoice delivery, provider customer records, and entitlement checks are persisted and reconciled by the API.
1. Plans and trials
- Platform plans cover the main Crownvo product.
- Agency plans carry client-workspace, team, white-label, and usage limits.
- Mailbox plans use GBP pricing with VAT-aware display and free mailbox quotas per verified domain.
- Free trials provision access without pretending that a payment provider has charged the customer.
2. Invoices
Platform invoices use the configured Crownvo issuer and delivery rules. The invoice issuer, recipient resolution, BCC policy, and send audit are part of the backend service boundary.
- Invoice sends are real mail deliveries, not audit-only placeholders.
- Delivery targets are resolved from workspace business contacts and CrownvMail fallback identities.
- The sender and BCC policy are configurable through deployment environment values.
3. Payment providers
- Stripe and PayPal are integration boundaries, not sources of truth for local entitlements.
- Provider customer and subscription IDs are stored using explicit DTO contracts.
- A provider outage should not silently erase local billing state; reconciliation is idempotent and auditable.
Still need help? Contact support.