The first step is to create your products and plans in Stripe. The Servicebot standard design for Stripe Products & Plans makes your billing system scalable and makes it easy to change your pricing model in the future without going into code. It involves creating Stripe Products and Plans in certain ways according to the architecture below, and adding Metadata to those Products to define which products are part of which service offering and tier. This allows you to handle essentially any pricing model and easily make changes to them.
This process is as simple as logging into your Stripe account and adding your available products and pricing plans. Servicebot uses metadata attached to your Stripe products to render the pricing plans to your customers.
Metadata in Stripe is used to group together Products & Plans into Services & Tiers. Metadata tags are used on the Product object.
The name of the service or offering. Allows us to group together many Products and Plans into a single service offering which enables the Subscription Management Portal to display options for customer to upgrade or downgrade to.
Slack, Servicebot, SaaS USD
The name of a tier within a service. Allows us to group together many Products and plans into a single tier to do complicated billing models with multiple metrics or units. Whenever a tier is selected by a customer, they are subscribed to all the plans in the tier
Free, Premium, Pro
Each product you add to your Stripe account must have the 'sb_service' metadata tag. So if you have 3 pricing tiers, and each tier has a flat pricing, you must create one product for each tier (3 in this case) and add metadata to each of the 3 products with the service name and tier name.
If each tier has multiple pricing units, such as flat pricing plus some usage-based pricing, then you would also create one product for each of the flat pricing and 3 for each usage-based pricing units, and tag them with the appropriate metadata. So for a model with 3 tiers, and each tier having a flat subscription and usage based pricing, there would be six products created (2 per tier). Each product would need to have the sb_service and sb_tier metadata added to it.
Plans are created for each interval available (daily, monthly, yearly...) within each product.