We've added an ability to programmatically manage customers' promotional entitlements. 

By leveraging the new APIs you can grant customers access to features even if they're not part of the subscription automatically based on custom functionality. Access can be granted for a limited time, or the entire customer lifetime.

It's also possible to programmatically revoke promotional entitlements. Revoking takes place immediately.

The new functionality is supported in the Stigg Node.js SDK v2.26.0, Stigg Python SDK v0.550.2 and the Stigg Ruby SDK v0.550.2.

We're excited to announce the ability to report high-volume usage events to Stigg and leverage the Stigg platform to do the heavy lifting of aggregating reported events to calculate and meter customer usage.

With this new functionality, Stigg can now meter feature usage from 2 data sources:

1. Calculated usage that has been pre-aggregated by your application. This source is useful for features such as seats.
2. Raw events that have been reported by your application, which Stigg can filter and aggregate to calculate customer usage. This source is useful for features such as monthly active users (MAUs).

When usage events are reported to Stigg, they're processed in real-time and allow you to provide customers with visibility for their current usage, enforce access according to pre-defined limits, bill customers and trigger notifications.

Reporting raw events to Stigg is supported by the Stigg Node.js SDK v2.3.0, Stigg Python SDK v0.465, Stigg Ruby SDK v0.465, Stigg Go SDK v0.1.6 and the Stigg GraphQL API.

Aggregation of reported events can be defined as part of the definition of metered features.

More details about Stigg high-volume metering capabilities can be found here.

We've extended the supported pricing models for usage-based charges that customers to commit to in advance. 

Each usage-based charge can be defined with one of the following pricing models:

1. Standard pricing - where customers will be charged the same price for each unit

2. Stair-step pricing - where customers will be able to commit to bulks of units in tiers, and the unit price in each tier represents a discount over the previous tier

When stair-step pricing is selected, customers can select their desired tier directly from the Stigg pricing table widget. When integrated with a billing solution such as Stripe, the selected tier would be automatically reflected in the Stripe-hosted checkout page.

As well with all of the supported pricing models on the Stigg platform, you can easily switch between the different pricing models with no-code - Stigg auto-magically 🪄 reflects the changes in your application 💪🤩.

Stair-step pricing is supported by the Stigg Node.js SDK v2.25.0, Stigg JavaScript SDK v2.18.1, Stigg React SDK v4.2.2, Stigg Vue.js SDK v3.4.0 and the Stigg Embed SDK v4.4.0 or later.

When your client-side (frontend) application is integrated with Stigg it uses the Client API key, which is publicly accessible to anyone.

While the Stigg platform limits access for that API key to a minimum, some sensitive data may still be accessible by a malicious actor (e.g. by guessing customer ID).

It's highly recommended to prevent any un-authenticated access to data using Client API key, by configuring Stigg to verify the identity of requests that originate from your client-side application.

We've now made it possible to enable client-side hardening in each environment via a self-serve manner. More details about client-side hardening and how to enable it can be found here.

We've made significant improvements to how subscription payment errors are reflected in the Stigg platform. In addition to ensuring that customers will only have access to entitlements that they successfully pay for, Stigg now:

1. Provides visibility for payment errors - when payment for a subscription fails, the subscription will appear with a "Payment error" status, as well as with a description of the error that was encountered. You can also filter the customer list according to the "Payment error" status to easily identify customers with payment errors.

2. Provides a payment link (when applicable) that you can copy and send to the relevant customer, or open directly from the Stigg app to complete the payment for the subscription. The payment link is also returned by the Stigg SDKs when provisioning or updating subscriptions fails.

The new changes are supported by the Stigg Node.js SDK v2.24, Stigg Python SDK v0.541, Stigg Ruby SDK v0.541, Stigg JavaScript SDK v2.16, Stigg React SDK v4.2.0, Stigg Vue.js SDK v3.3.0 and Stigg Embed SDK v4.3.0 or later.

More details about how payment errors are handled in the Stigg platform can be found here.

We've updated the design of the Stigg pricing table widget with a fresh new look that incorporates recent best practices, including:

1. The plan description now appears immediately below the plan name

1. The price amount now appears in a dedicated line

2. The call-to-action (CTA) buttons have been moved up to appear below the plan price instead of after the entitlement list

The Stigg pricing table widget can be embedded in public pricing pages, as well as in-app. When embedded in-app, customers have visibility for the current plan that they're subscribed to. In addition, the pricing tables are also included in the Stigg customer portal widget. More details about Stigg's snap-in widgets can be found here.

The updated design is available in the Stigg React SDK v4.1.2, Stigg Vue SDK v3.2.0, and the Stigg Embed SDK v4.2.0 and later. If you leverage custom CSS to customize the widget's style, minor adaptations may be required to align them with the new design.

We've made the indication in the product details screen for entitlements with custom display text more subtle.

Entitlements with custom display text will now have a dedicated icon that represents this state. Hovering on the icon will provide visibility for the default text.

The improved indication makes it easier to understand how the entitlement will be communicated to customers.

We've significantly reduced the latency of entitlement checks that are performed using the Stigg Python SDK.

We've made it easier to leverage third-party tax compliance solutions such as Avalara to calculate tax rates and stay compliant with tax regulations.

To so do, simply provide the customer's billing address to the third-party tax compliance solution to calculate their tax rate. Then, include the response in the billingInformation of the provisionSubscription and estimateSubscription methods of the Stigg SDK.

When Stigg is integrated with a billing solution, Stigg will auto-magically create the relevant tax objects in the billing solution if they don't already exist and apply them to customers' invoices.

The new APIs are supported by the Stigg Node.js SDK v2.13.0, Stigg Python SDK v0.511.0, Stigg Ruby SDK v0.511.0, Stigg JavaScript SDK v2.13.0 or later.

When changes to the plans add-ons are rollout out only to new subscriptions (for example: when changing their price), grandfathering takes place.

To prevent a SKU sprawl, Stigg allows you to manually migrate each subscription to the latest plan and add-on version.

It's now possible to schedule subscription migrations to take place at the end of customers' billing period directly from the Stigg app, in addition to being able to trigger them immediately.