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.
We've added the ability to customize the coupons that are applied to subscriptions.
When provisioning and updating subscriptions you can select a pre-defined coupon from the Product Catalog and customize it, or create an entirely new custom coupon.
Stigg gives you the full flexibility of customizing coupons, including:
1. Type - fixed fee or percentage
2. Discount amount
3. Duration - forever or limited to a few months
Applying custom coupons to subscriptions can also be done programmatically using the Stigg API, Stigg SDK for Node.js v3.56.0, and Stigg SDK for Python, Ruby, Go, Java and C# from v2.209.0 or later.
When Stigg is integrated with a billing solution such as Stripe or Zuora, Stigg will automatically create the relevant coupon in the billing solution and associate it with the subscription.
Custom coupons are subscription-specific and don't appear in the Coupons screen of the Product Catalog.
This enhancement introduces an additional level of flexibility, which is especially helpful in provisioning of sales-led opportunities. Together with the ability to bill customers using invoices and payment links, provisioning complex enterprise subscriptions has never been easier.
We've added the ability to create coupons with limited discount duration. With this change you can create coupons such as "20% off for 3 months" and "$15 off for 1 month" and apply them to subscriptions.
When Stigg is integrated with a billing solution, coupons from the Stigg product catalog are automatically synced to it 🪄.
If you'd like to allow customers to apply the coupons in a self-served manner you can generate promotion codes for these coupons in the billing solutions that are integrated with Stigg.
This enhancement comes in a timely manner, allowing SaaS vendors to grant additional discounts and promotions during the upcoming holiday season 🕎 🎄🎅.
We've added the ability to delegate the management of subscriptions to other customers. Example use-cases include organizations that pay for subscription on behalf of their employees, and companies that pay for subscriptions that are managed by marketing and design agencies.
When the management of a subscription is delegated from customer A to customer B:
1. Customer A continues to pay for the subscription
2. Customer B will have access to the subscription's entitlements and can upgrade, downgrade or cancel the subscription.
The new functionality also complements the recently introduced payment delegation flow, and allows customers that were only paying for a subscription to regain its ownership.
To delegate the management of a subscription to another customer use the delegateSubscriptionToCustomer() method.
Subscription management delegation is supported by the Stigg SDK for Node.js v3.50.2, Stigg SDK for Python v2.196.0, Stigg SDK for Ruby v2.196.0, Stigg SDK for Go v2.196.0, Stigg SDK for Java v2.196.0, and Stigg SDK for .NET v2.196.0 or later.
We've added support for price localization in fixed fee coupons - upon creation of the coupons it's now possible to specify the discount amount in other currencies in addition to USD. Doing so allows users you to apply the coupon to subscriptions with non-USD currencies.
Fixed fee coupons can be applied to subscriptions only if they offer a discount amount in the currency of the subscription.
Price localization in fixed fee coupons is supported by the Stigg SDK for Node.js v3.51.0, Stigg SDK for Python v2.199.0, Stigg SDK for Ruby v2.199.0, Stigg SDK for Go v2.199.0, Stigg SDK for Java v2.199.0, Stigg SDK for .NET v2.199.0, Stigg SDK for JavaScript v3.31.0 or later.
More details about coupon creation in Stigg be found here.
We've lifted the limitation that prevented users from changing customers' billing currency.
The billing currency is now automatically determined according to the billing currency of customers' active subscriptions.
Customers can be billed in a different billing currency when they don't have any active subscription to paid plans.
We've added the ability to control the behavior of resettable metered features when customers update their subscription using no-code.
The new configuration supports the following options:
1. Always reset usage upon plan transition (default)
2. Never reset usage upon plan transition
3. Reset only if the subscription's billing anchor changes - this configuration is useful when you'd like to reset feature usage upon transition between free, paid and custom plans, and when switching billing periods (monthly <-> annually), while persisting the usage in all other cases.
The new configuration can be controlled separately for each product under the product's customer journey configuration.
Changes to the configuration would only affect future subscription updates, and does not apply retroactively.
Customers that report raw usage events to Stigg and leverage Stigg for aggregation and calculation of customer's usage of metered features can now leverage Stigg to also export these raw events to Snowflake and BigQuery.
With this change you can leverage the same scalable and reliable event ingestion pipeline as the source of truth for usage metering, enforcement and billing as well for usage business intelligence and analytics. Thus, saving you valuable development time and engineering resources.
Exporting data to Snowflake and BigQuery is available as an add-on to the Stigg Growth plan, and is included as part of the Stigg Scale plan.
To export raw usage events as part of this integration, contact Stigg Support.
We've added an ability to view the changes of all of the Stigg SDKs using an SDK changelog.
The changelog includes the SDK version, its release date and changes that were included in that version.
Each SDK has its own separate changelog allowing you to easily keep track of the changes, and make it easier to determine the implications of updating the SDK version in your application.
To access it, use this link.
