# Billing > Review workspace billing information and complete payment actions from the NexHost dashboard. Source: https://nexthomelabs.com/docs/billing Markdown: https://nexthomelabs.com/docs-md/billing Slug: billing Section: Teams and Billing Last updated: 2026-08-30 Reading time: 4 min read --- # Billing Open **Dashboard → Billing** to review the billing information associated with the **active workspace**. Every charge, plan selection, and payment record is scoped to the workspace — switching workspaces changes which billing view you are inspecting just as it changes which projects and services are listed. Use the values and actions presented there as the current source of truth for plan, payment, and account details rather than relying on memory of what was chosen during setup. This page intentionally avoids repeating numeric pricing or plan limits that are better sourced from the billing screen itself. What follows is the operational workflow around billing, so charges do not surprise you and support requests do not need to ask for the same context twice. ## When to review this page - When a deployment or scaling choice you are about to make has cost implications and you want to know what the workspace already holds. - When a billing contact changes roles and the owner listed on the workspace should be updated before the next cycle. - When a payment method needs review and you want the change to route to the intended workspace. ## Before changing billing details Confirm that you are in the **correct workspace** and that the **billing contact** is current. Two small confirmations prevent most "why did the wrong account get charged" tickets: 1. Read the workspace name shown in the header. 2. Read the contact email shown on the billing screen itself. Keep payment information inside the **secure dashboard flow**. The billing screen is the only channel that should see full payment input. Do not send card details, account credentials, or transaction references through project logs, deployment detail output, or support messages unless the support channel explicitly requests a safe method — and even then, use only the channel support provides, not a general email or chat transcript. If your organization separates concerns, assign one owner to per-workspace billing contact per workspace and document that ownership outside the platform so on-call can reach the right person during a payment incident without re-discovering the assignment under pressure. > [!WARNING] > Screenshots of the billing screen that include a complete card number, expiry, or CVV must never be shared. Redact sensitive fields before saving such a capture anywhere. ## How billing relates to services Creating, resizing, or deploying services — adding a database, adding a domain, adding concurrent workers — may change the workspace bill. The billing screen reflects the active **plan** and **payment** state that corresponds to those services. Consult it before and after a meaningful service change rather than assuming a previously quoted total still applies after the workspace has grown. ## Need help? Use the **dashboard’s Support entry** for a billing question and include the **workspace name** and any **non-sensitive reference** shown in the billing view (invoice number, line item name, or date). Support can then map your message to the right record without you exposing payment data. Good first messages include: - The exact workspace name as displayed at the top of the dashboard. - The invoice number or date when the question is about a specific charge. - The service or domain name when the question is "did this service cause this line item." Avoid: - Pasting card numbers, account logins, or transaction secrets into logs, tickets, screenshots, or chat messages. - Sharing the same message across workspaces when they have different owners — route the message to the accounting owner for the workspace that owns the charge. The dashboard Support path is the place to ask for a receipt reissue, a contact update, or a charge explanation. For non-billing operational issues, use the guidance under [Workspaces and Access](/docs/teams) and [Deployments](/docs/deployments). ## Related documentation - [Workspaces and Access](/docs/teams) — who can affect what within a workspace and how to report clearly. - [Services Overview](/docs/services) — which service types were added that may affect the bill. - [Custom Domains](/docs/configuration/custom-domains) — domain add-on state that may appear in add-on lines.