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

We 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 / Ruby / Java / Go / .NET SDKs: v6.6.1
• JavaScript SDK: v3.102.1

We've added an ability to control how credit entitlements behave when customers purchase an add-on, giving you even more flexibility to model your pricing exactly the way you want.

🆕 What’s New?

Previously, when a customer purchased an add-on containing credits, the add-on amount would automatically increment their existing plan limit.

With the additional Entitlement Behavior setting, you can now choose exactly how those credits interact with the base plan. You can set the behavior to either:

1. Increment plan limit (Default): The add-on credits are added on top of the base plan's credit limit. (e.g., A plan with 100 credits + an add-on for 50 credits = 150 total credits).
2. Override plan limit: The add-on completely replaces the base plan's credit limit. (e.g., A plan with 100 credits + an override add-on for 500 credits = 500 total credits).

⭐️ Why Does This Matter?

This added flexibility is perfect for businesses that use credits for monetizing their products. It allows you to:

• Create Upgraded Credit Tiers: Offer add-ons that act as strict upgrades rather than cumulative top-ups, ensuring your customers are bumped to a specific new tier of credits without complex math.
• Tailor the Customer Experience: Give your customers exactly the amount of credits they paid for through custom, bespoke add-ons that act as strict limit overrides.

⚒️  Get Started

Configuring this behavior takes just a few clicks within the Stigg app:

1. Open the selected add-on.
2. Add a new credit entitlement (or edit an existing one) under the Entitlements section.
3. In the entitlement settings, locate the “Entitlement behavior” dropdown.
4. Select either “Increment plan limit” or “Override plan limit”.
5. Save the configuration and hit Publish for the changes to take effect!

🍿  See it in action

We’re giving you even more control over your custom enterprise deals by bringing variable recurring credit grants directly into Stigg Workflows.

🆕 What’s New

You can now automate the provisioning of subscriptions to custom plans that include variable recurring credit grants using Stigg Workflows. This allows you to dynamically set and pass the exact credit allocation needed for an individual customer directly through an automated workflow.

⭐️ Why It Matters

• Support custom monetization flows: Seamlessly weave variable credit grants into your unique onboarding, upgrade, and provisioning logic.
• Bypass CRM API limits: Offload complex provisioning logic to Stigg, which is especially helpful if your Salesforce environment is constrained by strict external API call limits.
• Superior debugging and troubleshooting: Take advantage of the robust monitoring and error-handling capabilities built into Stigg Workflows, offering a smoother and more transparent experience compared to native tools like Salesforce Flows.
• Connect any system: Easily integrate custom credit provisioning with other CRMs, billing engines, or internal tools that Stigg doesn't natively integrate with today.

⚒️ Get Started

To start provisioning custom grants via Workflows, simply add a Provision Subscription or Update Subscription action node to your workflow canvas.

Inside the node's configuration, locate the Credit Entitlements section. From there, dynamically pass the relevant credit currency and the specific variable entitlement value you want to grant.

For a deeper dive into configuring these nodes, check out our documentation on Stigg Workflows and Workflow actions.

📦 Availability

This capability is available immediately for all customers utilizing Stigg Workflows.

We’ve extended our Salesforce integration to support the provisioning of recurring credit grants, smoothly bridging the gap between your sales motions and credit provisioning.

🆕 What’s New

Vendors can now provision subscriptions to custom plans with variable recurring credit grants directly from within Salesforce. 

When closing a deal, your sales team can easily input the exact custom credit allocation agreed upon in the Salesforce contract, and Stigg will immediately execute the grant.

⭐️ Why It Matters

• Automate sales-led provisioning: Fully automate the provisioning of sales-led, credit-based subscriptions without requiring manual intervention from your RevOps or engineering teams.
• Accelerate time-to-value: Ensure enterprise customers get instant access to their uniquely negotiated credit limits the moment a deal is closed in Salesforce.
• Maintain a single source of truth: Keep your CRM and entitlement data perfectly in sync, reducing human error and streamlining your quote-to-cash workflow.

⚒️ Get Started

