Buyer Flow

◉Canonical

---

Purpose

Buyer flow must make purchase decisions clear and safe.

Workflow

1. Buyer discovers a listing.
2. Buyer reviews details, seller status, included and excluded items, price, accepted assets, delivery terms, refund policy, disclosures, and support path.
3. Buyer starts checkout and confirms payment method.
4. Discounts or credits are applied if eligible and approved.
5. Buyer approves or signs a transaction if crypto payment is used.
6. Payment is processed and an order is created.
7. Access or delivery starts.
8. Buyer accepts delivery, completes the course, opens support, or starts a dispute if policy allows.
9. Settlement proceeds under the order terms.

Order Fields

Order fields may include order ID, buyer reference, listing ID, seller ID, order status, payment status, delivery status, settlement status, refund status, dispute status, price, payment asset, credits used, discounts, fees, creation time, and completion time.

Order Statuses

Statuses may include Created, Awaiting Payment, Paid, In Delivery, Delivered, Completed, Cancelled, Refunded, Disputed, and Failed.

Buyer Protection Requirements

Listings should expose seller status, price, fees, refund policy, delivery model, risk disclosures, support path, and transaction summary before payment. Outcomes depend on listing terms and are not guaranteed.

Buyer Decision Flow

1. The buyer identifies a listing and reviews provider, status, scope, price or quote basis, delivery terms, and risks.
2. Eligibility and availability are checked in the applicable context.
3. Custom or ambiguous work routes to Business before commitment.
4. Any payment or credit step routes through an authorized settlement surface.
5. Delivery and acceptance are recorded.
6. A mismatch routes to support or dispute handling.

No step implies that listings, checkout, payments, refunds, credits, or settlement are currently enabled. A buyer-facing interface must fail closed when status, authority, or payment evidence is unavailable.