Process 02 — Onboarding & First-Bid KYC
Process 02 — Onboarding & First-Bid KYC
Section titled “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).
Failure-path summary
Section titled “Failure-path summary”| Path | Trigger | User-visible outcome | Recovery |
|---|---|---|---|
| VIES degraded | SOAP timeout / 5xx | Registration completes; bidder may bid (capped paths) | Async queue retries 72 h, then admin queue |
| SCA abandoned | User closes 3DS modal | 409 setup.requires-action; no bid placed | Retry within 15 min using same pending_bid_token |
| Card declined | setup_intent.setup_failed | UI shows “Card was declined”; no PM saved | User enters a different card; fresh SetupIntent |
| Identity required | bid > 500 € & account < 14 d | Bid staged, not placed; Identity link emailed + shown | On verified webhook, bid auto-released to 04 |
| Non-EU registration | country not in EU-27 | Account created, bidding blocked | Manual approval via /admin/queue/non-eu |
Cross-references
Section titled “Cross-references”- 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.