We're excited to share that Stigg now supports subscription payment delegation. Example use-cases include organizations that pay for subscription on behalf of their employees, and companies that pay for subscriptions that are managed by marketing and design agencies.

When subscription payment is delegated:

1. The managing customer (customer A) will have access to the subscriptions' entitlements and be attributed with feature usage

2. The paying customer (customer B) will be paying for the subscription

3. When Stigg is integrated with a billing solution such as Stripe or Zuora, Stigg will associate the subscription in the billing solution with the paying customer (customer B).

To delegate the payment of a subscription:

1. Create the managing customer (customer A) in Stigg

2. Create the paying customer (customer B) in Stigg

3. Attach a valid payment method to customer B in Stigg

4. Provision a subscription to customer A and pass the ID of customer B as the payingCustomer

Delegated subscriptions are reflected in the Stigg app:

1. In the managing customer (customer A) - a link to the paying customer will appear under the subscription details screen.

2. In the paying customer (customer B) - subscriptions that are only paid (and not managed) by the customer will appear in a dedicated tab under the "subscriptions" section of the customer details screen. Clicking on the subscription will redirect users to the subscription details screen of customer A.

In the Stigg API and SDKs, the paying customer ID is returned in the response of the getActiveSubscriptionList, getActiveSubscriptions and getSubscription endpoints, as well as all of the subscription-related webhook events.

Subscription payment delegation is supported in the Stigg SDK for Node.js v3.45.0, Stigg SDK for Python, Ruby, Java and Go v2.100.2, and Stigg SDK for JavaScript v3.22.0 or later.