Inventory intake
PSA slab data, photos, custody location, and exception notes are captured before a card can enter active supply.
Every card has a known owner, bin, snapshot, and lifecycle state.
General team
Operate the full PSA rip lifecycle.
This is the high-level process map for people making decisions across product, ops, legal, support, design, and launch. It explains what happens, what must be visible, and where the team has to be careful.
- Process lanes6
- Customer outcomes3
- Trust modelProof + custody
01 / Process map
Every team should be able to trace a slab from intake to outcome.
Wave publish
A public pool goes live with fixed card contents, deadline, odds language, and rules customers can inspect.
No silent replenishment; pulled and remaining cards stay understandable.
Checkout
A verified customer buys packs with store credit first, then card payment for the remaining balance.
Payment, eligibility, fraud, and pack quantity rules are resolved before queueing.
Draw and proof
Openings run in order from a queue using external randomness and a deterministic draw algorithm.
Proof can be replayed from wave state, randomness, algorithm version, and selected cards.
Reveal
Customers see pulled cards with proof, source context, and enough detail to understand value and rarity.
Reveal supports one-by-one, fast reveal, mute, reduced motion, and shareable results.
Resolve
Each pulled card moves to delivery, store-credit buyback, or a decide-later state with deadlines.
The customer always knows the active choice, value basis, and next action.
02 / Trust model
Trust is made from visible state, not internal promises.
PromiseCustomer seesTeam checks
The card exists
PSA cert, slab image, declared condition, and public history.
Custody scan, bin location, ownership state, and intake snapshot.
The pool is fixed
Wave contents, pulled cards, remaining cards, deadline, and RIPPED labels.
Publish lock, no hidden edits, exception path for live wave incidents.
The draw is replayable
Opening proof, randomness source, selected cards, and visible result.
Provider contract, algorithm version, queue order, and verifier replay.
The outcome is clear
Deliver, buy back, or decide later with value and deadline.
Credit ledger, fulfillment state, support notes, and dispute trail.
03 / Customer loop
The simple story is browse, buy, reveal, resolve.
- Browse a live wave
- Buy packs
- Wait in the queue
- Reveal pulled slabs
- Choose delivery or buyback
- Track follow-up
Deliver
The slab leaves active inventory, gets a validated address, label, insurance/signature rules when needed, and tracking.
Buyback
The customer accepts store credit based on a confidence-aware offer. The slab can re-enter supply only after review rules pass.
Decide later
The customer keeps a temporary unresolved state with a clear deadline, reminders, and an automatic fallback policy.
04 / Operations surface
Back-office work is part of the customer promise.
Pricing and buyback
Market data produces confidence-aware buyback offers. Low-confidence or high-value cards require manual review before customers see final numbers.
Delivery and fulfillment
Address validation, carrier rates, labels, insurance, signature rules, and tracking turn resolved slabs into shipped orders.
Support and risk
Support needs read-only context for payments, openings, proofs, card status, disputes, fraud signals, and admin decisions.
Admin controls
Trust-critical actions need permissions, reason notes, audit history, and second approval when value or risk is high.
05 / Launch readiness
Mainnet launch needs gates, not vibes.
These are the areas the general team should track before public MVP. Each gate should have an owner, evidence, and a launch/no-launch decision.
- Legal framing: sweepstakes/gambling posture, terms, age, tax, and jurisdiction.
- Provider readiness: payments, randomness, PSA data, shipping, pricing, email.
- Quality bar: verifier replay, E2E flows, accessibility, visual regression, load, and security.
- Operations readiness: inventory audit, admin approvals, support scripts, incident handling.