AI credit consumption and return records

How points change.Verification through the records.

Charges and returns have records, providing specific references for usage issues.

LDG-076Awaiting operational validation
See how to use it
Crop of Lingdonggu member point-transaction headers with time, account, type, change, description, and order-ID fields; no rows
Point-transaction fields· Real system screenshot

Only original headers remain. No balance, usage details, or order records are shown. Visible fields do not establish settlement acceptance and are not a per-task token report.

See this feature's highlights.

real work.
Details worth exploring.

Compare charges and returns.

Check charges or returns by time, account, type, and description; refer to the corresponding order ID when needed.

See the actual steps

Keep task context for verification.

For a disputed use, submit a review request with its timing and task context.

See how to check

Locate the time first.
Compare charges and returns.

Charges and returns have records, providing specific references for usage issues.

This feature's focushas a record

Point transactions give usage issues specific references

How the feature works. Actual results depend on information, permissions, and service requirements.

When to use it

Prepare first.
Make this task specific.

When AI usage raises questions about charges or refunds, trace the credit history to the specific time and description.

01

Record evidence

time, type and explanation in membership usage history.

02

Investigation context

the related task, account and order number when needed.

Complete steps

From the start.
To the next step.

View AI credit transactions in member usage records. Check dates, consumption or returns, explanations and linked orders. Task-level Token reports are not a general member page. Submit the task context to investigate usage issues.

01

View AI point transactions in the membership center.

02

Check charges or returns by time, account, type, and description; refer to the corresponding order ID when needed.

03

For a disputed use, submit a review request with its timing and task context.

Understand the tool and human handling separately

What the tool handles.
What you decide.

Feature assistance

Locate the time first.

Charges and returns have records, providing specific references for usage issues.

Check charges or returns by time, account, type, and description; refer to the corresponding order ID when needed.

Your review

3 key points.
After confirmation, continue.

  1. Review charges and refunds separately.
  2. Ordinary membership history is not an internal task-level token report.
  3. Exception handling follows actual rules and operational acceptance results.

This compares feature handling scopes. Scenarios explain the sequence, not measured efficiency or completed customer cases.

Explain the feature through real work

This time.
Verification.

Suppose a user questions a credit change.

Hypothetical scenario · Feature explanation, not a customer case or completed AI result
Previous handling steps

Look only at the current balance, making the event difficult to explain.

With this feature

Check the history's time, explanation and task context before raising a specific question.

Connect the work from step to step

Make this step clear.
Connect the next step.

Provide relevant record references for investigation. The corresponding process confirms actual charges, refunds or exceptions.

Return to Accounts and team workspace for the complete workflow

Understand before use

Bring the actual conditions.
Continue this step of the work.

The standard member page shows point transactions. Per-task tokens and settlement status are internal-management information. Charges, returns, and exception handling follow actual rules and operational acceptance results.

Product facts and FAQsBack to the product feature directory

More details in this product

Order, payment and refund records

Check order-related work by records and statuses separately.

Explore this feature on its own