> For the complete documentation index, see [llms.txt](https://showreward.gitbook.io/showreward-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://showreward.gitbook.io/showreward-docs/getting-started/billing.md).

# Understand ShowReward billing

ShowReward usage charges and participant rewards are separate costs. Check the base rate and billing mode shown for your project; your GoHighLevel agency may add its own markup.

## View your project's billing

1. Select your project and open **Settings**.
2. Find **ShowReward billing**.
3. Review the displayed billing mode and base rate.
4. Click **View usage** to open the project's history. Administrators may see **Manage billing** instead.
5. Use **Refresh** to request the latest history.

Project managers can view usage. Only a ShowReward administrator can change the project's billing mode. Closers do not manage billing.

## What counts as a new lead?

For usage billing, a lead is unique within a project by normalized email address. A reschedule, another appointment, a repeated import, or another campaign for that same lead in the same project does not add another lead unit. The same person in two different projects can count once in each project.

A project marked exempt does not incur new ShowReward usage charges. Enabling usage billing applies to new registrations from activation; it does not retroactively charge leads registered while the project was exempt. Changing a project to exempt does not automatically refund charges already submitted or charged.

## Read the usage status

| Status              | Meaning                                                                                             |
| ------------------- | --------------------------------------------------------------------------------------------------- |
| Pending             | The usage record is waiting to be processed.                                                        |
| Processing          | A charge attempt is being processed.                                                                |
| Awaiting resolution | An issue needs to be resolved before the record can proceed. Read the explanation below the status. |
| Confirming with GHL | ShowReward is checking an uncertain result with GoHighLevel.                                        |
| Charged             | The charge has been confirmed.                                                                      |
| Exempt              | No charge applies to this record.                                                                   |
| Refunded            | A refund was detected for the recorded charge.                                                      |

Pending amounts are estimates. The history shows ShowReward usage for the selected project; it is not your agency's complete GoHighLevel invoice. The net total below the table applies to the displayed page of records.

## Resolve a billing notice

Follow the notice shown in the dialog. Common issues include a missing connection, billing permissions requiring reauthorization, insufficient GoHighLevel funds, or account limits. Ask the administrator to review account conflicts or a changed billing account.

A lead registered before an eligible GoHighLevel connection is established is not automatically charged to an account connected later. Reauthorizing billing permissions for the same existing connection is different: the dialog may explain that new pending leads will be charged after reauthorization.

Availability depends on your installed ShowReward version, GoHighLevel permissions, and billing setup. Use the status shown for your project to confirm readiness.


---

# 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://showreward.gitbook.io/showreward-docs/getting-started/billing.md?ask=<question>&goal=<user_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.