Billing and plans
Plan groups, credits, and add-ons as the product enforces them.
Billing is owner-only. Administrators cannot change plans or payment methods.
Plans have a group (free, starter, pro) plus credit limits (events, registrations, check-ins, users). A metric can be a number or unlimited.
What the code gates on
| Capability | Rule |
|---|---|
| Registration forms | Starter or Pro (starter_or_higher?) |
| Email campaigns | Starter or Pro |
| Badge templates | Starter or Pro (onsite_plus_or_higher?) |
| Kiosks | Pro only (onsite_pro?) |
| Event website | Always on |
| Event App | Add-on |
| Lead retrieval | Add-on |
| Expo sponsors | Add-on |
| Expo passport | Add-on |
| Party check-in | Add-on |
Locked features render a feature-gate page instead of the real screen.
Credits vs add-ons
Quantity add-ons (extra credits / seats) can be bought again. Single-enable add-ons (Event App, passport, lead retrieval) show as already purchased once they are on the event.
Marketing prices on micepad.co/pricing describe packages. Studio enforces the table above.
Stripe
Checkout and invoices go through Stripe. Connect (for ticket payouts) is also owner-only. After Stripe onboarding, Studio syncs the account so it can accept charges.