We've improved our native integration with Stripe and now automatically sync pay-as-you-go (PAYGO) charge data upon invoice generation.

Before this change, usage was periodically synced to Stripe, and in rare edge cases this caused customers to be billed for a some of their usage in subsequent billing periods.

With this enhancement, generated invoices always include line items based on the most up-to-date usage that was reported to Stigg.

More details can be found in our docs.

Stigg app users can now be invited to multiple Stigg accounts.

To switch between the different accounts, use the "Switch accounts" action in the user context menu that appears at the bottom of the left navigation pane.

In the opened screen, select the destination account.

When users are invited to additional Stigg accounts, they're automatically prompted to select the account that they'd like to access upon first login after the invitation.

More details can be found here.

We've added an ability to managed the discounts that are applied to subscription via the Stigg app UI.

In Stigg, discounts are applied to subscriptions using coupons. 

With this updated interface users can apply, update and remove coupons from subscriptions when provisioning and updating subscriptions in the Stigg app.

Before this change, this was only possible using the Stigg API and SDKs.

We're excited to share that Stigg now supports subscription payment delegation. 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 subscription payment is delegated:

1. The managing customer (customer A) will have access to the subscriptions' entitlements and be attributed with feature usage

2. The paying customer (customer B) will be paying for the subscription

3. When Stigg is integrated with a billing solution such as Stripe or Zuora, Stigg will associate the subscription in the billing solution with the paying customer (customer B).

To delegate the payment of a subscription:

1. Create the managing customer (customer A) in Stigg

2. Create the paying customer (customer B) in Stigg

3. Attach a valid payment method to customer B in Stigg

4. Provision a subscription to customer A and pass the ID of customer B as the payingCustomer

Delegated subscriptions are reflected in the Stigg app:

1. In the managing customer (customer A) - a link to the paying customer will appear under the subscription details screen.

2. In the paying customer (customer B) - subscriptions that are only paid (and not managed) by the customer will appear in a dedicated tab under the "subscriptions" section of the customer details screen. Clicking on the subscription will redirect users to the subscription details screen of customer A.

In the Stigg API and SDKs, the paying customer ID is returned in the response of the getActiveSubscriptionList, getActiveSubscriptions and getSubscription endpoints, as well as all of the subscription-related webhook events.

Subscription payment delegation is supported in the Stigg SDK for Node.js v3.45.0, Stigg SDK for Python, Ruby, Java and Go v2.100.2, and Stigg SDK for JavaScript v3.22.0 or later.

We've extended the Stigg Sidecar SDK to support Ruby and Go.

With this change, applications written in Ruby and Go can now also benefit from Stigg's persistent caching mechanism, entitlement access from the edge and built-in fallback strategy for high availability and scale.

This means that you can now enjoy lightning-fast⚡ entitlement checks at scale regardless of your application’s architecture (monolith, microservices or serverless) or language it's written in.

More details about the Stigg Sidecar can be found in our documentation.

We've extended our data warehouse integration and now support exporting the details of Stigg coupons and coupons that are applied to subscriptions.

Together with the subscription information that was already exported, customers can generate reports for tracking subscription discounts.

We've added an ability to create fixed fee coupons programmatically and via the Stigg app. Using this new functionality you can grant customers fixed fee discounts, such as $15 off.

Fixed fee coupon can be applied to customers and subscriptions:

1. To customers - via the Stigg app or programmatically by passing the Stigg coupon ID as the couponId parameter when provisioning and updating customers.

2. To subscriptions - programmatically by passing the Stigg coupon ID to the appliedCoupon object when provisioning or updating subscriptions.

When Stigg is integrated with a billing solution such as Stripe, Stigg will automatically create and update the relevant entities in the billing solution.

Fixed fee coupons can currently be created in USD. Support for additional currencies is on our roadmap.

We've added an ability to define usage reset periods for plan charges.

Similarly to entitlements, Stigg can optionally reset the measured usage at the end of the billing period or a subset of it (yearly, monthly, weekly, daily, and hourly).  

The new configuration is helpful when billing customers in advance, for example when billing according to Monthly Active Users (MAUs, similarly to AppCues' pricing) and daily sessions (similarly to HotJar's pricing).

In addition, the new configuration simplifies the implementation of pay-as-you-go (PAYGO) pricing when provisioned resources that customer are billed for persist, such as when billing customers for invited team members as they join or hired employees.

Defining the usage reset period is possible under the "Usage reset" section of every usage-based charge.

We've added an ability to override the prices of add-ons when provisioning subscriptions.

This new change allows you to offer customers the same add-ons using different price points, while still leveraging Stigg for managing the subscription billing.

Overriding the default add-on price is possible when provisioning and updating subscriptions in the Stigg app, by hovering on the relevant charges and selecting the "Edit price" action.

When the default plan price is overridden, an proper indication will appear next to the charge's price.

To apply the changes to the subscription, confirm the subscription provisioning.

Overriding the prices of plan charges and add-ons can also be done programmatically using the Stigg API and SDKs. This functionality is supported in the Stigg SDK for Python, Ruby, Go, Java and .NET from v2.73.0 or later.

We've extended the supported pricing models for pay-as-you-go (PAYGO) charges, and now include support for tiered and volume pricing.