Settings Guardrails
Source-static proofBilling Entitlement Console
Stripe/payment setup deferredEntitlementsBilling providerNot configured ready for review.ProviderStripe or future payment providerNo products, prices, checkout, webhooks, customer records, or secretsAuditPayment provider intentionally deferredContinue with entitlement placeholders
Billing & entitlements
Plan posture, feature limits, and provider deferral without a checkout surface.
Billing opens as an admin entitlement console while staying strictly placeholder-only: no customer billing record, payment method, subscription change, invoice, or capture.
Deferred by ownerStripe or future payment provider
No products, prices, checkout, webhooks, customer records, or secrets
Billing providerNot configured
Stripe setupDeferred
Payment actionsDisabled
Plan changesBlocked
Enabled placeholderCore operations
20 properties, 2 work rows, 1 inspections, 2 documents, 1 reports
No paid subscription changeEnabled placeholderLong-Term backboneRent roll, residents, leases, delinquency, deposits, ledger views
No rent payment collectionEnabled placeholderMoney operationsReceivables, payouts, payables, owner statements, reconciliation
No bank, card, ACH, payout, or Stripe setupProvider readinessAll payment dependencies are deferred, blocked, or synthetic-safe.
Provider rows explain what cannot happen yet, so billing planning stays decoupled from live Stripe, bank, channel payout, plan, invoice, and subscription workflows.
Stripe or future payment providerSubscription billing and payment processingStatus: Deferred by ownerBlocked: No products, prices, checkout, webhooks, customer records, or secrets
Bank / ACH providerRent, owner draws, vendor and cleaner paymentsStatus: Not configuredBlocked: No bank accounts, no ACH, no payouts, no reconciliation feeds
Channel payout importsAirbnb, Vrbo, Booking.com, direct booking payoutsStatus: Provider not configuredBlocked: No live import, no private reservation/payment data, no channel writeback
Plan and invoice managementRing & Knock customer billingStatus: Placeholder onlyBlocked: No paid plan activation, no invoice delivery, no payment method collection
Read-only billing review only; no checkout, invoice send, subscription change, payment capture, provider activation, billing portal launch, transfer, payout, webhook secret, or tenant writeback.
Billing Entitlement Overview
Provider not configuredSection 1 entitlement-overview carry-throughStart with tenant-safe entitlement metrics so plan posture, synthetic readiness, and deferred provider state are visible before table review.Billing remains synthetic-only, provider-safe, and no-live.
Billing providerNot configured
Stripe setupDeferred
Payment actionsDisabled
Plan changesBlocked
Plan Entitlements
Section 2 plan-entitlements carry-throughReview entitlement status, coverage, limits, and blocked billing actions together so workspace planning stays bounded and read-only.No checkout, invoice issuance, charge execution, or subscription change is available here.
| Entitlement | Status | Includes | Limit | Billing Action |
|---|---|---|---|---|
| Core operations | Enabled placeholder | 20 properties, 2 work rows, 1 inspections, 2 documents, 1 reports | Synthetic demo limit only | No paid subscription change |
| Long-Term backbone | Enabled placeholder | Rent roll, residents, leases, delinquency, deposits, ledger views | Synthetic fixture rows only | No rent payment collection |
| Money operations | Enabled placeholder | Receivables, payouts, payables, owner statements, reconciliation | Provider-agnostic workflow states | No bank, card, ACH, payout, or Stripe setup |
| AI assistance | Draft-only placeholder | Message drafts, report drafts, source-backed summaries, review suggestions | Synthetic/account-scoped source records only | No autonomous send, publish, charge, pay, or access release |
| Integrations | Provider not configured | Read-only connector scope planning, API/email/webhook/MCP placeholders | No tokens, secrets, credentials, or external writes | No third-party account modification |
Provider Readiness
Section 3 provider-readiness carry-throughUse provider readiness to confirm every external dependency remains deferred, blocked, or synthetic-safe before interpreting tenant billing posture.All provider references remain placeholders only.
| Provider | Area | Status | Blocked Actions | Safe Next Action |
|---|---|---|---|---|
| Stripe or future payment provider | Subscription billing and payment processing | Deferred by owner | No products, prices, checkout, webhooks, customer records, or secrets | Evaluate payment options later |
| Bank / ACH provider | Rent, owner draws, vendor and cleaner payments | Not configured | No bank accounts, no ACH, no payouts, no reconciliation feeds | Keep Paid externally and Reconciled workflow states only |
| Channel payout imports | Airbnb, Vrbo, Booking.com, direct booking payouts | Provider not configured | No live import, no private reservation/payment data, no channel writeback | Use synthetic source records until connector scope is approved |
| Plan and invoice management | Ring & Knock customer billing | Placeholder only | No paid plan activation, no invoice delivery, no payment method collection | Represent entitlement limits without charging |
Billing Audit Queue
Section 4 audit-queue carry-throughClose with audit events so entitlement posture, provider deferral, and tenant-safe evidence all land in one receiving surface.Audit rows stay review-only and synthetic-safe.
| Event | Status | Evidence | Tenant Safety | Next Action |
|---|---|---|---|---|
| Payment provider intentionally deferred | Accepted owner decision | Stripe/payment setup is not part of current phase | No secrets, no webhooks, no paid subscriptions | Continue with entitlement placeholders |
| Entitlement gate added | Planning proof | Feature areas map to account/workspace limits | Entitlements do not replace RLS or role permissions | Wire to database only after account schema exists |
| External billing actions blocked | Required | No plan changes, no checkout, no payment method forms | No third-party account modification | Owner approves payment path later |
Billing Guardrails
Billing is entitlement modeling onlyBilling entitlements derive from active synthetic POC fixtures only; denial tenant billing rows render as zeroStripe and live payment processing are deferredNo customer billing records, payment methods, bank data, checkout, products, prices, invoices, or webhook secretsNo paid subscription creation, checkout, billing portal launch, payment collection, transfers, payouts, invoices, or plan changesNo provider credentials, Supabase writes, database migrations, seed execution, or real-data migrationTenant isolation and role permissions still control all feature accessFuture owner real data must use a separate second tenant after migration, security, and tenant-isolation approvalMoney workflows use provider-agnostic states like Imported, Pending, Received, Paid externally, and Reconciled
Route Closure
Source-static route closureBilling Settings now carries supervisory continuity, entitlement posture, deferred provider readiness, bounded audit readability, and tenant-safe billing review through the full receiving surface.All billing behavior remains synthetic-only, no-live, and provider-safe.
Boundary rules summaryRead-only billing review only; no checkout, invoice send, subscription change, payment capture, provider activation, or tenant writeback.The receiving surface stays source-static, review-only, and ready for later no-live validation routing only.