We've extended integration with Stripe to support importing of plans that have per-unit and usage-based pricing.

The import flow now also supports searching for specific Stripe product and customers; thus, allowing gradual import of entities from Stripe to Stigg.

The Stigg product catalog now includes support for coupons.

Coupons can be used to grant percentage discounts (X% off) to specific customers for all of their subscriptions.

The discounted price is reflected under the customer details screen in the Stigg Console, as well as the customer portal that can be generated using the Stigg SDK.

Coupons are synced to Stripe, and when a coupon is applied or removed from a customer in the Stigg, the action is also propagated to Stripe - this de-facto means that Stigg can be used to manage coupons in Stripe.

We've adapted the UX of the Stigg Console to better cater to developers' needs - since the integration between the app's codebase and Stigg takes place at the feature-level, we've added instructions on how to integrate each feature directly within the Stigg Console.

Developers can simply copy the relevant snippets and see Stigg in action immediately 🚀, read our documentation or invite additional team members.

The instructions also include syntax highlighting for the platforms that we support.

We've added an ability to store customers' payment details in Stripe directly from the Stigg Console.

Valid payment methods are required in order to create subscriptions for paid plans and add-ons.

The new functionality allows CS and technical support representatives enter the relevant payment information directly from the Stigg Console. The payment details are stored directly in Stripe.

Storing the payment details can be done proactively for each customer under the Customer details section of the Customer details screen, or as part of the subscription creation flow when the customer doesn't have any valid payment details defined.

The Stigg Console provides visibility whether the customer has a valid payment method defined and the last 4 digits of that payment method under the Customers > Customer details screen.

In order to lower the integration bar, and save precious developer time we now allow our customers to import their existing product catalog from Stripe.

Stigg's customers can also import their customers and active subscriptions to Stigg; thus, saving approximately 1 week of integration work in writing the migration script ⏱

The new functionality allows Stigg's customers to quickly get up-and-running with Stigg, test their integration, and rollout it out to production 💪.

⚠️ The import flow currently only supports the flat fee pricing model.

As part of our scalable architecture, updates to entities in Stigg are sent asynchronously to third-party integrations.

We've updated our UX to accommodate for this behavior - entities now have an indication of their sync status to the relevant third-party integration. There's also an indication for entities that are not synced (for example: plans and subscriptions with a custom price are not synced to billing solutions), as well as entities that their sync failed.

The timestamps in the Stigg Cloud Console now appear in the time zone of the computer that's used to access the Stigg Cloud Console.

In addition, in order to support collaboration across multiple time zones, an account-level time zone can be defined, which allows Stigg admins to refer to entities and actions that take place on them using the same timestamp.

Moreover, in order to assist developers and tech support representatives👩‍💻🧑‍💻 in troubleshoot issues, Stigg also provides visibility for the timestamp in the UTC standard, which is the standard that's commonly used for searching logs and alerts.

Accessing the account and UTC timestamps is possible by hovering over the timestamp in the Stigg Cloud Console.

We've extended our integration with Stripe to include automatic propagation of usage data of subscriptions to plans that have a usage-based pricing model from Stigg to Stripe.

This allows Stigg's customer to bill their customers based on usage data that's reported to Stigg.

Usage-data between Stigg and Stripe is synced on an hourly basis.

When plans have multiple billing periods (monthly and annually) there's now an indication below the price to the billing period that it refers to.

When all plans have only one billing period, the billing period switcher is hidden.

We've extended our integration with Stripe checkout form, and it's now possible to pay for plans that have per-unit pricing, as well as subscriptions that include both plans and add-ons using the Stripe checkout form.