1. Payment processor
Wise-Revise uses Stripe for subscription checkout, payment method handling, recurring billing, invoicing, and billing portal functionality.
2. Checkout and card handling
- Payment details are entered on Stripe-hosted pages.
- Wise-Revise does not store full card numbers or card security codes.
- Account provisioning is linked to successful Stripe checkout lifecycle events.
3. Recurring billing models
- Fixed monthly plans bill according to Stripe subscription schedule.
- Teacher AI metered plans bill by reported usage events at the configured per-quiz rate.
- Subscription status is synchronised to Wise-Revise access controls.
4. Metered usage reporting
- AI usage attributable to a teacher billing owner is reported to Stripe as usage/meter events.
- Usage records are tied to Stripe customer/subscription identifiers for invoice generation.
- Local spend tracking is used for budgeting and in-product guardrails; Stripe remains billing source-of-truth.
5. Plan changes and proration
- Users can preview prorated impact before changing plan.
- Proration may create an immediate charge or future invoice credit depending on direction of change.
- Billing cycle dates remain unchanged unless configured otherwise.
6. Billing portal
- Eligible Stripe-linked accounts can open the billing portal from account settings.
- Portal actions can include payment method updates, invoice history, and cancellation controls.
7. Webhook integrity and reconciliation
- Stripe webhook signatures are validated before processing.
- Subscription updates from webhooks are reconciled to local entitlement state.
- Failed verification or processing errors are logged and handled safely.
8. Failed payment and disputes
Failed or disputed charges are managed using Stripe subscription/invoice states and may restrict paid feature access until resolved.
9. Security and compliance
Stripe configuration secrets must be stored securely outside public web root. Stripe processing should be reviewed against your organisation’s finance, tax, and procurement requirements before production rollout.