🆕 What's new

We’ve enhanced our Zuora integration to fully support termed subscriptions. You can now create subscriptions in Stigg and seamlessly sync them as termed subscriptions in Zuora, rather than relying solely on the default evergreen model.

Using specific subscription metadata keys during subscription creation, you can define the initial term length, renewal term length, period types (e.g., days, months, years), and exact renewal behaviors. Stigg automatically maps these details to the corresponding fields in Zuora.

⭐️ Why it matters

• Full Contract Control: You can precisely define if a subscription should auto-renew for another specific term, convert to an evergreen subscription upon renewal, or simply reach "Out of Term" status without auto-renewing.
• Streamlined Operations: By defining term logic directly within Stigg, you eliminate the need to manually adjust contract terms and dates in Zuora.
• Flexible Conversions: You can easily convert an existing evergreen subscription into a termed agreement (or vice-versa) straight from the Stigg UI just by updating the subscription’s metadata. Stigg will automatically issue the necessary amendment in Zuora.

⚒️ Get started

Managing termed subscriptions is handled entirely through Stigg's metadata mapping. You can learn more about termed subscription support in Stigg here.

We've decoupled the retrieval of customer usage history from their subscription lifecycle, giving you continuous and uninterrupted visibility into their activity.

🆕 What’s New

The behavior of the getUsageHistoryV2 endpoint has been extended. You can now retrieve a customer's usage history for a metered feature regardless of whether they currently have an active subscription or had one during the requested time frame.

If the customer does have an active subscription, the endpoint response includes a markers array containing the subscription's usage reset periods.

⭐️ Why It Matters

• Query usage data regardless of the subscription state
• Contextualized data: The markers array allows you to easily cross-reference raw usage data with entitlements, making it crystal clear exactly when a customer's usage was reset.

⚒️ Get Started

• GraphQL API and GraphQL-based SDKs - pass the includeInactiveSubscriptions: true parameter when calling the getUsageHistoryV2 endpoint.
• REST API and REST-based SDKs - simply call the getUsageHistory endpoint.

📦 Availability

GraphQL-based SDKs:

• Node SDK: v4.29.3
• Python / Java / Go / .NET SDKs: v6.2.3
• Ruby: v6.2.3

REST-based SDKs:

All versions

🆕 What's new

Following a successful private preview, we're excited to announce that the Stigg REST API is now available in Public Beta.

With this release, the REST API is now available to all customers and, most importantly, available for use in production environments.

⭐️ Why it matters

The transition to public beta reflects a significant step in the maturity of the REST API. Moreover, the REST API is now stable enough for use in production environments.

⚒️ Get started

To get started, call the REST API directly, or use our REST-based SDKs to get up-and-running faster in your native programming language.

We’ve decoupled the credit-granting process from the subscription lifecycle. 

🆕 What's new

You can now grant credits to customers, regardless of whether they have an active subscription. Thus, ensuring they are ready to go the moment they start using your product.

⭐️ Why it matters

This change provides the flexibility needed to handle modern SaaS onboarding and retention workflows:

• Seed New Accounts: Grant promotional or "trial" credits to leads before they even select a plan.
• Customer Support Flexibility: Quickly issue credits to customers whose subscriptions may have lapsed or haven't started yet.
• Reduced Friction: Sales and Support teams no longer need to wait for subscription creation to provide value to a user.

⚒️ Get started

To grant credits to a customer without a subscription:

1. Navigate to the Customers section in the Stigg App.
2. Select the specific customer.
3. Under the Credits section, click "+ Adjust Credits"
4. Enter the credit amount. For paid credits, specify the credit unit cost. 

The balance will update immediately, even if no plan is currently assigned.

🍿 See it in action

🔮 Coming up next

While credits can now be granted independently, credit consumption is still currently defined at the plan level and requires an active subscription. However, we are already working on decoupling the consumption flow as well, which will allow customers to draw down their credit balance even without a formal plan assignment. Stay tuned! 

We've added an ability to archive credit types. Instead of permanently deleting old credit types and losing historical data, you can now "soft delete" them when they're no longer in use. 

When a credit type is archived, customers that have credits with this credit type can continue consuming it; however, they can't be granted additional credits of that type.

🆕 What’s New?

• Archive with Ease: Remove outdated credit types from your primary view without losing their configuration or history.
• Centralized Visibility: Access your archived custom types anytime. We’ve added a new filter to the Credits screen, allowing you to toggle between active and hidden credit types seamlessly.
• Simple Restoration: Bring credit types back to life with the Restore action if you ever decide to resume offering them.

🛠 Get started

1. Navigate to Product Catalog > Credits in the Stigg app.
2. Select the three dots next to the credit type you wish to hide and click Archive.
3. To view or restore an item, use the status filter at the top of the list to select Archived credit types and simply click Restore.

We’ve enhanced the feature management experience in Stigg to give you instant visibility into exactly where your features are being utilized. You can now easily view which plans and add-ons a specific feature is included in directly from the feature's details screen.

🆕 What’s New

When managing your Product Catalog, clicking into any feature will now reveal a brand-new "Used by" tab. This tab displays a comprehensive list of all the active plans and add-ons that currently include the selected feature.

⭐️ Why It Matters

• Complete Visibility: Instantly understand the footprint of any given feature across your entire pricing model without having to manually dig through individual plans or add-ons.
• Streamlined Catalog Management: Save time navigating the Stigg app. The clear, centralized view helps product and monetization teams manage entitlements and troubleshoot customer access significantly faster.