To enable this functionality, you'll need to map your credit products in Salesforce to your credit types in Stigg. 

To do so, navigate to your Salesforce environment, locate the relevant credit product, and set the Stigg type field to Credit entitlement. Once mapped, variable credit grants can be defined and passed through during the standard subscription provisioning flow within Salesforce.

For more detailed setup instructions, check out our documentation on the Salesforce integration and entity mapping.

📦 Availability

This feature is available for customers using the Stigg app for Salesforce v1.13.0 or later.

We’ve rolled out a sleek visual update to the Stigg app to make managing pricing, packaging and entitlements an even better experience.

🆕 What’s New

Both our light and dark mode themes have received a comprehensive design refresh. We've meticulously updated our color palettes, refined our interface components, and polished our typography across the entire platform to give the app a more modern and cohesive feel.

⭐️ Why It Matters

• Improved usability: A cleaner interface helps you navigate complex pricing models and customer data with greater ease and speed.
• Enhanced consistency: Unified design patterns and components across all screens ensure a familiar and intuitive experience, no matter which part of the app you are using.
• Better readability: Optimized contrast levels and refined typography reduce eye strain and make your data - from entitlement limits to billing metrics - much easier to parse at a glance.

⚒️ Get Started

There's no action required on your end - the new UI is already live in your account!

If you'd like to toggle between the newly updated light and dark modes to see which one you prefer, simply click on the icon in the top-left corner of the app.

📦 Availability

This UI update is now live and automatically available for all Stigg users across all environments.

🍿 See it in action

We’ve introduced a lightning-fast way for developers to retrieve and display customer credit balances, ensuring your in-app experiences remain snappy and scalable.

🆕 What’s New

Developers can now utilize the new getCreditEntitlement() endpoint to instantly retrieve a customer's current credit balance. When recurring grants are included in plans and add-ons the response will include their next reset date.

Built on top of Stigg's highly scalable infrastructure, this endpoint is served directly from the Edge. For maximum performance, when integrated with Stigg's persistent cache, this data can be accessed with < 10ms latency.

⭐️ Why It Matters

• Exceptional User Experience: Presenting real-time credit balances and reset dates to your customers is crucial for transparency. 
• Built for Scale: By serving requests from the Edge and for persistent cahce, this endpoint is designed to handle massive traffic spikes effortlessly.

⚒️ Get Started

To implement this, simply update your Stigg SDK to the latest version and call the getCreditEntitlement() method for the relevant customer. 

For detailed implementation instructions, check out the SDK documentation, as well as our guides on leveraging Persistent Caching.

📦 Availability

This functionality is available now in the following SDK and service versions:

• Node SDK: v4.30.1
• Python / Ruby / Java / Go / .NET SDKs: v6.40.0
• JavaScript SDK: v3.99.1
• Sidecar SDK: v6.7.3
• Persistent Cache Service: v3.1.1

We've enhanced our custom plan capabilities, giving you the flexibility to negotiate and define custom recurring credit limits for your enterprise customers on the fly.

🆕 What’s New

Vendors can now define recurring credit entitlements within custom plans as variable.

Just like other variable entitlements in Stigg, this means you no longer need to create separate plans for each closed contract. Instead, leverage Stigg's custom plans as templates for contract negotiation and specify the actual value of the recurring credit grant upon subscription provisioning.

Currently, monthly and yearly recurring grants without rollover are supported for variable limits.

⭐️ Why It Matters

• Enterprise-grade flexibility: Tailor included credit limits to match the specific needs and negotiated terms of individual enterprise deals without cluttering your product catalog with one-off plans.
• Streamlined sales motions: Empower your sales and success teams to easily adjust recurring credit allocations right at the moment of closing the deal or provisioning the subscription.
• Automated provisioning workflows: Once the custom value is set during provisioning, Stigg automatically handles the monthly or yearly recurring grants based on that specific amount for the lifetime of the subscription.

⚒️ Get Started

To grant custom credit grants:

1. Navigate to the Stigg App.

2. Create or edit a custom plan.

