‹ SQOOT Pure Hub
SQOOT PURE

SQOOT Pure — Coin Purchase MVP: Design & Requirements (v1)

Owner: Jay (Founder) · Entity: Fortress Gold Inc. dba SQOOT Pure · Created: June 3, 2026 Phase: Design + requirements (Phase 1 of: Design → Prototype → Payments → Full Architecture)


0. Assumptions (correct any — they shape everything below)

  1. Deliverable now = this written design + requirements brief. Interactive prototype comes next.
  2. “Allow only 20” = a hard cap of 20 coins per order (any mix of sizes). Used as both an MVP simplifier and a compliance guardrail. (If “20” meant a dollar threshold or ~20 screens, tell me and I’ll re-scope.)
  3. Architecture = build on the existing compliant stack (Stripe for card/ACH, Plaid for bank link) + a gold-vendor/pricing API for live spot price and fulfillment. Shopify, if used, is storefront/marketing only — never the regulated payment/KYC backend.
  4. “Gold Byiu” payment API = to confirm. Likely your gold vendor (Dillon Gage) or a bullion pricing/fulfillment API. Named below as the Gold Vendor API until confirmed.
  5. Product scope = three coin sizes only: 1/10 oz, 1/2 oz, 1 oz.

1. Goal

Let a user buy a SQOOT Pure gold coin in three sizes through a Starbucks-grade purchase experience: clean, fast, card-based, trustworthy. Nail this core loop, then expand (gifting, group gift, subscriptions, vault/redeem).

Success = a first-time user can go from open → pick size → pay → confirmation in under 90 seconds, with KYC handled gracefully inside the flow.


2. Why Starbucks is the right reference

Mapping the Starbucks app patterns (from your screenshots) to SQOOT coin-buying:

Starbucks pattern SQOOT Pure equivalent
Stars balance + tier slider (25→400) Your gold holdings — total oz/grams owned, with a progress feel
“Scan in store” big green CTA “Buy Gold” primary CTA — always reachable
Drinks list (Hot/Cold/Tea) Coin sizes — 1/10 oz, 1/2 oz, 1 oz as clean product cards
Reward tiers (what you get at each level) Size cards with live price + what each represents
Onboarding carousel modal First-run trust carousel — “Real allocated gold, held securely”
Clean white cards, one bold accent color SQOOT brand palette, gold accent, lots of white space
Terms checkboxes at sign-up KYC + terms consent built into onboarding

The lesson from Starbucks: hide complexity, show one clear action per screen, make the balance feel rewarding.

⚠️ Key difference: no physical location

SQOOT Pure is fully digital — there is no store, branch, or pickup point. So everything location-based in the Starbucks app is removed, not adapted: - ❌ No store picker, map, or “Choose a store” - ❌ No “Pickup store” bar, pickup method, or “order ahead” - ❌ No “Send location” / nearby-store services (location permission isn’t needed for the core flow) - ❌ No store hours, drive-thru, or in-store filters

Fulfillment is digital: either the coin is shipped to the buyer, or the gold is allocated/vaulted and held in-app (see §9 open decision). The “pickup” mental model is replaced by “added to your holdings.”


3. Screen-by-screen flow (MVP)

Keep it to a tight core set. Each screen = one job.

A. Welcome / Trust carousel (first run only) - 3–4 cards, Starbucks-style modal: “Buy real gold in seconds” · “Allocated and securely held” · “Start from 1/10 oz” · “Gift it too (coming soon).” - CTA: Get started.

B. Sign up / Sign in - Email + password (+ Face ID / biometric option, like Starbucks). - Terms consent checkboxes: accept Terms + Privacy; optional marketing opt-in. - 18+ required.

C. Home / Dashboard - Top: “Your gold” — total holdings in oz + USD value (live). Empty state for new users: “Start your stack.” - Primary CTA: Buy Gold (big, gold/green). - Secondary: recent purchases, live spot price ticker (powered by AURUM). - Bottom nav: Home · Buy · Holdings · Gift (disabled/“soon”) · Profile.

D. Choose coin size (core screen) - Three clean cards: 1/10 oz · 1/2 oz · 1 oz. - Each shows: image of the coin, live price = (spot × weight) + premium/fee, and a one-line descriptor. - Quantity stepper per size; running cap of 20 coins enforced. - Live-price refresh indicator (“price locked for 60s at checkout”).

E. Review order - Line items, subtotal, fees, total. Price-lock countdown. - Payment method selector: Bank (ACH via Plaid) or Card (Stripe). (USDC/Klarna later.) - “By purchasing you agree to…” consent line.

F. KYC / Identity (first purchase, or threshold-triggered) - Collect required identity info (name, DOB, address; ID/selfie if threshold hit). Framed reassuringly: “A quick check keeps everyone safe and is required for gold purchases.” - This is mandatory and must feel native, not bolted on. (See §5.)

G. Payment - Bank link (Plaid) or card entry (Stripe). Confirm.

H. Confirmation - Success state: “X oz added to your holdings.” Order #, receipt by email. - Nudge: view holdings / buy again / (soon) gift.


Account-area screens (from additional Starbucks references)

These aren’t part of the purchase loop but are needed for a complete app. Map directly to Starbucks patterns:

