Claude Billing Lifecycle Visual Map

Fresh map of the Claude.ai billing entry points, plan chooser, checkout surfaces, team and enterprise routing, buying-agent branch, API patterns, and blocked paid-plan states. Captured on 2026-06-29 from authenticated Chromium Profile 3 / tegy.

18 sanitized screenshots retained
10 live routes directly observed
31 billing-related endpoint templates mapped
0 payments, emails, or account changes made

Scope And Safety

The account was a Free plan account, so live testing stopped before payment submission, team email link delivery, cancellation, invoice retrieval, and usage-credit purchases. Raw network logs and text dumps were deleted from this report tree because they contained account identifiers and third-party telemetry keys. The committed evidence is screenshots with account identifiers redacted plus sanitized route and endpoint templates.

Evidence Quality

Tier Used For Meaning
Live screenshot Free plan shell, settings billing, upgrade chooser, Pro/Max checkout, Team/Enterprise starts, public sales page, buying-agent entry Direct visual capture from the authenticated browser session.
Live text/API Buying-agent chat start, enterprise CTA transitions, validation states, network endpoint templates Observed in page snapshots or network request lists, summarized without raw identifiers.
Static bundle Unreached route names, redirects, billing object names Extracted from the current Claude app bundle served by assets-proxy.anthropic.com; bundle timestamp observed as 2026-06-27.
Official docs Paid-plan cancellation, Team invoice/payment management, usage credits, Enterprise billing model Claude Help Center pages checked on 2026-06-29; linked in the source notes.
Blocked Successful payment, declined card, active paid Billing tab, invoice list, cancellation confirmation, post-email Team setup Would require payment, a paid account, account mutation, or external email handoff.

State Graph

Green nodes are directly captured live. Amber nodes are inferred from the app bundle or official docs. Red nodes are known but intentionally blocked in this session.

Free chat shell /new Account menu Upgrade entry Settings modal #settings/general Billing tab Free plan card Upgrade chooser Individual: Free, Pro, Max Pro checkout monthly / annual / invoice Max checkout 5x / 20x monthly Payment submit branch success / fail / 3DS Paid Billing tab payment / invoice / cancel Upgrade chooser Team / Enterprise tab Team start work email form Team post-email flow name, billing, invites Enterprise start routing question Contact sales page claude.com/contact-sales Buying agent entry + chat start text Usage credits Settings > Usage, add funds

Route Map

Route Status Surface Transitions Observed Or Inferred
/new Live Free chat shell with top Free plan / Upgrade chip, left rail, account button, and model controls. Account menu, settings, upgrade page, Code upgrade entry.
/new#settings/general Live Settings modal shell with tabs: General, Account, Privacy, Billing, Capabilities, Connectors, Claude Code. Billing tab switches modal content without leaving the chat shell.
/new#settings/billing Live Free-plan Billing tab with plan card, feature bullets, and Upgrade plan. Upgrade CTA opens /upgrade?from=billing.
/upgrade?from=billing Live Plan chooser with Individual and Team/Enterprise tabs, monthly/annual toggle, Free/Pro/Max cards. Pro checkout, Max checkout, Team start, Enterprise start, buying agent.
/upgrade/pro?interval=monthly Live Pro checkout with order review, billing interval toggle, payment iframe, invoice-name expansion, tax/VAT rows. Monthly/annual toggle updates totals in place; subscribe remains disabled without valid payment details.
/upgrade/max?from=billing Live Max checkout with 5x and 20x tiers and monthly order review. Tier toggle updates subtotal, tax, and total in place.
/create/team/start Live partial Team plan start with work email field and native browser validation. Post-email flow is blocked because it requires sending a sign-in link.
/create/enterprise/start Live partial Enterprise routing question with options for 500+ seats, HIPAA-ready offering, tailored contract, or none of the above. Sales-sensitive options change CTA to Contact sales; None did not visibly advance from this account.
https://claude.com/contact-sales Live Public sales page with quick-result Enterprise choices and complex-needs contact form. Opened from the Enterprise branch in a new tab.
/buying-agent?src=upgrade_page_team_tab Live partial Buying agent landing and chat-start text for plan selection help. Press Enter starts chat; screenshot capture timed out after chat start, but text and API calls were observed.
/create/team/name, /create/team/billing, /create/team/invites, /create/team/pending/:organization_id Static only Team setup continuation routes. Present in the current app bundle; not reached without email handoff.
/create/billing, /create/invites, /create/name, /create/billing/pending/:organization_id Static redirects Legacy or generic organization setup paths. Bundle maps these toward Team-specific create routes.

Sanitized API Pattern Map

