所有作品
案例 12
KYB / KYC B2B Register — Societe API
Designed B2B company registration and identity verification flows integrating the French Societe API, covering KYB (Know Your Business) and KYC (Know Your Customer) verification across multi-country regulatory requirements.
KYBKYCB2B RegisterIdentity VerificationSociete APIMulti-countryCompliance UX
- A structured B2B registration flow that handled multi-country regulatory variation clearly
- Clearer document upload and verification states reduced user confusion
- Closer cross-team alignment between UX, compliance, and backend on what the API could support
- Product type
- B2B company registration & identity verification
- Platform
- Web (desktop)
- Timeline
- 2024–2026 · multi-phase compliance stream
- Role
- UX flow, UI design, compliance flow mapping
- Team
- Designer, PM, compliance team, backend engineers
- Tools
- Figma, FigJam, Flow diagrams
為什麼這個專案存在
B2B enterprise onboarding requiring both KYB (Know Your Business) and KYC (Know Your Customer) verification using the French Societe API for company data validation. The product needed to guide business users through multi-country regulatory compliance — a process that is inherently complex, document-heavy, and legally sensitive.
我負責的部分
- B2B UX
- Verification Flow Design
- Compliance UX
- Document Upload Flow
- Multi-step Onboarding Design
- Cross-functional Collaboration
困難之處
- Multi-country regulatory requirements meant different documents and verification steps per country
- Business users often don't know what's required upfront — the flow had to guide them progressively
- API integration constraints meant the UX had to map carefully to what Societe could validate
- Long, multi-step forms risk drop-off — keeping momentum while collecting complex data
- Error states needed to be actionable, not just 'something went wrong'
如何完成
- 1Mapped the full KYB + KYC verification requirements per supported country
- 2Designed progressive disclosure for multi-step business registration
- 3Collaborated with compliance team to understand API validation rules
- 4Designed document upload flows, status indicators, and rejection-recovery states
- 5Designed error, pending, and verified states throughout the flow
- 6Reviewed and iterated with engineering on API-driven UI edge cases
背後的思考
Introduced a step indicator and status system so business users always knew where they were, what was needed next, and why — reducing anxiety in a legally sensitive flow.
精選視覺
抽象示意圖——原創 mockup，非客戶截圖。
改變了什麼
- A structured B2B registration flow that handled multi-country regulatory variation clearly
- Clearer document upload and verification states reduced user confusion
- Closer cross-team alignment between UX, compliance, and backend on what the API could support
我的收穫
Compliance-driven design taught me that clarity is a legal asset — when users don't understand a verification step, it costs everyone time and trust.