I. Profile / Account home (Starbucks “Account”) - Sections: Profile (Personal info, Payment methods, Transaction history, Privacy & data, Account ID) · Security (passcode lock, Face ID toggle) · Notifications (order/receipt + marketing toggles) · Help & policies (Help, Terms, Privacy Notice, Delete account, “Do Not Share My Personal Information”, Sign out) · app version footer. - ⚠️ The Privacy Notice, “Do Not Share,” and Delete-account links must point to the flows defined in VARPET/SQOOT Privacy Policy v4 — keep them consistent.

J. Personal info (Starbucks “Personal info”) - First/last name, DOB (drives 18+ + KYC), address fields. Editable; some fields lock once KYC-verified.

K. Payment options (Starbucks “Payment options” — two tabs) - Methods tab: saved bank (Plaid) + card (Stripe), Apple Pay, “Add payment.” - (No “gift card / stored balance” tab in MVP — revisit when gifting ships.)

L. Holdings / Transaction history (Starbucks “History”) - Chronological list of purchases (size, oz, $ paid, date) + running holdings balance. This is the SQOOT analogue of the Stars history — but it’s your gold, the core retention hook.

Additional reference screens (batch 2) — settings, trust & gifting

M. Privacy & data controls (Starbucks “Privacy and data”) - Toggles: share for targeted advertising, track activity across apps (ATT), send location. - ⚠️ SQOOT difference: per Privacy Policy v4 we do not sell/share data — the “targeted advertising” toggle should default off or be omitted; keep only location (for service) and an honest tracking stance. Wire the “Do Not Share My Personal Information” control here.

N. In-app legal display (Starbucks “iOS Privacy Policy” / “Application Terms”) - Render Privacy Policy v4 + Terms of Use as readable in-app screens, linked from Account → Help & policies. (Terms draft is a separate to-do.)

O. Help / Q&A (Starbucks “Customer Service” search + topic tiles) - A “How can we help?” search + topic tiles → wire to the SQOOT Q&A chatbot built on the role-tailored knowledge base. This is where the AI assistant lives in-app.

P. Gifting (roadmap, not MVP) (Starbucks “eGift” history + “Send a new gift”) - Empty state → “Send a gold gift.” Maps to your gift-link / group-gift roadmap and Diwali campaigns. Stub the entry point now (“soon”), build later.

Q. Payment method management (Starbucks “Scan & pay” carousel) - Card/bank carousel with “Make default” / “Manage.” For SQOOT this manages Stripe cards + Plaid bank links (no stored-value card in MVP).

R. Sign out + Delete account (Starbucks confirmation + “Delete account”) - Sign-out confirm modal. Delete-account flow needs a gold-specific twist: unlike a coffee balance, an account holding real gold can’t be wiped on demand — the user must first sell, transfer, or redeem holdings, and records are retained for AML/tax per the compliance framework. Don’t copy Starbucks’ “we’ll mail your balance” literally; design settlement + retention.

4. Pricing logic

Coin price = (live spot price per oz × coin weight) + SQOOT premium/fee


5. Compliance overlay (non-negotiable — Fortress Gold is a FinCEN-registered dealer)

This is what makes it different from a coffee app. Bake in from day one:

Loop in Wisdom (compliance advisor) to confirm KYC tiers and the reporting threshold before build.


6. Payments & architecture recommendation

Recommended: custom flow on your existing compliant rails.

On Shopify: fine as a marketing storefront or landing page, but not the purchase backend — Shopify Payments won’t approve bullion, and it’s weak for KYC/ACH. If you want Shopify for SEO/landing, it links out to the compliant SQOOT purchase flow.

“Gold Byiu” — confirm: exact provider, whether it does live pricing, physical fulfillment, vaulting, or all three. This determines the integration scope.


7. Visual / asset list (to produce this phase)


8. Development requirements (Phase 1 build)

  1. Auth: email/password + biometric, 18+ gate, terms/marketing consent capture.
  2. Catalog: 3 fixed SKUs (coin sizes) with weight + premium config.
  3. Live pricing service: poll Gold Vendor API / AURUM; compute all-in price; price-lock at checkout.
  4. Cart/limits: quantity stepper, 20-coin cap, dollar-threshold checks.
  5. KYC module: tiered identity capture + AML screening hook; gate first purchase.
  6. Payments: Stripe (card) + Plaid (ACH) integration; idempotent order creation.
  7. Order + fulfillment: create order, call vendor to allocate, store receipt, email confirmation.
  8. Holdings ledger: per-user oz balance + transaction history.
  9. Admin: orders, KYC status, refunds/exceptions, price-config.
  10. Compliance logging: immutable audit of KYC, screening, transactions, thresholds.

9. Open decisions (need your input)

  1. Confirm “allow only 20” meaning (assumed: 20 coins/order).
  2. Confirm “Gold Byiu” = which provider, and what it covers (pricing / fulfillment / vault).
  3. Storage model: does the buyer receive a physical coin (shipped), or allocated/vaulted gold they hold in-app? (Changes fulfillment + the “holdings” UX a lot.)
  4. KYC tiers + reporting threshold (with Wisdom).
  5. Brand assets: use Vanessa’s existing SQOOT brandbook for the UI tokens?

10. Next steps

  1. You confirm §9 (especially storage model + Gold Vendor API) and the assumptions in §0.
  2. I build the clickable Starbucks-style prototype of screens C→H so you can feel the flow.
  3. Then the full technical architecture plan (data model, API contracts, sequence diagrams, compliance flows).

v1 — June 3, 2026.