> For the complete documentation index, see [llms.txt](https://docs.ovationvr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovationvr.com/ovation/creating-an-account/billing-1.md). # Failed Payment Each billing date we attempt to charge the account's credit card on file. ### Individual If we are unable to successfully charge the subscription fee, the account will be deactivated and will not be able to use Ovation. If the billing information is updated and the subscription fee is successfully charged, the account is reactivated. ### Organization Member An Organization Member does not pay for the subscription it occupies and cannot fail a payment. ### Organization Admin If we are unable to successfully charge the subscription fee, the Organization Admin subscriber and all Organization Members will be deactivated and will not be able to use Ovation. If an Organization Admin, or Organization Member with the appropriate billing role, updates their billing information and the subscription fee is successfully charged, the Admin account and all Organization Members are reactivated. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovationvr.com/ovation/creating-an-account/billing-1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.