We've added an ability to view the prorated amount due today when creating new subscriptions in the Stigg app. 

The experience is similar to the one that was previously available when updating a subscription a subscription to a specific plan -changing billing period, unit quantity and add-ons.

Using the new interface, Stigg app users can determine the prorated amount due today also when creating subscription to a new plan.

We've added an ability to refresh the "Entitlement Usage" and "Entitlement Summary" section. This new capability is helpful during the integration with Stigg, when programmatically reporting usage to Stigg, updating subscriptions, and updating customer's promotional entitlements.

With the new refresh button that appears in this section, you view the most-up-to-date data without needing to refresh the entire Stigg app.

Stigg also provides visibility when the presented data was last refreshed.

We've added the ability to update customer's current usage directly from the Stigg app. This is helpful when setting up the initial integration with Stigg (before usage is programmatically reported to Stigg), and addressing customer support requests, for example: when there's a need to reset customer's current usage.

To update usage, navigate to the "Entitlement usage" section of the relevant subscription under the "Customer details" or "Subscription details" screens.

Uncollapse the relevant feature to expose its historical usage graph, and click on the "Add usage record" button.

In the opened navigation pane, enter the following:

1. Update behavior - "delta" to increment or decrement units relative to the current value, or "set" to override the current value.

2. The usage value

You can leverage the preview section to see the affect on customer's current usage.

More details can be found here.

We've made it easier than ever to find entities in your Stigg environments using a new universal search capability, that's accessible from the top-right corner of the Stigg app and also via a dedicated shortcut (⌘+K on Mac or CTRL+K on Windows).

Entered search criteria will be matched according to entities in the product catalog (products, plans, add-ons, features and coupons), customers and subscription of the currently selected environment. 

To navigate to a relevant entity, simply click on the returned result.

More details about the new universal search capability can be found here.

We've added an ability to manage your subscription in a self-served manner directly from the Stigg app. To do so, navigate to the Account Settings > Billing section, where you could:

1. View your current subscription details

2. View your current feature usage and their limit

3. Upgrade, downgrade and manage the add-ons of your subscription

4. View and update your payment details 

5. View past invoices

Under the hood we use our very own widgets, which you too can integrate into your application using a few lines of code 💪.

More details can be found here.

We've added an ability to better differentiate between non-production and production environments. 

Non-production environments are isolated sandboxes that can be used for testing and iterating on pricing and packaging without affecting your real customers. Non-production environment can only be integrated to test Stripe accounts, and their usage is excluded from your Stigg subscription.

Production environments are live environments where your real customers interact with the final, stable version of your product. Only production environments can be integrated to live Stripe accounts and their usage is enforced according to your Stigg subscription.

The environment type can be defined during the environment creation. After the environment is created it can no longer be modified.

More details about the differences between each environment type can be found here.

We've added support for in-advanced commitment using the tiered usage-based pricing, where customers pay per unit, and the unit price is based on the tier range it falls into.

In the below example, when a customer purchases 20 units, the total price per month will be (5 units x $20) + (5 units x $15) + (10 units x 10$) = $275.

As we any other pricing model, the tiered pricing model is automatically reflected in the Stigg snap-in widgets 🙌.

The new pricing is supported by the Stigg Node.js SDK v3.2.0, Stigg Python SDK v1.11.1, Stigg Go SDK v1.11.1, Stigg Ruby SDK v1.11.1, Stigg Java SDK v1.11.1, Stigg JavaScipt SDK v3.2.0, Stigg React SDK v5.2.0 and the Stigg Vue.js SDK v4.1.0 or later.

More detail can be found here.

We've extended the Stigg JavaScript SDK to allow retrieval all of the product's plans, including ones that have been marked as hidden from the Stigg pricing table widget.

The new functionality allows you to implement custom logic when presenting pricing tables to customers, for example: we offer a “limited time” plan for customers that have an annual subscription.

By default, hidden plans are not returned by the getPaywall method.  To fetch all of the product's plans, pass the includeHiddenPlans: true parameter to the getPaywall method of the Stigg JavaScript SDK.

The new functionality is supported in the Stigg JavaScript SDK v3.1.0 or later.

We've made the Stigg pricing table widget even more customizable by allowing you to override the price and call-to-action (CTA) button texts of plans with custom pricing using a function, instead of static text.

By default, the price of custom plans will appear as "Custom", and the CTA button would appear with a "Contact us" text.

With this change, these texts can be customized and include the plan name, for example: "Select ".

The new functionality is supported by the Stigg React SDK v4.13.2 and Stigg. Vue.js SDK v3.25.0 or later.

For more details, see the price and planCTAButton properties of the PaywallLocalization type.

We've added an ability to programmatically remove customer payment methods when they don't have an active paid subscription. 

The new functionality allows your customers to remove their payment method when they no longer pay for a plan.

To do so, leverage the detachCustomerPaymentMethod function in the Stigg SDK.

The new functionality is supported by the Stigg Node.js SDK v3.3.0, Stigg Python SDK v1.12.0, Stigg Ruby SDK v1.12.0, Stigg Go SDK v1.12.0, Stigg Java SDK v1.12.0 or later, as well as the Stigg GraphQL API.