Billing policy

Billing policy is an internal provider/control-plane operation. It is used by Novantra operators to inspect and adjust enterprise entitlement projections. It is not a customer self-service checkout, invoice, cancellation, or payment portal.

What the console owns

Open System -> Billing policy in the control plane. The console lets an authorized operator:

• inspect the effective entitlement projection for an organization and app key;
• create feature, limit, maintenance, migration, trial, or enterprise add-on grants;
• revoke active grants with a governed reason;
• trigger entitlement recomputation;
• preview feature and usage-cap access decisions from the effective entitlement projection and recorded commercial usage counters;
• review customer payment attempts, immutable policy events, and credit-ledger entries.

Runtime authorization reads the effective entitlement projection. It does not authorize directly against Stripe or another payment provider during workspace requests.

The access preview is an operator preflight. It uses the same commercial decision resolver as owner modules should use before they perform governed work, but it does not mutate usage counters. If no usage counter exists for the selected organization, limit, and UTC month, the decision reports missing usage evidence instead of assuming zero usage.

Grants

Use grants for reviewed enterprise exceptions, launch accommodations, maintenance windows, migrations, trials, or account-specific add-ons. Each grant requires a reason and can include evidence references. Limit grants must include a limit key and value.

Revoking a grant removes it from the next effective entitlement projection after recompute.

Policy events and credit ledger

Policy events are operator and runtime evidence for grant creation, revocation, dunning, and entitlement recomputation. Credit-ledger entries show immutable credit movements when credit operations are used.

Payment attempts show the sanitized state of customer portal billing actions: support fallback, pending Payment Element confirmation, projected completion, or failure. The staff view does not expose client secrets, card data, raw payment provider payloads, private discounts, or unrestricted billing metadata. The billing policy sweep marks expired pending payment attempts as failed with policy evidence so abandoned browser flows do not remain pending indefinitely.

Do not use these records as customer-facing billing statements. Customer billing and payment UX is owned by the customer portal.

Deployment posture

Cloud customer workspaces consume provider entitlement projections. On-prem organizations consume signed-license and per-organization entitlement projections. On-prem installations do not depend on live control-plane billing policy routes for normal workspace authorization.