> For the complete documentation index, see [llms.txt](https://docs.apismart.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apismart.ai/account-and-wallet/view-your-balance-and-transaction-records.md).
# View Your Balance and Transaction Records
Learn how to check your ApiSmart wallet balance, review top-up and transaction records, and understand how API usage affects your available credits.
Use the ApiSmart Console to monitor your available wallet balance, review top-up and transaction activity, and understand how API usage affects your account credits.
This guide explains where to find your balance and how to distinguish wallet activity, payment records, and API usage costs.
***
### ๐ฐ Check Your Wallet Balance
Sign in to the **ApiSmart Console** and open **Wallet** to view your current available balance.
Your wallet balance represents the credits currently available for eligible ApiSmart services.
Your balance can change when you:
* Add funds to your wallet
* Receive bonus credits from an eligible top-up package
* Make billable API requests
* Receive an approved refund or account adjustment, where applicable
Before running production workloads, make sure your wallet has enough available balance for the models you plan to use.
> **Wallet balance and cash are not the same thing.**\
> ApiSmart wallet credits are digital service credits for use within the platform and are not withdrawable or exchangeable for cash.
For more information, see [**Add Funds and Understand Wallet Credits**](/account-and-wallet/add-funds-and-understand-wallet-credits.md).
***
### ๐งญ Wallet, My Orders, and Usage Logs
These sections serve different purposes:
| Console Section | What It Shows |
| --------------- | ------------------------------------------------- |
| **Wallet** | Your current available balance |
| **My Orders** | Recharge and payment records |
| **Usage Logs** | API requests, consumption, performance, and costs |
If you want to understand why your balance changed, you will usually need to compare **My Orders** with **Usage Logs**.
***
### ๐งพ Review Top-up and Order Records
Open:
**Token Packages โ My Orders**
to review recharge and payment records associated with your account.
Each order can include the following information:
| Field | Description |
| ---------------------- | ---------------------------------------- |
| **Order ID** | Unique identifier for the order |
| **Recharge Amount** | Recharge value associated with the order |
| **Actual Amount Paid** | Amount actually paid for the order |
| **Payment Method** | Payment method used |
| **Payment Status** | Current payment status |
| **Order Created At** | Date and time the order was created |
The **Recharge Amount** and **Actual Amount Paid** may be different depending on the package, discount, promotion, or payment arrangement associated with the order.
#### Filter Your Orders
You can search and filter order records by:
* Order ID
* Date range
* Payment status
* Payment method
If a payment has been completed but your balance does not appear as expected, first confirm that the order's **Payment Status** shows `Paid`.
Then check your Wallet to confirm whether the corresponding recharge value has been applied.
***
### ๐ Review API Usage and Costs
Open:
**Console โ Usage Logs**
to review requests made through your API credentials and understand how API activity affects your balance.
#### Usage Summary
At the top of the Usage Logs page, ApiSmart provides summary metrics including:
* **Total Cost ($)** โ Total API cost for the selected records or period
* **Total Tasks** โ Number of recorded API tasks
* **Avg Latency (ms)** โ Average request latency
* **Success Rate** โ Percentage of successful requests
These metrics provide a quick overview of API activity and performance.
#### Filter Usage Records
You can filter usage records using criteria such as:
* Date
* API Key Name
* Model Type
* Model Name
* Billing Mode
* Status
Use these filters when you need to investigate a specific API Key, model, billing method, or time period.
#### Usage Record Fields
Individual usage records can include:
| Field | Description |
| ----------------- | ------------------------------------- |
| **Request ID** | Unique identifier for the API request |
| **Time** | Time the request was recorded |
| **API Key Name** | API Key associated with the request |
| **Model** | Model used for the request |
| **Type** | Request or model type |
| **Billing Mode** | Billing method applied to the request |
| **Duration (ms)** | Request processing time |
| **Consumption** | Usage generated by the request |
| **Result** | Request result information |
| **Cost** | Amount charged for the request |
| **Status** | Request status |
> The Console may temporarily display **Token Name** while the platform terminology is being updated. In the documentation, API authentication credentials are referred to as **API Keys**.
#### Export Usage Records
The Usage Logs page also allows you to select and export usage records.
Exporting records can be useful for:
* Internal reporting
* Cost analysis
* Troubleshooting
* Comparing usage across models or API Keys
For more detailed information about this page, see [**Usage Logs and Costs**](/api-usage/usage-logs-and-costs.md).
***
### โก Understand Balance Deductions
Different models can use different billing methods.
Do not assume that every ApiSmart request is charged only by input and output tokens.
#### Text Models
Text models may be billed according to token usage.
Depending on the model, input and output tokens may use different pricing.
#### Image Models
Image generation may be billed according to the number of generated images successfully delivered.
The number of outputs generated by a request can therefore affect the final cost.
#### Video Models
Video models can use different billing methods depending on the selected model.
Billing may be affected by factors such as:
* Generated video duration
* Generated token usage
* Resolution
* Input type
* Model-specific pricing rules
For some video models, explicitly setting parameters such as `resolution` and `duration` is important because these values can directly affect billing.
For current model-specific billing information, see [**Model Pricing and Billing**](/models-and-pricing/model-pricing-and-billing.md).
***
### ๐ How Balance Changes Relate to Usage
A typical account flow looks like this:
1. **Add funds**\
Complete a recharge and create a payment order.
2. **Confirm the payment**\
Check **My Orders** and verify that the Payment Status is `Paid`.
3. **Credits become available**\
Review your available balance in **Wallet**.
4. **Send API requests**\
Your application uses an API Key to call supported models.
5. **Usage is calculated**\
ApiSmart calculates the applicable cost according to the selected model and billing mode.
6. **The balance is deducted**\
Billable usage is deducted from your available balance.
7. **Review the request**\
Open **Usage Logs** to see request-level consumption and cost information.
This means that your current wallet balance reflects both incoming recharge activity and outgoing API usage.
***
### ๐ If Your Balance Looks Incorrect
If your wallet balance does not match what you expected:
1. **Check My Orders**\
Confirm that recent recharges show `Payment Status: Paid`.
2. **Review Usage Logs**\
Check recent requests, especially **Model**, **Billing Mode**, **Consumption**, and **Cost**.
3. **Review Model Pricing**\
Different models and request parameters may use different billing methods.
4. **Check for Repeated Requests**\
Retries, duplicate requests, or automated workflows may increase usage.
If you still cannot explain the balance change, contact **ApiSmart Support** with the relevant **Order ID** or **Request ID**.
> Never provide your full API Key to support.
***
### ๐ Use the Console as Your Primary Reference
When reviewing balance changes or API costs, use the information displayed in the ApiSmart Console as your primary reference.
Keep in mind that:
* Different models may use different billing methods
* Model pricing may change over time
* Recharge packages and promotions may change
* Request parameters can affect final costs
* Failed and successful requests may be handled differently depending on the API and billing workflow
Always review [**Model Pricing and Billing**](/models-and-pricing/model-pricing-and-billing.md) before running large or production workloads.
***
### โก๏ธ Next Steps
Continue with:
* [**Add Funds and Understand Wallet Credits**](/account-and-wallet/add-funds-and-understand-wallet-credits.md) โ Learn how recharges and wallet credits work
* [**Model Pricing and Billing**](/models-and-pricing/model-pricing-and-billing.md) โ Understand model-specific billing methods
* [**Usage Logs and Costs**](/api-usage/usage-logs-and-costs.md) โ Review request-level usage and costs
* [**Create and Manage API Keys**](/welcome-to-apismart/api-keys/create-and-manage-api-keys.md) โ Manage credentials used for API requests
* [**HTTP Status Codes and API Errors**](/troubleshooting/http-status-codes-and-api-errors.md) โ Understand and troubleshoot API errors
