IBeam.Billing.Services 2.9.45

IBeam.Billing.Services

IBeam.Billing.Services provides the service-layer implementation for IBeam billing records, provider-event ingestion, and local in-memory persistence.

dotnet add package IBeam.Billing.Services

For ASP.NET Core endpoints, use the future IBeam.Billing.Api package.

What This Package Contains

Quick Start

using IBeam.Billing.Services;

builder.Services.AddIBeamBillingServices(builder.Configuration);

Example offer configuration:

{
  "IBeam": {
    "Billing": {
      "Offers": [
        {
          "Key": "hubbsly-pro-monthly",
          "ProductKey": "hubbsly",
          "PlanKey": "hubbsly-pro",
          "DisplayName": "Hubbsly Pro",
          "BillingPeriod": "monthly",
          "Currency": "USD",
          "SeatPolicy": {
            "DefaultTotalSeats": 3,
            "MinimumTotalSeats": 3,
            "SeatIncrement": 1
          },
          "Pricing": {
            "PerSeatAmount": 25.00
          },
          "ProviderPrices": [
            {
              "ProviderName": "stripe",
              "PriceId": "price_pro_monthly",
              "BillingMode": "self-service-monthly"
            }
          ]
        }
      ]
    }
  }
}

Provider checkout quantity should be set from the resulting quote's TotalSeats. The offer always represents one license.

The bundled store is in-memory and intended for local development, tests, and prototypes. Production applications should replace IBillingStore with Azure Table, SQL, EF, or an application-owned provider.

builder.Services.AddIBeamBillingServices(builder.Configuration);
builder.Services.AddScoped<IBillingStore, MyBillingStore>();

Register the replacement after AddIBeamBillingServices so the host application's store wins.

Service Operations

Billing service methods are tagged with IBeamOperation names for policy, audit, and service-base consumers.

Provider Event Idempotency

BillingProviderEventService.RecordEventAsync creates a stable idempotency key from ProviderName and ProviderEventId. Replaying the same provider event returns the original billing event record instead of creating a duplicate.

Billing And Licensing Boundary

Billing services record commercial state. They do not directly authorize application access. A later reconciler can consume billing records and provider events, then update IBeam.Licensing grants, renewals, suspensions, revocations, seats, and credit grants.