Getting Started Concepts The Things Stack Cloud The Things Stack Enterprise Integrations API Hardware
Get The Things Stack

Concepts

    Overview
  • Architecture
    • Components
      • Alert Routing Server
      • Application Server
      • Console
      • Device Claiming Server
      • Device Template Converter
      • Gateway Configuration Server
      • Gateway Server
      • Identity Server
      • Join Server
      • Network Operations Center
      • Network Server
      • Packet Broker Agent
      • Tenant Billing Server
    • ID and EUI Constraints
    • Last Activity
  • Features
  • Networking
  • Migrate to The Things Stack
  • Packet Broker
  • Server Addresses
  • Advanced Topics
  • Troubleshooting
  • The Things Stack Sandbox

Tenant Billing Server

The Tenant Billing Server is an enterprise component that manages the creation, suspension and billing of tenants using different payment backends. It requires a license with multi-tenancy support.

Backends

The Tenant Billing Server backends allow the Tenant Billing Server to manage multiple payment service providers at the same time. The backends themselves are stateless, and maintain tenant information using the tenant attributes.

Stripe

The Stripe backend provides billing and tenant management support using Stripe’s pricing plans using Stripe’s webhook functionality.

Tenants are created when a customer subscribes to a pricing plan which is enabled in the backend configuration. As long as the customer maintains their subscription and their payments are up to date, the tenant remains active. As soon as the subscription ends, the tenant is suspended until another subscription is created for the same customer. If the customer subscription is changed to a different pricing plan, the tenant will be upgraded automatically as well.

See Modeling subscriptions for more information about Stripe products, pricing plans and subscriptions. You can also refer to the Billing with Stripe guide which covers the creation of products, pricing plans and subscriptions in Stripe.

Pricing Plans

Both metered and and recurring plans are supported by the backend. The metered plans will report the number of registered devices as part of the billing, while the recurring plans are meant to be used as fixed cost plans.

Tenant Entity Limits

It is possible to limit the number of entities that a tenant can own using Stripe’s pricing plan metadata.

← Packet Broker Agent ID and EUI Constraints →

On this page

  • Backends

Sections

Getting Started

Concepts

The Things Stack Cloud

The Things Stack Enterprise

Integrations

API

Hardware

Sitemap

View our Sitemap

Contributing

GitHub

About Us

The Things Industries