> For the complete documentation index, see [llms.txt](https://docs.pravatherapy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pravatherapy.com/client-billing.md).
# Client Billing
If a client has any costs they owe for a session, we will automatically charge their credit card on file *after* we get a confirmation from insurance. We wait until insurance has confirmed the charges to avoid unnecessary confusion/refunds/additional charges if the cost doesn’t match what insurance told us during the benefits review process (which does happen from time to time). The processing times vary payer by payer but are typically about 3 weeks after the session. After charging we sent out a detailed receipt to the billing email on file for the client.
You can see an example receipt here: [ExampleClientInvoice.pdf](https://drive.google.com/file/d/1UUNBT8GrExBokgGcDSTy92ILTpv2YxhF/view?usp=sharing).
If we don’t have a credit card on file, we will send out an invoice to the client’s billing email that has a link to pay online or instructions to mail us a check.
## How a client can update their own payment information
They can log into their account via [pravatherapy.gethealthie.com](http://pravatherapy.gethealthie.com) and go to “Settings > Update payment information”.
## Updating a Client’s Payment Information
If you need to update the credit card a client has on file with us you can do so via the Client’s profile on either the web or the mobile app.
### Mobile
### Web
---
# 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.pravatherapy.com/client-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.