We've extended our integration with Stripe to include automatic propagation of usage data of subscriptions to plans that have a usage-based pricing model from Stigg to Stripe.

This allows Stigg's customer to bill their customers based on usage data that's reported to Stigg.

Usage-data between Stigg and Stripe is synced on an hourly basis.

When plans have multiple billing periods (monthly and annually) there's now an indication below the price to the billing period that it refers to.

When all plans have only one billing period, the billing period switcher is hidden.

We've extended our integration with Stripe checkout form, and it's now possible to pay for plans that have per-unit pricing, as well as subscriptions that include both plans and add-ons using the Stripe checkout form.

We're excited to share that we've added the ability to store custom metadata on Stigg entities.

The metadata can then be leveraged by the hosting application and third-party solutions via the Stigg SDKs, API and webhooks to implement custom functionality, for example: highlight a selected plan in the paywall (as can be seen in the below video), or defining different time period for in-app notifications for each subscription.

Metadata can currently be provided for customers, subscriptions, products, plan and add-ons, either via the Stigg Console UI, or programmatically using the Stigg SDKs and APIs.

We're excited to share the Stigg is now compliant with the SOC2 Type II and ISO27001 standards:

• SOC2 is the most sought after security framework for growing SaaS companies. SOC2 certification demonstrates your organization’s ability to effectively safeguard the privacy and security of customer and client data.
• ISO 27001 is an international standard on how to manage information security.

These certifications serve as an example to Stigg's maturity and practice of security-by-design, while we ensure that customer data is secure.

We're excited to share that Stigg now offers a React SDK, which includes a paywall widget ! 🎉

Adding a Stigg-rendered paywall to applications now only requires a few lines of code.

The widget supports 3 modes:

1. Showing plans without any customer context - this mode is useful when leveraging Stigg to render the public pricing page.
2. Showing only the plans that the customer can upgrade to - this mode is useful when a customer attempt to access a gated feature.
3. Showing the current customer plan, plans that the customer can downgrade to and plans that the customer can upgrade to - this mode is useful in the context of a customer portal, where customers manage their subscriptions.

The widget is fully customizable, including: colors, fonts, alignment, texts, selection of which plan will be highlighted, as well as what happens when a customer clicks on the relevant call-to-action (CTA) buttons.

Future and canceled subscriptions now have an indication if they relate to a trial subscription.

The indication is available in the Customer details > Subscription section as well as in the Subscription detail screen.

Following customer confusion from trial cancelation "at the end of the billing period", and since we don't currently support automatic subscription activation at the end of the trial, we've limited the cancelation options for trials; therefore, trials can now only be canceled immediately.

Note that it's still possible to shorten and extend trial the "Edit trial" action.

When Stigg is integrated with Stripe, and a subscription for a paid subscription is created, the subscription is first created in the "Pending payment" state.

Once Stripe completes the billing of the subscription, the subscription becomes active and the customer has access to the subscription's entitlements.

We now automatically updated the customer details and subscription details UI when this transition takes place; thus, providing a more responsive experience to the Stigg admins.

Plans and add-ons that are now propagated from Stigg to Stripe using the following format:

1. <PRODUCT_NAME> <PLAN_NAME> Plan - for example: Revvenu Basic Plan
2. <PRODUCT_NAME> <ADDON_NAME> Add-on - for example: Revvenu 10 Seat Add-on