Zum Inhalt springen

Process 02 — Onboarding & First-Bid KYC

Companion to: docs/superpowers/specs/2026-05-23-02-identity-onboarding-design.md Date: 2026-05-23

This diagram covers the full path from anonymous visitor through first-bid acceptance, with the three principal failure branches (VIES degraded, SCA abandoned, Stripe Identity required).

Registration verifies email and business identity before bidding. The first bid sets up a Stripe payment method, handles authentication or card failure, and proceeds only after the required checks pass.Registration verifies email and business identity before bidding. The first bid sets up a Stripe payment method, handles authentication or card failure, and proceeds only after the required checks pass.
PathTriggerUser-visible outcomeRecovery
VIES degradedSOAP timeout / 5xxRegistration completes; bidder may bid (capped paths)Async queue retries 72 h, then admin queue
SCA abandonedUser closes 3DS modal409 setup.requires-action; no bid placedRetry within 15 min using same pending_bid_token
Card declinedsetup_intent.setup_failedUI shows “Card was declined”; no PM savedUser enters a different card; fresh SetupIntent
Identity requiredbid > 500 € & account < 14 dBid staged, not placed; Identity link emailed + shownOn verified webhook, bid auto-released to 04
Non-EU registrationcountry not in EU-27Account created, bidding blockedManual approval via /admin/queue/non-eu
  • Spec §3 endpoints implement each step above.
  • Spec §4 covers the VIES retry queue mechanics.
  • Spec §5 covers Stripe SetupIntent + error-code UI mapping.
  • Spec §7 covers Stripe Identity escalation rules.
  • Master §10.4 records the VIES outage caveat that motivates the degraded-pending state.