Billing for Add-on Licenses - request for help or best practices for Stripe integration #12614 | Support Center

oguzhanagir created 8 months ago

Support Team

Hi @eric_pulaski

I’d like to summarize the current state of add on licensing in ASP.NET Zero (such as additional widgets, additional users, etc.).

Current Structure

ASP.NET Zero’s payment system works as follows:

Edition based Payment: The system is built around the SubscriptionPayment and SubscriptionPaymentProduct entities.
Feature System: Features can be defined per Edition (via AppFeatureProvider), such as MaxUserCount.
Stripe Integration: Out of the box support exists for Edition purchase, upgrade, and subscription extension.

Status of Add on Licenses

Unfortunately, ASP.NET Zero does not provide a built in UI or infrastructure for add on licenses.

The existing system supports:

Initial Edition purchase
Edition upgrade
Subscription extension
Trial to paid conversion

Recommended Approaches

For add on licenses, you can apply one of the following approaches:

Manually Updating Tenant Feature Values (Simple Approach)

You can update a tenant’s feature values from the Host Admin panel.
This is supported via TenantAppService.UpdateTenantFeatures().
Payments can be handled separately in Stripe, and the feature value can be updated manually afterward.

Custom Add on Payment System (Recommended)

You can model your solution after the existing subscription flow. By taking the existing structure as a reference:

// Create an AddOnAppService similar to SubscriptionAppService
public async Task<long> StartPurchaseAddOn(PurchaseAddOnInput input)
{
    var tenant = await TenantManager.GetByIdAsync(AbpSession.GetTenantId());
    
    return await _paymentManager.CreatePayment(new SubscriptionPayment
    {
        TenantId = tenant.Id,
        SuccessUrl = input.SuccessUrl,
        ErrorUrl = input.ErrorUrl,
        IsRecurring = false,
        SubscriptionPaymentProducts = new List<SubscriptionPaymentProduct>
        {
            new(
                description: $"Additional {input.AddOnType} x {input.Count}",
                amount: CalculateAddOnPrice(input),
                count: input.Count,
                extraProperties: new ExtraPropertyDictionary
                {
                    {"AddOnType", input.AddOnType},
                    {"TenantId", tenant.Id.ToString()},
                    {"FeatureName", "MaxAllowedWidgets"} // Feature to be updated
                }
            )
        }
    });
}

To update the feature value after a successful payment:

// In PaymentAppService.cs or an event handler
await TenantManager.SetFeatureValueAsync(
    tenantId, 
    "MaxAllowedWidgets", 
    newValue.ToString()
);

UI Layer

Use subscription-management.component.ts as a reference.
Add a new “Purchase Add ons” section.
Reuse the existing gateway selection and payment flow.

For add on licenses, you will need to write mostly custom code, but you can still reuse the existing payment infrastructure (SubscriptionPayment, PaymentManager, Stripe integration). Rather than building everything from scratch, the recommended approach is to replicate the Edition upgrade flow and adapt it for add ons.

Billing for Add-on Licenses - request for help or best practices for Stripe integration #12614

2 Answer(s)