5 min read
› Documentation › Stripe › Stripe Products Overview

Stripe Products Overview

Getting Started

If you're looking for a straightforward, step-by-step guide to setting up a new product catalog, check out our how-to guide:

That guide walks you through:

  1. Defining product types (subscription, consumable, non-consumable)
  2. Adding metadata for your own application logic
  3. Configuring one-time or recurring prices
  4. Managing product visibility with the "can_purchase" metadata and Stripe's "active" status
  5. Testing your catalog before going live

In-Depth Reference

For a deeper look into supported product types, advanced metadata usage, and best practices, see our reference documentation:

That reference details:

  1. How iaptic recognizes different product types
  2. Metadata schemas for advanced features like usage limits, feature flags, tiers, and more
  3. Ensuring correct pricing modes (recurring vs. one-time)
  4. Visibility controls at the price level
  5. Maintaining consistency across your product catalog

Explanation and Best Practices

Below is an overview of the core concepts and advice when working with Stripe products for iaptic:

  1. One Product = One Pricing Model
    iaptic does not support mixing recurring and one-time prices within the same product. Decide if each product is either a subscription or a consumable/non-consumable before configuring your Stripe catalog.

  2. Metadata Matters
    iaptic relies heavily on product metadata—such as product_type, can_purchase, and optional fields like features, tier, etc. This makes your app's logic simpler and more flexible. Keep these keys consistent across all products.

  3. Focus on Testing
    Stripe's test mode and test cards are extremely helpful for verifying your setup before going live. Make sure to run test transactions for each product type (subscription, consumable, non-consumable) and see if everything works correctly in your iaptic dashboard.

  4. Plan for Growth
    If you add new product tiers or more complex pricing (e.g., multiple currency support, trial periods, usage-based billing), ensure your metadata strategy is well-defined. That way, your front-end, back-end, and iaptic logic can adapt seamlessly.

  5. Webhooks
    Stripe webhooks (via the iaptic validator) are essential for subscription lifecycle events. If you haven't set this up yet, see How to Configure Stripe Webhooks to handle renewals, cancellations, and more. This ensures your app and iaptic remain in sync.

Additional Resources

Whether you're setting up a single subscription plan or a full marketplace of products, these guides will help you take advantage of iaptic's seamless integration with Stripe.