Loading dispute workspace
Gather every proof source, build a defensible package, keep an internal archive, and never miss the submission window.
Square dispute facts, recommendation, package state, and submission controls.
No package built yet. Rebuild evidence to create one.
Submissions remain blocked until the package is approved and all cited assets are usable.
Focus on cancellation timing, policy acceptance, and whether a refund or return offer was already made.
No active gaps detected in the latest package.
Immutable commerce context linked to this dispute.
This case has not been linked to a Shopify order yet.
Every item remains archived internally regardless of what gets uploaded to Square.
Use the manual asset endpoint or inbound webhooks to add evidence.
Each rebuild creates a new immutable version before submission.
Build the first evidence package to start versioning.
Every fetch, review, package build, and submission is recorded.
Synced dispute state EVIDENCE_REQUIRED from Square history import.
Imported existing Square dispute in state EVIDENCE_REQUIRED.