Stigg can be integrated with Stripe Tax to automatically calculate customer tax rates during checkout sessions, provisioning and updating of subscriptions.

We've extended the Stripe integration configuration to allow customers to manage automatic tax calculation using Stripe Tax. Before this change, customers needed to reach out to Stigg Support to do so.

Enabling automatic tax calculation using Stripe Tax can be achieved by toggling the relevant setting under the Stripe integration section:

We've improved the user experience for applications that are integrated with Stigg. With this change, only active integrations appear under the Integrations section. In addition, it's possible to filter the active integrations according to the integration type.

Integrating additional applications with Stigg environments is possible by clicking on the "+ Add integration" button. Available integrations can also be filtered according to the integration type.

When Stigg is integrated with Stripe it's now possible to determine the number of attempts that were made to collect payment for a generated invoice. 

When subscriptions to paid plans are created in Stigg, the number of payment collection attempts is is immediately 1. This number can increase when payment fails and Stripe is configured to automatically retry failed payments.

Vendors can leverage this field to customer-facing notifications, for example using an in-app banner.

This information is accessible via the response of the getActiveSubscriptions and getSubscription endpoints as well as the subscription.updated webhook event under the latestInvoice.attemptCount property.

The new property is available via the Stigg API as well as in the Stigg SDK for Node.js v3.62.0, Stigg Python, Ruby, Go, Java and C# v2.307.0, Stigg JavaScript SDK v3.36.0, Stigg React SDK v5.30.0, Stigg Vue.js SDK v4.15.0 and Stigg Embed SDK v5.15 or later.

We've made it easier and more intuitive to end trial subscriptions. Previously, triggering the trial end flow was only possible by updating the trial subscription to 0 remaining trial days.

We've now added a dedicated action in the subscription context menu for triggering this flow. The new action is available in the Customer details > Subscriptions section as well as in the Subscription Details screen.

When attempting to end a trial users can select whether the trial should end now or schedule it for a later date.

⚠️ It can take up to a few minutes for the trial end flow to be initiated.

We've extended the subscription scheduled changes behavior to include scheduling of changes to subscription metadata - when subscription changes are scheduled to the end of the billing period or billing month, changes to the subscription's metadata will now also be applied then.

Scheduling of subscription changes can be done programmatically by passing the scheduleStrategy parameter when provisioning new subscriptions or updating existing ones.

Customer payment methods can now be removed using the Stigg app, in addition to programmatically using the Stigg API and SDKs. To remove a payment method in the Stigg app, navigate to the Customer Details screen of the relevant customer and hover on their payment method. Click on the "Trash" icon and confirm the action.

We've also added the ability to remove payment methods from customers that have an active subscription to a paid plan. The new capability is helpful when offering free plans that can be extended with optional add-ons, which is becoming more popular with AI add-ons, similarly to Notion's pricing. To do so, model the plan as a paid $0.00 plan, and when customers no longer subscribe to the add-on you can optionally detach their payment method as well.

⚠️ Payment methods are stored directly in billing solutions that are integrated with Stigg (and never in Stigg itself), and therefore require such an integration to be active.

We've extended offline support to the Stigg frontend SDKs.

Offline support is useful during local development and testing, when you'd like to avoid making network requests to the Stigg API. 

You can run the SDK in offline mode by enabling the offline option. When enabled:

1. API key validation will always succeed, regardless of the key provided.

2. Entitlement evaluations are limited to the values defined in the global fallback strategy.

We've made it easier to integrate applications with Stigg using the React SDK by introducing custom hooks and entitlement guard components:

1. Hooks that give you access to the Stigg object, entitlement checks, and helper methods for fetching data.

2. Entitlement guard components are useful in the cases where you need to wrap some part of the UI with an entitlement check and show a component in case the customer has no access to the feature.

The new capabilities are available in the Stigg React SDK v5.28.0 or later.

Stigg's native integration with Auth0 connects Auth0's identity management with Stigg's entitlement enforcement capabilities. Instead of manually building custom integration logic, developers can leverage the integration to seamlessly authenticate users and enforce feature access based on entitlements.

The integration ensures that when users authenticate, they're granted access to the correct set of features in Stigg, enabling the application to function according to their plan limits.

The integration addresses several use cases that streamline app development and improve end-user experience, including:

1. Automatic provisioning - with Auth0 and Stigg you can easily provision subscriptions for both B2B customers and B2C users when they are onboarded by configuring product-level customer journeys, like assigning new customers with a default free plan, or starting a trial for a paid plan are possible in no-code.

2. Automatic active users metering - for B2B companies, tracking active users helps measure product adoption and growth. This integration automatically tracks active users during the login process, making it easy to implement usage-based billing models like pricing per Monthly Active Users (MAU). This is especially helpful for self-service plans, where customers typically pay based on their actual usage instead of a fixed number of licensed seats.

3. Enforcing user limits - tracking active users can also help enforce seat limits. The system can ensure that the number of active users stays within the limits of their agreement, which is ideal for fixed-seat contracts. This helps both vendors and customers stay aligned with the terms of their plans.

4. Gate identity related features - while not part of the integration, using Auth0 and Stigg allows entitlement enforcement for typical paid features like Single Sign-On (SSO) or System for Cross-domain Identity Management (SCIM). You can leverage Stigg to check if users have access to configure a feature, and then leverage Auth0 to set it up. This makes it easy to offer tiered features that scale with customer needs, and create upsell opportunities for larger customers.

You can more details about the integration here.

During local development or testing, you might want to avoid making network requests to the Stigg API.

To do this, you can run the the Stigg SDK in offline mode by enabling the "offline" option. When enabled:

1. API key validation will always succeed

2. Entitlement evaluations will return the values that are defined in the global fallback configuration

Offline mode is supported by the Stigg Node.js SDK v3.56.1 and Stigg Sidecar SDK v2.236.1 or later.