Linkit

Billing suspension & service access

How Linkit responds when subscription billing is overdue after the grace period.

Billing suspension & service access

When an organization leaves the paid window and passes the configured grace period without settling the subscription line, billing status becomes OVERDUE. In that state Linkit applies a full service suspension:

  • HTTP APIs for authenticated tenant users return 403 Forbidden with body code: BILLING_SERVICE_SUSPENDED, except for payment, authentication, health, webhooks, and contract download routes.
  • Admin dashboard shows a blocking overlay; only the Payment and Legal contract flows remain reachable until billing is healthy again.
  • Connected apps stop syncing: scheduled and manual runs for the organization are skipped, and installed apps are paused until balances are cleared and the server lifts the freeze after a successful payment.

Operational state is also exposed on GET /api/v1/payments/status as service_operational (inverse of hard suspension) together with billing_mode, included_app_slots, and add-on subtotals for transparency.

Suspension checks may be cached briefly per organization; after a successful payment, allow/deny state catches up automatically.

Customer Groups

Organizing customers into segments for targeting and management

Payments Orders API

Create and track payment-provider order flows via the unified providers API

On this page

Billing suspension & service access