> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/administration/billing-and-usage.md).

# Billing & Usage

Use Billing & Usage to review the current plan, credit balance, credit activity, daily consumption, and approved Stripe billing actions.

## Quick answer

Open **Settings → Billing & Usage** to review the plan and payment card, credit balance, credit history, activity, and daily usage. Days with zero consumption are labeled **No credits used**. When execution cannot start because the organization has no credits, ContextQA explains the condition and directs an authorized administrator to Billing instead of presenting it as transient demand.

## What this page covers

{% hint style="info" %}
**Who is this for?** Workspace owners and super administrators responsible for subscription access, credits, and consumption review.
{% endhint %}

{% hint style="warning" %}
The page is rollout- and permission-dependent. If **Billing & Usage** is absent, confirm that you are a super administrator in an eligible workspace before contacting support.
{% endhint %}

## How billing and usage fit together

```mermaid
flowchart LR
    A[Workspace plan] --> B[Credit balance]
    B --> C[ContextQA actions consume credits]
    C --> D[Usage summary and daily chart]
    C --> E[Activity ledger]
    A --> F[Secure Stripe billing flow]
    F --> B
    D --> G[Administrator reviews trend]
    E --> G
```

This page reports the account and usage information available to the workspace. Use the underlying run or activity record when you need to investigate a specific automation outcome.

## Open Billing & Usage

1. Open **Settings**.
2. Select **Billing & Usage**.
3. Confirm that the organization or workspace shown is the one you intend to review.
4. Use the **Billing** and **Usage** tabs for the appropriate task.

## Billing tab

The **Billing** tab can show:

* a combined plan and payment card;
* a credits card with the available balance and clear loading or unavailable states;
* plans available to the workspace;
* a control to add or update payment through Stripe;
* a control to manage supported subscription actions through Stripe; and
* credit history or recent credit activity.

If a subscription is scheduled to end and the billing arrangement can be resumed, the plan card can show **Resubscribe**. Follow that action to the supported Stripe flow, then return to ContextQA and verify the resulting plan state.

When you select an available payment or management action, ContextQA redirects the current tab to a Stripe-hosted page. Verify the Stripe domain and the ContextQA organization before entering payment information. Return to ContextQA after completion and confirm that the plan or balance reflects the intended change.

The page refresh changes presentation rather than the meaning of the underlying billing workflow. Use the current plan, balance, and Stripe result as the source of truth; do not infer a successful purchase from the presence of the redirect screen alone.

{% hint style="info" %}
The exact actions in the Stripe portal depend on the current plan and billing arrangement. If the action you need is not available, contact the workspace owner or ContextQA support rather than attempting a workaround.
{% endhint %}

## Usage tab

Use the **Usage** tab to understand how the workspace is consuming credits. Depending on the current view, it can include:

| View                                  | Use it to answer                                    |
| ------------------------------------- | --------------------------------------------------- |
| Usage summary                         | How much activity occurred in the selected period?  |
| Daily usage chart                     | On which days did consumption increase or decrease? |
| Activity ledger                       | Which recorded actions added or consumed credits?   |
| By-action view                        | Which categories account for the observed usage?    |
| Date, user, source, or action filters | Which subset should an administrator investigate?   |

Activity timestamps are displayed in the user's local time. Record the selected date range and filters when sharing a usage finding so another administrator can reproduce the view.

A day labeled **No credits used** means the daily chart recorded zero consumed credits. It does not prove that nobody opened the workspace or performed a non-billable action.

## When a run cannot start because credits are exhausted

ContextQA shows **You're out of credits** when a new execution session is rejected because the organization has no usable credits. The available recovery depends on your role:

* an authorized billing administrator can open **Manage billing** and review the plan or credits;
* another user is directed to contact the organization administrator.

Retrying the same run does not add credits. Resolve the billing state first, then start a new execution and preserve its new run ID as the evidence record.

## Investigate unexpected usage

1. Confirm the workspace, date range, and local timezone.
2. Compare the summary with the daily chart to locate the change window.
3. Filter the activity ledger by action, user, or source when those filters are available.
4. Open the related execution or platform record for operational evidence.
5. Preserve non-sensitive IDs, timestamps, and filter settings before contacting support.

Do not infer that a test passed, failed, or produced a defect from credit consumption alone. Billing records describe usage; execution results describe test outcomes.

## Common questions

<details>

<summary>Why can I not see Billing &#x26; Usage?</summary>

The page is currently restricted to super administrators in eligible workspaces. Ask a workspace owner to confirm your role and the organization's rollout status.

</details>

<details>

<summary>Where do I enter payment details?</summary>

Use the payment action on the **Billing** tab. ContextQA redirects you to a secure Stripe-hosted page. Do not enter card details into a test case, environment variable, support message, or other ContextQA text field.

</details>

<details>

<summary>Can I download invoices from this page?</summary>

A general invoice list is not part of the current ContextQA Billing & Usage page. Use the billing actions made available through Stripe or contact the account owner for the applicable invoice workflow.

</details>

<details>

<summary>Why does the ledger not prove which test failed?</summary>

The ledger records account activity and credit movement. Open the associated run in ContextQA reporting to inspect status, steps, screenshots, video, logs, and failure analysis.

</details>

## Related documentation

* [Administration Overview](/administration/administration.md)
* [Roles & Permissions](/administration/roles-and-permissions.md)
* [License Status and Expiry](/administration/license-status.md)
* [Reporting Overview](/reporting/reporting.md)
* [Execution History](/reporting/execution-history.md)

{% hint style="info" %}
**Need a usage and governance walkthrough?** [**Book a Demo →**](https://contextqa.com/book-a-demo/?utm_source=learning.contextqa.com\&utm_medium=referral\&utm_campaign=docs_demand_gen\&utm_content=billing_usage) — Review workspace controls, execution evidence, and usage visibility with your team.
{% endhint %}


---

# 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://learning.contextqa.com/administration/billing-and-usage.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.