Higgsfield Refund Case · Visual Course

Ledger and consumption

Define the technical proof that separates general activity from purchased-lot consumption.

Primary source

Redacted dossier — “Usage and subscription”

What this source supports: There are 648.5 credits of July 4 activity, but entries omit the source wallet.

The simple layer stands alone; open the technical layer for limits and objections.

The big idea

By the end, you can

Specify minimum ledger fields
Separate general use from top-up use
Formulate an allocation test

History records 648.5 credits of general activity on July 4. That does not answer whether debits came from the monthly plan or the extra purchase. A useful ledger must show each event, source wallet, and priority policy.

Think of it as… a statement that shows only “−20” without naming the account. The total reconciles, but the dispute remains unanswered.

Under the hood

Minimum fields are timestamp, event, quantity, wallet_id or wallet_type, lot, applied rule, and balances before/after. Support can provide a redacted allocation without exposing operational secrets.

Visual map

Read left to right: each stage limits what the next may claim.

The case becomes stronger when the evidence boundary stays visible.

Timestamp

Event ID

Quantity

Wallet type

Lot

Priority

Before

After

Monthly

Top-up

Safe redaction

Reconcile

General usage

648.5 credits

Top-up usage

Undetermined

In practice

This record turns the reasoning into verifiable fields without personal identifiers.

Structured case record

{
  "event_time": "redacted",
  "credits": 12.5,
  "wallet_type": "monthly | top_up",
  "lot": "redacted",
  "balance_before": "required",
  "balance_after": "required"
}

How to verify

Use ../../dossie-reembolso-higgsfield.md to verify totals; request missing fields from support.

Worked example

1List all July 4 events.

2Assign wallet_type to each debit.

3Sum top-up debits only and reconcile the balance.

Try it

Commit before reveal

Is a total-usage number enough to audit the purchased wallet?

No. Each debit must be attributed to a wallet or lot.

Commit before revealLedger↻

Reveal answerChronological record of debits, origin, and balances.

Commit before revealAllocation↻

Reveal answerLink between a usage event and the debited wallet.

Commit before revealReconciliation↻

Reveal answerCheck that inputs, debits, and ending balance agree.

Active review

Answer both questions; the score updates automatically.

648.5 credits represent:

The total records activity; accounting origin is not exposed.

Which field is decisive?

Wallet type attributes the debit; feature name does not resolve origin.

Sources and traceability

RESOURCES.md

Higgsfield Terms of Use

§ 9.3 · § 9.4

Brazilian Consumer Code

Official source · context, not automatic conclusion

Use what you learned to review the request and seek professional guidance if legal or banking consequences matter. With technical proof defined, build a concise and verifiable full-refund request.