Dispute evidence
Review how order snapshots, delivery proof, refund review, seller holds, chargeback readiness, hub evidence, customer notices, and approval steps can be organized before payment services are connected.
Order Snapshot
- Dispute review should begin with the item title, listing photos, order number, seller, buyer, price, fees, handoff method, and protection status.
- The snapshot should preserve the listing state as it appeared when the buyer committed.
- Support review needs one place to compare the listing promise against delivered or released evidence.
Delivery Proof
- Delivery proof should include carrier scans, hub pickup release, QR confirmation, pickup window, package photos, and buyer receipt status.
- Local pickup needs a clean record of scheduled window, release code, counter action, and no-show history.
- Shipment cases need tracking, insurance, declared value, packing notes, and damage photos.
Refund Review
- Refund review should separate item price, shipping, hub service lines, insurance, taxes, credits, and seller-release impact.
- Support outcomes should show whether the buyer receives account credit, original-tender refund, partial refund, replacement path, or no refund.
- Customers should see the evidence still needed before a decision can be made.
Seller Holds
- Seller holds should connect to open reports, delivery issues, chargeback risk, item authenticity, restricted-item review, and proceeds readiness.
- Sellers need a clear explanation, evidence request, expected review timing, and appeal path.
- Hold history should stay available for finance review and seller statements.
Payment Dispute Packet
- Payment dispute packets should package order snapshot, listing proof, delivery proof, communication history, refund history, and review decisions.
- Review owners need deadline tracking, reason codes, evidence completeness, and outcome records.
- Customer-facing copy should stay focused on the dispute outcome rather than payment-network terminology.
Hub Evidence
- Hub evidence can include intake photos, condition notes, accessory counts, serial proof, certificate checks, packing photos, and pickup release records.
- Hub notes should help separate shipping damage, pickup mismatch, seller description issues, and buyer misunderstanding.
- Only approved reviewers should see private custody notes.
Customer Notices
- Buyer and seller notices should explain what happened, what evidence is needed, who owns the next step, and when the next update is expected.
- Notices should be consistent across order status, support case, email-ready templates, and account inbox.
- Private notes and finance details should stay out of public pages and customer messages.
Approval Steps
- Approval steps should connect dispute outcomes to receipts, seller statements, settlement review, credits, refund reserves, and release status.
- Owners need clear approval for refund authority, chargeback evidence handling, seller hold rules, retained records, and exports.
- The demo does not process payments, issue refunds, or release seller funds.
Purchase Protection
Issue windows, evidence checklists, seller response, hub proof, return status, and refund review.
Resolution Center
Missing items, condition issues, seller response, hub proof, outcome paths, and appeal history.
Returns & Refunds
Eligibility, evidence, seller response, refund holds, credit routing, and outcome paths.
Seller Disputes
Seller proof, buyer evidence, hub records, refund exposure, response timing, and appeal paths.
Insurance & Claims
Declared value, damage review, hub custody exceptions, pickup release issues, and evidence packets.
Payment Readiness
Authorization, credits, seller releases, refunds, dispute packets, tax readiness, and approval ownership.
Payment Disputes
Evidence packets, refund reserves, seller holds, buyer notices, review ownership, and owner approval.
Settlement Ledger
Order value, hold reasons, refund impact, seller release status, and finance review.
Seller Protection
Buyer abuse, return swaps, seller release holds, pickup disputes, evidence packets, and owner approval.
Current demo state
Dispute evidence is represented as review packets.
The demo shows order snapshots, delivery proof, refund review, seller holds, payment dispute packets, hub evidence, customer notices, and approval steps as static review paths. It does not process payments, issue refunds, store payment methods, release seller funds, or collect private financial details.
Future platform state
Launch disputes need payment-provider rules and clear ownership.
A launched marketplace needs provider workflows, refund authority, deadline tracking, retained evidence, role permissions, seller hold rules, customer notices, reconciliation, exports, and owner approval before payment disputes affect real funds.