Moment Endpoint Templates Notes For Tegy
App shell and free-plan context GET /api/account_profile
GET /api/accounts/{account_id}/invites
GET /api/organizations/discoverable
GET /api/billing/{org_id}/gift/purchase_eligibility
GET /api/organizations/{org_id}/overage_spend_limit
GET /api/organizations/{org_id}/trial_status
GET /api/organizations/{org_id}/paused_subscription_details
GET /api/bootstrap/{org_id}/current_user_access
Billing state is loaded alongside general workspace bootstrap. Tegy should keep plan, trial, pause, usage-credit, and access state in a single account/org snapshot.
Upgrade chooser GET /api/account/raven_eligible
GET /api/account/ss_enterprise_eligible
POST /api/billing/{org_id}/consumer_pricing
POST /api/billing/{org_id}/cw_pricing
POST /api/billing/{org_id}/individual_plan_pricing/v2
POST /api/billing/{org_id}/ss_enterprise_pricing
GET /api/team-signup/voucher-eligible
GET /api/team-trial/exposure-eligible
Plan cards appear pricing-driven. Do not hard-code all amounts into UI; use pricing responses and render unavailable states explicitly.
Individual and Max checkout GET /api/referral
GET /api/organizations/{org_id}/payment_method
GET /api/organizations/{org_id}/subscription/checkout_capabilities
GET /api/billing/stripe_region?country={country}&organization_uuid={org_id}
POST /api/billing/{org_id}/individual_plan_pricing/v2
GET https://api.stripe.com/v1/elements/sessions?...mode=subscription...
Checkout combines local tax/region calculation, saved-payment capability, and Stripe Elements state. Tegy needs disabled CTA and validation states before any mutation.
Buying agent GET /api/buying-agent/organizations?organization_uuid={org_id}&include_all_plans=true
GET /api/buying-agent/account-summary?organization_uuid={org_id}&target_organization_uuid={org_id}
POST /api/buying-agent/chat?organization_uuid={org_id}
Sales chat receives account and organization summary context. This is an AI boundary in Tegy terms and should require explicit operator review before cloning.
Static bundle billing names /api/billing/
/api/billing/gift/products?currency=
/api/billing/gift/validate?code=
/api/billing/gift/confirm
/api/billing/promotion/
/api/internal-test/account/subscription
Gift, promotion, and test subscription routes exist in code but were not active in the captured UI path.

Visual State Inventory

Captions call out what changed, what controls matter, and which branch the state feeds next.

Claude free plan new chat shell
01. Free plan chat shell. Primary billing signals are the top Free plan / Upgrade chip, the account button plan label, and a Code shortcut that also routes toward upgrade.
Claude account menu with upgrade entry
02. Account menu. Billing entry is a first-level Upgrade plan row, separate from Settings. Account identity text is redacted.
Claude settings modal general tab
03. Settings shell. Billing is a left-nav tab inside a modal over the existing chat page, not a full page navigation.
Claude settings billing tab free plan
04. Free Billing tab. The active subscription state is a compact plan card plus feature bullets and a single Upgrade plan CTA.
Claude individual upgrade yearly plans
05. Individual chooser, annual selected. Cards compare Free, Pro, and Max. Pro annual pricing is shown as a monthly equivalent with annual billing copy.
Claude individual upgrade monthly plans
06. Individual chooser, monthly selected. The same cards change price and commitment copy in place.
Claude Pro monthly checkout
07. Pro monthly checkout. Order review includes plan subtotal, local tax, total, renewal date, payment method, invoice-name checkbox, business tax ID, VAT, and disabled Subscribe.
Claude Pro yearly checkout
08. Pro annual checkout. The route remains the checkout route while interval selection updates price, tax, total, and renewal copy.
Claude Pro checkout invoice name expanded
09. Invoice-name expansion. The optional invoice name row expands into a Bill to field without leaving checkout.
Claude Max 5x checkout
10. Max 5x checkout. Same checkout structure as Pro, but plan selection uses usage tier controls.
Claude Max 20x checkout
11. Max 20x checkout. Tier toggle changes the order review to the higher monthly price and tax total.
Claude Team and Enterprise upgrade tab
12. Team/Enterprise chooser. Team has standard and premium seat rows; Enterprise has a separate path; buying agent is presented as a support path.
Claude Team create start work email
13. Team start. Work email is required and the copy says Claude will send a sign-in link. No email was sent in this capture.
Claude Team create empty validation
14. Empty Team email submission. No custom error banner appeared; browser validity prevented progress.
Claude Team create invalid email validation
15. Invalid Team email submission. Native browser validation points out the missing @ in the email address.
Claude Enterprise create start routing question
16. Enterprise start. The page routes users by needs: 500+ seats, HIPAA-ready offering, tailored contract, or none of the above.
Claude contact sales page opened from enterprise branch
19. Contact sales branch. Sales-sensitive Enterprise options open the public Claude sales page with quick-result and complex-needs paths.
Claude buying agent entry page
20. Buying agent entry. The page positions sales chat as a beta assistant with account-context awareness, privacy notice, and Enter-to-start interaction.