⚒️ Get Started

To view what plans and add-ons a feature is used in:

1. Open the left navigation pane in the Stigg app.
2. Select Product Catalog, then choose Features.
3. Select the relevant row from the feature list to open the feature details.
4. Click on the new "Used by" tab to see the list of associated plans and add-ons!

🍿 See it in action

We've updated the behavior of the Checkout Widget to automatically reflect customer's billing address in generated invoices.

🆕 What's New

• The billing address that's collected via the Stigg Checkout Widget is now stored on the Stripe Customer object - before this change, the billing address was stored as part of the customer's payment method details.
• The billing address that customers enter in the Stigg Checkout Widget is now automatically reflected in generated invoices.

⭐️ Why It Matters

Including a customer's billing address on invoices is required for legal, tax, and compliance reasons in many jurisdictions.

⚒️ Get Started

To reflect this behavior, simply update the relevant Stigg frontend SDK to the latest version. 

If you're not leveraging the Stigg Checkout yet, click here to learn more how you can accept payments without ever worrying about changes to your pricing model or migration to another billing provider.

📦 Availability

The new behavior is available to all customers that leverage the Stigg Checkout widget together with Stigg's integration with Stripe.

This functionality is available in the following SDK versions:

• React SDK: v8.1.0
• Vue SDK: v6.1.0
• Embed SDK: v7.1.0

We've expanded the Stigg AI Credit Suite to allow you to easily link recurring credit grants to metered features (such as seats), automatically creating shared credit pools as your customers' teams grow.

🆕 What’s New

SaaS vendors can now define a specific number of included credits for every additional seat a customer purchases. When a new seat is added to a subscription, the relevant credit amount is automatically added to the customer's available balance.

Even better, these granted credits aren't siloed per user. Added credits can be shared across all seats, creating a unified shared seat-based credit pool that anyone in the organization can draw from.

⭐️ Why It Matters

• Scalable Pricing Models: Seamlessly tie your credit allocations to team growth. Provide a compelling package where adding more users naturally scales the organization's overall credit limit (e.g., "Get 1,000 AI credits per month for every seat").
• Maximum Flexibility for Customers: Simplify credit management for your users. Instead of individual users running out of credits while others have a surplus, the entire organization shares a single pool to maximize utilization.
• Automated Entitlement Operations: Say goodbye to manual adjustments. When a customer expands their team and adds new seats, Stigg handles the math and automatically provisions the correct amount of additional credits to their shared pool.

⚒️ Get Started

To configure a seat-based recurring credit grant:

1. Navigate to the Stigg App.
2. Create or edit a plan or add-on.
3. Add your credit as an entitlement.
4. Click on the "Link" icon to associate the credit grant with another entitlement to a metered feature (such as seats).
5. Define the amount of credits to be granted for each unit of the linked feature.
6. Publish the changes.

Once a customer subscribes, their shared credit pool will instantly update whenever a new seat is added!

🍿 See it in action

We are excited to bring more billing flexibility directly to your fingertips. When manually updating subscriptions to paid plans within the Stigg app, you now have complete control over how billing cycles and prorations are handled.

🆕 What’s New

You no longer need to rely on API calls to manage complex billing logic during subscription changes. When modifying an active subscription via the Stigg app UI, you can now configure:

• Billing anchor: Decide whether to keep the billing cycle exactly as it is (leave unchanged, which is the default) or immediately reset the billing cycle to the current timestamp.

• Proration behavior: Choose exactly how to handle the financial impact of the subscription change:

  • Invoice immediately: Generate and collect payment for the prorated amount right now.
  • Include in next invoice: Create the proration items but defer the charge until the next standard billing cycle.
  • Don't prorate: Disable prorations entirely for this specific update.

⭐️ Why It Matters

• Ultimate flexibility: Tailor the billing experience to specific customer scenarios. Whether you are executing an immediate mid-cycle upgrade, a requested downgrade, or a custom-negotiated contract change, you can ensure the invoice matches the agreement.
• Operational independence: Customer Success and Sales teams can safely make these complex billing adjustments instantly via the UI, without needing to loop in engineering to write custom scripts.

📦 Availability

The above configuration are fully supported when Stigg is integrated with Stripe, Zuora, or with a custom billing solution. 

🍿 See it in action

vWe are excited to announce a new capability that gives you more control over your customers' billing cycles when provisioning and updating subscriptions to paid plans and add-ons.

🆕 What’s New

You can now pass the billingCycleAnchor property with the following values when provisioning and updating subscriptions:

1. SubscriptionBillingCycleAnchor.UNCHANGED - keep the billing cycle anchor unchanged (the default behavior).

2. SubscriptionBillingCycleAnchor.NOW - reset the billing cycle anchor to the current timestamp.

⭐️ Why It Matters

This update introduces additional flexibility in how you bill customers for their subscription changes. By choosing whether to maintain the existing billing date or reset it to the moment the change occurs, you have fine-grained control over subscription cycles, prorations, and your customers' invoicing experience.

📦 Availability

The billingCycleAnchor property is fully supported when Stigg is integrated with Stripe, Zuora or with a custom billing solution. 

The new parameter is available in the following SDK versions:

• Node SDK: v4.33.1
• Python / Java / Go / .NET SDKs: v6.6.1
• Ruby: v6.4.0
• JavaScript SDK: v3.102.1