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.