> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amlok.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand balance, payments and consumption

> Review workspace credits, configure simulated autopay, manage payment methods and reconcile funding, charges and statements.

Owners use **Billing** to understand what was funded and how credits were consumed. Each workspace environment has a CAD balance shared by Insights and Signal. The organization owns the billing profile.

Sandbox uses simulated credits and payment records. It never charges a real card, debits a bank account or transfers funds. Screenshots in this guide show the demonstration dataset.

## Read the billing overview

Open workspace settings and select **Billing**. Confirm the workspace and environment, then review:

* **Balance:** the available amount in the selected environment.
* **Low balance threshold:** the configured level used to identify a low balance.
* **Autopay:** whether automatic recharge is enabled and its configured amount and trigger.
* **Organization billing profile:** the legal name and billing contact for the organization.

![Sandbox Billing overview showing simulated balance, enabled autopay, organization billing profile and payment-methods section.](https://mintcdn.com/amlok-docs/HXjKmnxFg9L3P2cw/images/console/billing.jpg?fit=max\&auto=format\&n=HXjKmnxFg9L3P2cw\&q=85\&s=3672e2f142954d03761c204a9d6f8488)

Billing combines the workspace balance and autopay with the organization profile and payment methods.

Use **Edit threshold** or **Edit profile** to update the corresponding setting. Complete the identity confirmation when requested.

## Configure autopay in Sandbox

**1. Add a simulated payment method**

In **Payment methods**, select **Add payment method**. Choose **Credit card** or **ACH bank account** and enter a display name. Sandbox does not need real card or bank details.

**2. Open Configure autopay**

Turn on **Enable autopay**. Enter the balance level below which a recharge should be triggered.

**3. Choose a recharge amount and method**

Select a displayed preset or **Custom**, then choose the payment method. Review the summary showing both the trigger and the amount to add.

**4. Confirm and save**

Complete identity confirmation and select **Save autopay**. Return to the overview to confirm the saved configuration. To stop future automatic recharges, switch autopay off and save.

![Autopay drawer with enable switch, CAD threshold, preset or custom recharge amount, payment method and confirmation controls.](https://mintcdn.com/amlok-docs/HXjKmnxFg9L3P2cw/images/console/autopay.jpg?fit=max\&auto=format\&n=HXjKmnxFg9L3P2cw\&q=85\&s=76efde73b478e3d56c5c2271268bc1ed)

The trigger balance and recharge amount are separate settings. This example uses only simulated funds.

Disabling autopay preserves the saved amount and method configuration. It does not reverse previously posted activity. Use the [financial Sandbox scenarios](https://docs.amlok.io/sandbox/simulated-billing.md) to inspect payment outcomes and resulting records.

Live funding options depend on your account's activation and configured payment facilities. If a Live payment control is unavailable, contact [support@amlok.io](mailto:support@amlok.io). Follow your [billing agreement](https://docs.amlok.io/pricing/credits-and-billing.md); Sandbox presets do not replace contractual funding requirements.

## Manage payment methods

Payment methods belong to the organization and environment and can be used by its workspaces. Open a record to inspect it or use its actions to rename it, make it the default or remove it.

**Set as default** changes the method suggested for new autopay configuration. Existing autopay configurations keep their selected method. Removing a method disables autopay for every workspace using that method; historical transactions remain available.

## Reconcile funding and charges

| View | What it answers |
| - | - |
| **Funding history** | What payments or funding attempts were made, and what happened to them? |
| **Transaction history** in Billing | Which credits, product debits, refunds or adjustments were posted to the wallet? |
| **Consumption** in Reporting | Which Insights or Signal usage generated charges? |
| **Statements** | What was recorded for a statement period and revision? |
| **Workload** in Reporting | How much processing occurred, independently of financial charges? |

Pending or failed funding is not available credit. A payment record and a posted wallet credit represent different stages, so do not add both as separate deposits. Compare currency, amount, status, period and related identifiers when reconciling a payment, ledger entry, consumption record and statement.

Historical transactions and statement snapshots are records of what was posted. Corrections appear as linked activity or revised statements rather than silent edits. API request counts are not the billable unit for Insights or Signal.

See [Reporting](https://docs.amlok.io/console/reporting.md), [credit reporting](https://docs.amlok.io/api-reference/credit-reporting.md) and [consumption reporting](https://docs.amlok.io/api-reference/consumption-reporting.md) for downstream reconciliation. Commercial cancellation and refund terms are covered in [contract terms](https://docs.amlok.io/pricing/contract-terms.md) and [refunds and payouts](https://docs.amlok.io/pricing/refunds-and-payouts.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.