3. Add your credit as an entitlement. When defining the entitlement, mark the entitlement value as variable and choose a monthly or yearly recurring cadence.

4. If you have not done so already - specify the metered features that will be used for credit consumption.

5. Publish the changes.

Then, when provisioning a subscription for a customer (either via the Stigg App or through the Stigg API), you will be prompted to input the negotiated recurring credit limit for that specific subscriber.

📦 Availability

The new functionality is available to all Stigg customers.

Programmatic provisioning of subscriptions with custom recurring grant entitlements is supported in the following SDK versions:

• Node.js: v4.30.1
• Python / Ruby / Go / Java / .NET: v6.40.0
• Sidecar SDK: v6.7.3
• JavaScript SDK: v3.99.1

🍿 See it in action

We've expanded our credit management capabilities to allow you to easily include recurring credit grants directly within your plans and add-ons.

🆕 What’s New

Vendors can now configure recurring credit grants as entitlements that can be directly attached to any plan or add-on in Stigg.

Currently, monthly and yearly recurring grants without rollover are supported.

To give you and your customers complete visibility, these recurring grants will be surfaced across the Stigg UI:

• Customer Details & Subscription Details: Grants will appear clearly under both the Entitlement Summary and Entitlement Usage sections.
• Customer Details > Credits tab: You can view a detailed breakdown of credit consumption and active grants.

Recurring grants work seamlessly with Stigg's existing credit capabilities, including one-time top-ups; thereby, allowing your customers to decide whether to increase their available credits on a recurring basis or using an ad-hoc credit purchase.

⭐️ Why It Matters

• Flexible Pricing Models: Easily support "included credits" as part of a base subscription (e.g., "5,000 AI credits included per month on the Pro Plan").
• Automated Refills: No need to manually grant credits each billing cycle. Stigg handles the monthly or yearly recurring grants automatically as long as the subscription is active.
• Clear Visibility: Give your success and support teams instant visibility into exactly how many credits a customer was granted through their subscriptions and how much they have consumed.

⚒️ Get Started

To include a recurring grant:

1. Navigate to the Stigg App.

2. Create or edit a plan or add-on.

3. Add your credit as an entitlement. When defining the entitlement, you can specify the grant amount and choose a monthly or yearly recurring cadence.

4. If you have not done so already - specify the metered features that will be used for credit consumption.

5. Publish the changes.

Once a customer subscribes to the plan or add-on, the credits will be automatically granted and reset according to the defined cycle!

🍿 See it in action

Scoped API keys are now available.

You can now create multiple API keys per environment, each with a specific set of permissions, so your integrations only get access to exactly what they need.

🆕 What's new

• Multiple scoped keys per environment: Generate as many keys as you need across your test, sandbox, and production environments, each scoped to a specific permission level. Assign them to individual services, teammates, or CI/CD pipelines.
• Fine-grained permission scopes:
  • Full access - complete read/write across all resources
  • Read only - read access across all resources, no writes
  • Customers write - manage customer data
  • Subscriptions write - create and update subscriptions
  • Coupons write - manage discount and coupon logic
  • API keys read & write - manage API keys programmatically
• Rotate or revoke anytime: Each scoped key can be rotated or revoked independently, without touching your other keys.
• UI & API support: Create and manage scoped keys directly from the dashboard or via the API to automate key provisioning as part of your infrastructure workflows.

⭐️ Why it matters

• Principle of least privilege: Instead of sharing a single full-access key everywhere, you can now issue narrowly scoped credentials per environment, limiting blast radius if a key is ever compromised.
• Cleaner integrations: Assign different keys to different services or teammates, each with only the permissions they need.
• Audit clarity: Multiple named keys make it far easier to trace which system made which call, and to revoke access for a specific integration without disrupting others.

🔒 Availability

Scoped keys are available on the Scale plan.

🛠 Get started

Navigate to Integrations > API keys inside your environment and click + Add scoped key to configure your first scoped credential.

To learn more about managing scoped keys via the UI or API, check out our documentation.

🍿 See it in action