Overview
Billing History is the detailed ledger behind the wallet summary. It shows transaction ID, type, description, date, amount direction, and status, with server-backed search, filters, and pagination.
- Find a transaction by identifier or search text.
- Filter by status and accounting category.
- Distinguish money entering and leaving the wallet.
- Collect evidence for billing support.
Before you start
- An owner or admin role, because wallet, subscriptions, payment methods, and renewal controls are restricted billing data.
- At least one connected bot when you want to select or change a per-bot plan.
- A supported card or cryptocurrency when adding funds.
Step by step
- Open Billing → History and note the total number of matching transactions.
- Use Search transactions when you have an ID, description, source, or other identifying text.
- Filter Status by Pending, Completed, or Failed to isolate incomplete payment flows.
- Filter Type by Deposit, Subscription, Paid media fees, or Adjustment to isolate the accounting category.
- Read the amount color and sign together with the type and status; a row can exist before its payment is complete.
- Use pagination for older entries and preserve the full transaction ID when escalating a mismatch.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Deposit category | Manual wallet top-ups, credit purchases, automatic recharges, and affiliate rewards are represented as incoming wallet activity. |
| Outgoing category | Bot subscription debits and applicable paid-media or legacy runtime charges reduce the wallet balance. |
| Status | Pending, Completed, and Failed describe settlement state; the existence of a row does not by itself prove funds moved successfully. |
| Adjustments | Administrative or manual corrections appear as adjustment entries rather than being hidden in the displayed balance. |
| Pagination | History loads a bounded page of results and provides navigation across older matching transactions. |
Verify the result
- The filtered row’s ID, type, date, direction, amount, and status match the event being investigated.
- A completed incoming row corresponds to the wallet increase shown in Overview.
- You have the full transaction ID and status before contacting support.
Troubleshooting
| If you see this | What to check |
|---|---|
| No row matches the search | Clear type and status filters, check the spelling or full ID, and navigate to older pages if the event is not recent. |
| The row is Pending for too long | Check the original card or blockchain payment and preserve its external reference before contacting support. |
| The displayed balance seems inconsistent | Compare completed incoming and outgoing rows around the affected time, then report the exact transaction IDs rather than only the current balance. |
Best practice
Use Billing as the source of truth for current prices, fee rates, thresholds, and plan availability; review History after every material payment or renewal change.