In the common use-case, Stigg only syncs customers with paid subscriptions to billing solutions that are integrated with Stigg.

There are cases where you'd like to explicitly sync customers to the billing solution, and we've recently made this possible by specifying billing information when updating customers. 

Syncing of entities between Stigg and third-party solutions usually takes place asynchronously. 

We've now made it possible to wait until the sync operation is complete. To do so, simply pass the shouldWaitSync parameter when updating customers. If successful, the response will include the ID of the customer in the billing solution.

The new functionality is supported by the Stigg Node.js SDK v2.31.0, Stigg Python SDK v0.577.0, Stigg Ruby SDK v0.577.0, Stigg Go SDK v0.577.0 or later, as well as the Stigg GraphQL API.

We've extended the Stigg Checkout widget to allow you to leverage third-party tax vendors such as Avalara to calculate and collect taxes according to customer's billing addresses.

To do so, follow this short guide.

The new functionality is supported by the Stigg React SDK v4.5.5, Stigg JavaScript SDK v2.24.2 and the Stigg Node.js SDK v2.31.0 or later.

We've updated the Stigg Go SDK to automatically retry requests that fail due to network errors.

The improved error handling is available in the Stigg Go SDK v0.570 or later.

We're excited to announce that Stigg can now leverage Stripe Tax to automatically calculate tax rates according to the customer billing address during checkout sessions, as well as configure Stripe to collect taxes on your behalf when provisioning and updating subscriptions.

Before the integration can be enabled, please make sure to set up Stripe Tax. 

To enable it, no code changes are required! Simply contact Stigg Support.

Once enabled, the relevant tax rates would be automatically reflected in the checkout experience that you've decided to implement either using the Stigg Checkout Widget, Stripe's hosted checkout page, or a custom checkout experience using the estimateSubscription and estimateSubscriptionUpdate methods of the Stigg SDKs and API. In addition, customers will be billed the relevant tax rates when provisioning and updating subscriptions using the Stigg SDKs and API.

More details about Stripe Tax can be found here. Details about the integration can be found here.

We've added an ability to store metadata in billing solutions that are integrated with Stigg, such as Stripe. Doing so is helpful when generating reports from the billing solution.

To store metadata in the billing solution, simply pass the relevant metadata under the billingInformation.metadata object when provisioning or updating subscriptions.

The new functionality is supported by the Stigg Node.js SDK v2.30.0, Stigg Python SDK v0.566.0, Stigg Ruby SDK v0.566.0, Stigg Go SDK v0.570 or later, as well the GraphQL API.

We're excited to announce the addition of a checkout widget to the Stigg Widget Library!

Stigg's checkout widget allows you to easily accept payments without ever worrying about changes to your pricing model or migration to another billing provider.

Using only a few lines of code you can offer customers a cart-like experience where they can configure their plans, add and remove add-ons and apply promo codes.

The checkout widget is optimized for SaaS and includes built-in support for advanced use-cases, such as multiple billable metrics, volume pricing, pay-as-you-go pricing, scheduled downgrades, downgrade to free, handling of prorations, and grandfathering.

The widget can be embedded directly into your application's UI, in a modal or even a completely separate page. Once integrated into your applications, changes to pricing and styling in the Stigg app are auto-magically reflected in the widget.

The checkout widget is available on the Stigg React SDK v4.4.4 and Stigg Vue.js v3.9.0 or later. More details can be found here.

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. Volume 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 volume 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 💪🤩.

Volume 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.