Build a Reproducible LevelUp Complaint File

Identify the service

Save the exact hostname, account username, operator or contracting entity shown in the terms, and any licence claim. Similar brand pages should not be treated as the same business without matching details.

Preserve the terms version and payment descriptor that applied when the disputed action occurred.

• Domain
• Legal entity
• Licence claim
• Terms date

Create a one-page chronology

List deposit, wager, verification, withdrawal and support events in order with IDs and timestamps. Link each event to a numbered screenshot or statement entry.

Redact unrelated personal information while leaving the fields needed to match the account and transaction.

• Account event
• Reference ID
• Evidence number
• Operator response

State one requested resolution

Ask for a specific action: explain a rejection, correct a balance, release an approved payment, close an account or confirm a protective restriction.

Do not combine a card dispute, bonus complaint and self-exclusion request into one unstructured message. Protective action should be raised immediately and separately.

Route the complaint by issue

Use the operator's formal process first for account decisions. A bank handles unauthorised card or transfer events; Australian authorities address matters within their own jurisdiction.

Keep every case number and referral. Close the file only after a reasoned decision or reconciled account event, not an automated receipt.

LevelUp account questions