When billing customers using invoices or payment links, it's now possible to customize the number of days before invoices are due.

Doing so allows you to customize customer billing according to the business terms that were agreed on.

By default, generated invoices are due within 30 days. 

We're excited to announce our native integration with Zuora!

Zuora is a billing solution loved by finance teams for its flexibility, yet it can be very complex for engineering teams to maintain.

Stigg abstracts Zuora away from your code, making changes to pricing and packaging effortless - after the integration is set up, changes to the Stigg product catalog (product, plans, add-ons), customers and subscriptions are automatically synced to Zuora.

Using this integration you can leverage Stigg for managing your pricing and packaging in no-code and Zuora for billing.

Stigg's native integration with Zuora is currently available in beta for customers of the Growth and Scale plans. 

More details about the integration can be found here.

We've added an ability to align the billing anchor of all paid subscriptions to the same anchor.

When selected and when customers have multiple active subscriptions either to the same product or to different products, the billing anchor of all of the paid subscriptions will be aligned to billing anchor as the first paid subscription. 

This allows invoices of multiple subscriptions to be generated on the same day. 

The configuration can be changed using no-code under the Account Settings section, and will affect all of the account's environments. Updating the configuration will affect all newly created subscriptions.

More details can be found here.

We've made it easier to get up and running with Stigg when using the Python SDK by providing visibility for all of the available SDK methods via an SDK reference.

The SDK reference is automatically updated whenever a new SDK version is published.

We've made it easier to get up and running with Stigg when using the Go SDK by providing visibility for all of the available SDK methods via an SDK reference.

The SDK reference is automatically updated whenever a new SDK version is published.

We've added an ability to schedule the cancelation of trial subscriptions. 

With this new change, trial subscriptions can be can be scheduled for cancelation at the end of the trial period or on a specific date. If the specific date is longer than the trial period, the trial will automatically be extended to accommodate for that.

When a trial is extended, its scheduled cancelation is removed. To cancel it, simply schedule its cancelation again.

When integrating Stigg via webhooks, canceled trials will be reflected via subscription.canceled events and expired trials via subscription.trial_expired events.

Scheduling cancelation of trial subscriptions is supported via the Stigg app, the Stigg API and Stigg SDKs.

We've added a new API for listing customers' active subscriptions. The new API is accessible from Edge and has a significantly higher rate limit.

Listing customers' active subscriptions can now be achieved by the getActiveSubscriptionsList method. Getting the full data of each subscription can then be done using the getSubscription method.

The new API is available in the Stigg Node.js SDK v3.37.0, Stigg Python SDK v1.236.0, Stigg Go SDK v1.236.0, Stigg Java SDK v1.236.0, Stigg Ruby SDK v1.236.0, Stigg .NET SDK v.1236.0, Stigg Sidecar SDK v2.0.0, Stigg JavaScript SDK v3.20.0, Stigg React SDK v5.16.0, Stigg Vue.js SDK v4.5.0 and Stigg Embed SDK v5.6.0 or later.

We've extended the Subscription Details screen in the Stigg app to provide visibility for the next estimated bill. 

When clicking on the estimated bill amount, users can view a breakdown of all of the upcoming charges.

Viewing the next estimated bill is especially helpful for products that are monetized via pay-as-you-go and hybrid pricing models.

A common pricing model in SaaS is to offer team plans with separate usage enforcement for each team member. For example, as part of a team plan every team member gets access 100 AI actions per month.

We've made now it easier than ever to implement this pricing model by leveraging Stigg to automatically cancel the team members' subscription when the team subscription is canceled.

More details about this pricing model and how model it in Stigg can be found here.

Every event on the Stigg platform is audited, and visibility for these events is available via the Activity Log. 

Using the Activity Log users can answer the following questions:

1. What happened?

2. When did it happen?

3. Who (or what) triggered the event?

Thus, the Activity Log serves as an audit log for actions on the Stigg platform and can also be useful for troubleshooting.

The Stigg app includes both a general activity log with all of the events of a specific environment, as well as an entity-specific log with a pre-filtered list of events for that entity. Event are also accessible via API.

The Activity Log is available in beta for customers on the Stigg Growth plan or higher, and currently includes events from May 22nd, 2024 or later.

More details about the Activity Log can be found here.