Blocked Or Inferred States

State Class What Is Known Why It Was Not Captured Live
Payment submit outcomes Checkout is ready for Stripe card collection and disables Subscribe without valid payment input. Likely branches include success, card decline, 3DS/authentication, and validation errors. No real card details were entered and no subscription was attempted.
Active individual Billing tab Claude Help Center says web/desktop Pro and Max cancellation starts from Settings > Billing and a Cancel button. Pro and Max renew automatically by default. The account remained Free, so no active paid card, cancel button, invoice list, or portal state was visible.
Team billing management Official Team billing docs describe Owner access from Organization settings > Billing, payment method updates, invoices, invoice name override, tax handling, cancellation, and resubscription. Team setup requires a work email link, and proceeding would mutate account/signup state.
Enterprise billing management Enterprise docs describe self-serve and sales-assisted options, seat fees, separate usage charges, and admin/billing management. Enterprise purchase/contract paths require eligibility, sales, or account mutation beyond safe observation.
Usage credits Official docs place individual usage credits under Settings > Usage; paid users can enable credits, add funds, configure spend limits, and auto-reload. Team owners can enable organization usage credits from Organization settings > Usage. The free account did not expose paid usage-credit controls, and purchasing funds would be a financial action.
Buying-agent chat screenshot Text and network were observed after pressing Enter: the agent sees the current Free plan and asks what the user wants to do. It posts to /api/buying-agent/chat. Screenshot capture timed out on browser/font readiness after the chat state; raw text was not retained because it contained account identity.

Tegy Parity Build List

  • Expose plan state in the main app shell, account menu, and Settings > Billing, with the same routeable entry points.
  • Keep Free, active paid, canceled-at-period-end, paused/past-due, trial, usage-credit, and team/enterprise states visually distinct.
  • Render pricing from server responses, including currency, tax, billing interval, renewal date, tier selection, regional availability, and discounts/promotions.
  • Use a dedicated checkout route with order review, payment method collection, invoice-name override, business tax ID, VAT/tax rows, disabled Subscribe, and validation states.
  • Model plan chooser branches separately: individual Pro/Max, Team self-serve setup, Enterprise sales/self-serve routing, and optional sales assistant.
  • Represent post-purchase billing management: payment method, invoice list, billing address, invoice recipient/name, tax exemption support path, cancel, resubscribe, and plan change.
  • Do not inject fake assistant messages into billing or sales chat. Any AI-assisted buying flow crosses the user/AI boundary and needs operator approval before implementation.
  • For Team, treat email-link signup and post-email routes as a separate lifecycle from consumer checkout: start, verify email, organization name, billing, invites, pending state.
  • For usage credits, separate subscription billing from credit balance, spend limits, add-funds purchase, auto-reload, alerts, and limit-reached confirmation.
  • Keep raw network logs out of committed artifacts; store only endpoint templates and redacted screenshots in product reports.

Source Notes

Source Use In This Report
Choose a Claude plan Plan names, intervals, and list-price context for Free, Pro, Max 5x, and Max 20x.
How do I sign up for the Pro plan? Pro signup path through Settings > Billing, upgrade page, billing interval, payment info, Subscribe, and renewal behavior.
How do I sign up for the Max plan? Max 5x/20x tier selection, upgrade path from Free/Pro, prorated upgrade notes, and renewal behavior.
What is the Team plan? Team seat types, minimum member count, pricing intervals, usage limits, and Team to Enterprise boundary.
Team plan billing FAQs Team payment methods, Organization settings > Billing, invoice access, invoice-name override, tax handling, and resubscribe path.
Cancel paid Claude subscription Individual Pro/Max cancel path and cancellation timing.
Cancel Team plan subscription Team cancellation owner path and access-through-current-cycle behavior.
Manage usage credits for paid Claude plans Individual paid usage-credit enablement, add funds, spend limits, auto-reload, and limit-reached confirmation.
What is the Enterprise plan? Enterprise self-serve versus sales-assisted framing and feature/billing model.
How am I billed for my Enterprise plan? Enterprise seat-fee plus usage-charge billing model.