What should I save for a Texas prediction-market dispute?

Save the contract or market name, exact event wording, platform terms, fee schedule, settlement source, order or contract status, support ticket, account-state prompt, timestamp and tax-record wording after removing private data.

Does this checklist prove a sports event contract is legal sports betting in Texas?

No. This checklist preserves evidence. It does not decide Texas sports-betting legality, platform suitability, payout approval, tax classification or consumer recourse.

What private data should not be included?

Do not include private account numbers, SSN, ID images, bank data, card data, passwords, seed phrases, private keys or private medical data.

Texas prediction-market child asset

Texas Prediction Markets Evidence Checklist: Contracts, Fees and Settlement

Use this checklist before you rely on a Texas-facing sports event contract, Kalshi-style market, FanDuel Predicts-style claim, Polymarket-style market, Crypto.com event-contract route or generic prediction-market shortcut.

Scope: this page preserves evidence. It does not decide Texas sports-betting legality, CFTC status, payout approval, tax classification, financial suitability or whether you should trade.

Reviewed: Michael JohnsonResearch editor: Sarah RobertsSource routes checked: May 23, 2026

Quick evidence checklist

Back to guide

Contract

Market identity

Save contract name, market URL, event wording, platform surface, timestamp and account-state prompt.

Settlement

Resolution source

Save the official source named in rules, result screen, settlement rule and support wording.

Fees

Cost and payout trail

Save fee schedule, matched order, contract count, price, withdrawal status and support route.

Private

Redact before sharing

Remove private account, SSN, bank, card, ID image, password, seed phrase, private key and medical data.

Full Texas event-contract field checklist

This is the indexable checklist version of the packet. Use it before a dispute, tax-record question or source-status claim.
Field	What to save	Why it matters
Contract / market name	Exact event and outcome wording.	Similar sports markets can settle on different wording.
Platform / app	Domain, app surface, PWA, email or ad route.	Platform access is not source ownership or approval.
Federal source wording	CFTC, exchange, FCM, NFA, derivatives or risk-disclosure language.	Federal market structure is separate from Texas sportsbook status.
Texas claim	"Legal in Texas", "sports betting", "not sportsbook", "available in Texas" or state-eligibility wording.	These are claim patterns, not proof by themselves.
Fees	Fee schedule, spread, commission, entry price, exit price and withdrawal/payment fee wording.	The contract price is not always the full cost trail.
Settlement source	Who resolves the market outcome and where that rule appears.	Resolution source controls many settlement disputes.
Support route	Official support URL, ticket path, date and public-safe reply.	Off-channel support can become a scam or evidence gap.
Account state	Texas, travel, geolocation or out-of-state context shown by the platform.	Location/account context can change the correct Texas route.
Funding method	Card, bank, crypto, wallet or payment-method category only.	Payment rail is not legal approval or tax classification.
Tax / dispute wording	Statements, forms, fee records, settlement records and support notes.	Records come before tax interpretation or dispute escalation.
Pressure signal	Chasing, urgency, repeated funding, secrecy or loss-recovery prompts.	Support routes come before tools or platform comparison.

Prediction-market packet fields

CSV packet

Use these fields before support, tax, settlement or status questions.
Field	Save	Do not save publicly	Correct route
Contract or market name	Public market label and event wording.	Private account identifiers.	Prediction-market guide
Contract ID / order ID	Only if it can be redacted or is safe to share.	Full account number, transaction account or login details.	Support evidence
Settlement source	Official source named in the contract rules.	Private messages with personal details.	Settlement decoder
Fees and funding	Fee wording, funding method category and withdrawal status.	Card, bank, wallet seed phrase, private key or exchange account ID.	Payout/tax records
Texas/source wording	Exact "Texas", "legal", "available" or "not betting" claim.	Personal location data beyond state-level prompt.	Texas laws
Support trail	Ticket path, public-safe reply, date and issue category.	ID images, SSN, passwords, bank/card data or private medical data.	Scams/support

Settlement status checklist

Status wording tells you what evidence to preserve next.
Status	Evidence	Risk	Route
Market open	Market URL, event wording, fee and settlement rule.	Reading visible access as Texas approval.	Texas laws
Order matched	Order/contract status, price, quantity, fee and timestamp.	Treating matched order as payout certainty.	Evidence packet
Event resolved	Resolution source, result screen and final settlement wording.	Result mismatch or unclear source.	Support evidence
Settlement pending	Status screen, support ticket and expected timing language.	Support delay or account review.	Payout tools
Disputed resolution	Original rules, result screen, support reply and timestamp.	Source conflict or support ownership issue.	Scams/support
Withdrawal pending	Request ID, KYC wording, method, support response and date.	Cashier, KYC or payment-rail delay.	Fast payout

Public-safe support message

Use only after removing private identifiers, account numbers, ID images, bank/card data and private medical data.

I am checking a Texas-facing prediction-market or sports event contract issue. The public market/contract wording I saw was: [exact wording]. The platform surface was: [website/app/email]. The issue is: [market open / order matched / contract held / event resolved / settlement pending / disputed resolution / withdrawal pending]. Please confirm the official contract rules, fee schedule, settlement or resolution source, support ticket path and whether this is a platform support issue, settlement issue, account review, KYC/payment issue or state-eligibility issue. I will not send SSN, card, bank, account password, seed phrase, private key, private medical data or ID images through off-channel support.

Download packet routes

JSON

Evidence packet JSON

Structured fields for contract, fees, settlement, support and tax-record status.

TXT

Plain text packet

Copyable public-safe checklist for support and records.

CSV

CSV packet

Spreadsheet-ready packet fields.

Next routes

Status

Texas prediction markets Parent source guide.
Texas sports betting Sportsbook, DFS, offshore and travel boundary.
Texas laws Product-lane status and state source ownership.

Records

Texas tax records Records before tax interpretation.
Payout tools Settlement, support and withdrawal status.
Sports tools Use only after source and pressure checks.

Support

Responsible gambling Texas Chasing, urgency, secrecy or repeated funding.
Texas scams Fake support, recovery, tax-release or payment demands.
Fast payout KYC, request ID and withdrawal delay records.

Checklist quick answers

Does this checklist prove legality?

No. It preserves public-safe evidence. Use Texas laws and CFTC/source routes separately.

Should I include my ID or bank details?

No. Redact account numbers, SSN, bank, card, ID images, passwords, seed phrases, private keys and medical data.

What if settlement is pending?

Save the contract, status screen, support ticket, settlement rule and timestamp before opening payout/support routes.

What if I feel pressure to keep trading?

Use 1-800-MY-RESET and Texas responsible-gambling routes before another funding step.

Changelog

May 23, 2026

Created indexable Texas prediction-market evidence checklist with contract ID, market wording, settlement source, fees, support ticket, account-state, tax-record and private-data warning routes.