> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/account-and-administration/billing.md). # Billing Billing lists the Stripe accounts that receive guest payments, their status, and the default account of the organization. {% hint style="info" %} **Requirements** * To connect and manage Stripe accounts, you need the **Super admin** role. See [Users and roles](/account-and-administration/users-and-roles.md). {% endhint %} Go to **Settings** → **Organization** → **Billing**. A connected, active Stripe account set as the default is what damage waivers, security deposits, upsells and other guest charges use. ## Billing accounts The accounts show as cards or as a table. **Connect** adds an account. Each card shows: * The badge **Test mode** for a sandbox account that takes no real money, and the badge **Default** with a star for the default account of the organization. * The name of the account, or its Stripe account ID when it has no name. * The status: **Complete** when the account is ready for billing, **Restricted** when it is not. * **Charges enabled** or **Charges disabled**, and **Details submitted** or **Details incomplete**. * The country and the default currency. The table has the columns **Name**, **Account**, **Live**, **Country**, **Currency**, **Charges** and **Details**. The sync icon on a row (**Sync billing account**) gets the latest status from Stripe. ## Account details Click an account to open its details. ### Information | Field | What it shows | | --------------------- | ------------------------------------------------------------------------ | | **Stripe Account ID** | The ID of the account. It links to the account in your Stripe Dashboard. | | **Email** | The contact email of the account. | | **Country** | The country of the account. | | **Default Currency** | The currency of the account. | ### Account status | Field | Values | What it means | | --------------------- | ------------------------------- | ------------------------------------------------------------------------------------------------- | | Status | **Active** or **Inactive** | **Active**: fully enabled and ready for billing. **Inactive**: Stripe onboarding is not finished. | | **Charges** | **Enabled** or **Disabled** | Whether Stripe accepts payments on the account. | | **Details Submitted** | **Submitted** or **Incomplete** | Whether all onboarding details were given to Stripe. | ### Manage | Action | What it does | Limits | | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | | **Complete Stripe setup** | Opens Stripe to finish the onboarding. | Only for an account that is not active. | | **Manage Stripe account** | Opens Stripe to update the account details. | Only for an active account. | | **Refresh account status** | Gets the latest status from Stripe. | None | | **Mark as default** | Makes the account the default of the organization. | Only for an active account. | | **Disconnect from Guestway** | Removes the account from Guestway. The Stripe account stays open, and you can still manage it in your Stripe Dashboard. | None | ## Connected accounts Guestway works with its own connected Stripe account for each organization. On this account, Guestway creates the charges, holds, refunds and payouts for damage waivers, deposits and upsells. Connecting always makes a new Guestway-connected account. It does not link an existing Stripe account in place. An account connected in one organization can be used again in another organization of the same holding. When Stripe reuses the verified business details of another Stripe account, the core business information is shared between the accounts. A change on one account can update the others that share the same details. ## Default account and inheritance The default account (**Default**, with a star) is the billing account of the organization, the global level. Properties inherit it: a listing uses the account of its multi-unit or complex, and these use the global account. A property can use another account on its **Billing** card. See [General](/properties/general.md#billing). Damage waivers and security deposits work only when an active account is the default of the organization. Until then, the readiness check of the protection step in the guest journey shows it. See [Guest journey](/guest-experience/guest-journey.md). ## Related * [How to connect Stripe to receive guest payments](/account-and-administration/billing/how-to-connect-stripe-to-receive-guest-payments.md) * [How to set your default billing account](/account-and-administration/billing/how-to-set-your-default-billing-account.md) * [How to set up protection](/guest-experience/guest-journey/how-to-set-up-protection.md) * [Guest portal](/guest-experience/guest-portal.md): where guests pay --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.guestway.io/account-and-administration/billing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.