The Stigg Console now includes visibility for all of the widgets that Stigg provides out-of-the-box and that can be integrated into your application in order to provide a buying experience that your customers will love 🤩.

Clicking on each tile will open more details about each widget, as well as instructions on how to integrate it into your application.

The new widget library is accessible from the Integrations > Widgets section of the left navigation pane.

We've extended our integration with Stripe and now support entering of promo codes during customer checkout. Promo codes can be extremely useful to promote your products upon launch and during the holiday season.

When a promo code is entered during checkout, it's validated by Stripe. If the code is valid, the discount is applied to the subscription and the discounted price will appear in the Stigg Console and customer portal widget, as well as returned by Stigg's APIs and SDKs.

When the discount is defined to apply during a certain time period (for example: 12 months), after the discount period is exceeded the original non-discounted subscription price will be presented.

Allowing customers to enter them during the checkout process is as easy as 1-2-3:

1. Create a coupon either from the Stigg console directly in Stripe.
2. Open the created coupon in Stripe and generate a promo code, for example: PRODUCTHUNT, BLACKFRIDAY22 or XMAS2022.
3. Allow entering promo codes when provisioning subscriptions using the Stigg SDK.

The order of plan entitlements can now be defined using drag-and-drop gesture. When the changes are published, the change is auto-magically 🪄 reflected in plan pickers that are rendered using Stigg's SDK and APIs, and specifically Stigg's plan picker widget.

We've added an ability to set minimum and maximum quantity restrictions when using per-unit pricing.

When such restriction are set, they're automatically reflected in Stigg's plan picker widget. When Stigg is integrated with a billing solution (such as Stripe), the quantity restrictions are also auto-magically applied to the checkout page.

The quantity restrictions only apply to subscriptions that are created in a self-served manner, and are not enforced on subscriptions that are manually created in the Stigg Console.

We've extended the supported integration methods for gating access to features according to the defined pricing model in Stigg, and now support gating access using AWS API Gateway.

The new integration method allows customers to get up and running with Stigg even faster than ever.

To integrate Stigg into your application using AWS API Gateway, follow this tutorial and example project.

We're excited to share that Stigg now offers a snap-in customer portal!

With only a few lines of code you can embed Stigg's customer portal into your application, introduce self-service and drive in-app expansions.

Stigg's customer portal:

1. Provides customers with visibility to their current subscription details - subscribed plan, purchased add-ons, and granted promotional entitlements.
2. Provides customers with visibility to the usage of their subscription's features.
3. Allows customers to upgrade and downgrade their subscription in a self-served manner - when you update your pricing model in Stigg, customers will auto-magically be able to upgrade or downgrade their subscription according to the updated pricing model 😎.
4. Allows customers to view their billing and payment information - when Stigg is integrated with a billing solution (such as Stripe), customers can also update this information and view previous invoices directly from the billing solution's billing portal.

The widget's layout, style and texts are fully customizable to suit your branding needs.

More details about the widget can be found here.

When customers subscribe to plans (for example: during an upgrade from a free plan to a paid plan), a subscription needs to be provisioned in Stigg.

We've added a new provisionSubscription API that exhibits the below behavior:

1. When provisioning of a paid subscription is attempted, Stigg is integrated with a billing solution and payment details have not been previously provided by the customer, the customer will be auto-magically redirected to the billing solution's checkout page. After the customer enters the required payment details in the presented checkout page, the relevant subscription will be created in both Stigg and the billing solution.
2. When no payment is required or when Stigg is not integrated with a billing solution, the subscription will be immediately created in Stigg.

The new API method significantly simplifies the integration with Stigg, allows Stigg's customers to focus on modeling and rolling out changes to their pricing using the Stigg platform, and delegates all of the heavy lifting and decision making about when payment details are required to Stigg.

As can be seen in this example (and below video), this results in needing to write and maintain 4X less lines of code.

The new provisionSubscription method is available in the Stigg Node.js SDK version 0.57.0 or later, and replaces the separate createSubscription and initiateCheckout methods, which have been marked for deprecation.

More details about the provisionSubscription API can be found here.

We're excited to share that it's now possible to update subscriptions using Stigg Console UI. Use the new "subscription builder" interface to:

1. Update the unit quantity for subscriptions to plans with per-unit pricing
2. Add, remove and update add-ons and their quantity

Whenever an update to a subscription affects its price, Stigg provides visibility for the following details:

1. Immediate amount that a customer will be billed or credit for.
2. The relative change to the current subscription price.
3. The total subscription price after the change.

When integrated with a billing solution (i.e. Stripe), Stigg leverages that billing solution for this calculation.

The updated user interface also allows users to set and update the trial length either to a specific date or to the number of (remaining) trial days.

The new UI is used both during subscription creation and update.

We've made it easier for customers with a Ruby backend to get up and running with Stigg by leveraging the Stigg Ruby SDK.

The initial version of the Ruby SDK serves as a wrapper around the GraphQL API and does not currently support local caching, polling or streaming of customer entitlements - such support is planned at a later stage.

More details about leveraging the Stigg Ruby SDK in order to integrate Stigg into your Ruby application can be found here.

We've improved the user experience of all of the forms in our system - labels now consistently appear on top of the input fields, which results in improved orientation in forms.