We're excited to announce that every Stigg environment can now be integrated with multiple billing providers at the same time!

The new functionality allows SaaS vendors to leverage Stigg as the single source of truth for their product catalog, customers, subscriptions, and entitlements while using different providers for billing.

Common use-cases include requirements to bill customers from different business entities (for example: for revenue recognition and tax purposes) and the need to support multiple billing providers as a result of merges and acquisition.

Whenever a billing provider is integrated with a Stigg environment, the Stigg product catalog is automatically synced to it. Vendors can then leverage Stigg's SDKs, API and user interface to route customers and subscriptions to the relevant billing provider. When no explicit routing is specified, customers and subscriptions will be created in the billing provider that's designated as the "default".

Beyond managing multiple billing providers, this new functionality makes migration between billing providers easier than ever. To do so, start by changing the default billing provider to route all new customers and subscription to the new provider. Then, follow a simple procedure to migrate existing entities.

The new feature is supported by the Stigg Node.js SDK v3.63.0, Stigg Python SDK v2.331.1, Stigg Ruby SDK v2.331.1, Stigg Go SDK v2.331.1, Stigg Java SDK v2.331.1, Stigg C# SDK v2.331.1, Stigg Sidecar SDK 2.337.0, and Stigg JavaScript SDK v3.37.0 or later.

More details can be found in our docs.

We've added an ability for team members to automatically join a Stigg account using an authorized email domain. Users outside of the company can still join the account if needed via an explicit invitation. 

To enable this configuration, navigate to the Account Settings > Login options tab, under "access method" select "Authorized domain" and the relevant domain from the list.

The new configuration natively integrates with Stigg's role-based access control (RBAC) capabilities - team members that join the Stigg account are granted a default role and level of environment access.

Allowing users to automatically join a Stigg account using an authorized domain is available as part of Stigg's Scale plan. 

More details about the available login options can be found in our docs.

We've added the ability to schedule syncing of subscription metadata to integrated billing providers. Before this change, syncing of metadata to billing providers occurred immediately even if the actual change to the subscription was scheduled to take place at a later date.

Syncing metadata to billing providers can be helpful when when there are existing BI reports that rely on information from the billing provider. Integrating Stigg with billing providers allows you to leverage existing reporting capabilities.

To sync subscription metadata to integrated billing providers, pass the billingInformation.metadata property when calling provisionSubscription or updateSubscription. To schedule the sync, also pass the scheduleStrategy property.

The new behavior is supported by all existing SDK versions - no changes are required.

We've increased the precision of prices that can be defined in the Stigg platform. Prices can now be defined with up to 7 decimal points; thus, allowing you to bill customers for their usage with higher granularity.

We've excited to share the availability of fine-grained control over how team members access your account and its entities using a concept of role-based access control (RBAC). 

As part of this functionality, Stigg offers 2 types of account-level roles:

1. Owner - can do everything in the account, including managing team members, billing and security settings.

2. Member - can view and manage environments they have been granted access to.

Access to environments is granted separately according to the environment type (production and non-production) and supports the following levels of access:

1. Full access - manage environments, product catalog, customers, subscriptions, and integrations.

2. Customer management - manage customers and subscriptions, all other entities are read-only.

3. Read-only - read-only access to all entities in Stigg.

4. No access - no visibility or access to this type of environments.

Account owners can define team member access upon invitation, as well as updating their details after they joined the account.

SSO natively integrates with Stigg's role-based access control (RBAC) capabilities. When SSO is enabled, team members that join the Stigg account are granted the default role and level of environment access, that are defined in the SSO configuration.

Role-base access control is included in the Scale plan. Without it, team members are granted an Owner role to the account and full access to all of its environments.

More details about role-based access control can be found here.

We've added the ability to unarchive features, plans and add-ons. Doing so is possible using the unarchiveFeature, unarchivePlan and unarchiveAddon mutations of the GraphQL API.

Unarchived entities will be set with the previous status they had before they were archived - "Active" for features, and "Published" for plans and add-ons.

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.