Let users voluntarily verify identity with a passport photo and a selfie holding the passport, understand review outcomes and how verification changes account limits.
Approach
Document UX and measurement before implementation. Add shared KYC models, provider and injectable dummy service, native image selection, EN/RU status/limits overview and guided submission. Model backoffice review, correctable rejection and final denial; preserve basic access. Use existing theme and router.
Acceptance criteria
UX plan and review/limits contract documented before implementation.
Optional verification, configurable tier limits and clear upgrade benefits.
Two-photo selection, validation, preview, replacement, review and submission.
Loading, failures, retry, pending, approved, correction and denial states.
Shared mobile-reusable service/provider; no identity data in telemetry or persistence.
EN/RU, responsive/accessibility checks and journey tests.
Required validation, commits, push, PR and durable documentation.
Notes
Current product has no authenticated backend/backoffice. Deliver explicit dummy workflow with service contracts for later integration, not a live document collection or authorization system. Per user clarification, limits are fetched through a dedicated provider/service from the backend stand-in; widgets do not infer caps from status. Sendico ADR 0001 and ListVisibleLimits contracts informed the boundary. No legal/compliance policy is inferred. Real review decisions must be server-authoritative; production backoffice UI/storage is outside this frontend flow.
Delivery
PR #21, branch kyc-20. UX planned before implementation in docs/ux/kyc.md. All 86 frontend tests, analyzer in three affected packages, format and web build pass. Browser PNG selection and mobile visual review completed; 320px Russian/large-text, accessibility and recovery covered by tests. Production backend/storage/backoffice/support remain explicit integration boundaries. Not merged.
### Goal
Let users voluntarily verify identity with a passport photo and a selfie holding the passport, understand review outcomes and how verification changes account limits.
### Approach
Document UX and measurement before implementation. Add shared KYC models, provider and injectable dummy service, native image selection, EN/RU status/limits overview and guided submission. Model backoffice review, correctable rejection and final denial; preserve basic access. Use existing theme and router.
### Acceptance criteria
- [x] UX plan and review/limits contract documented before implementation.
- [x] Optional verification, configurable tier limits and clear upgrade benefits.
- [x] Two-photo selection, validation, preview, replacement, review and submission.
- [x] Loading, failures, retry, pending, approved, correction and denial states.
- [x] Shared mobile-reusable service/provider; no identity data in telemetry or persistence.
- [x] EN/RU, responsive/accessibility checks and journey tests.
- [x] Required validation, commits, push, PR and durable documentation.
### Notes
Current product has no authenticated backend/backoffice. Deliver explicit dummy workflow with service contracts for later integration, not a live document collection or authorization system. Per user clarification, limits are fetched through a dedicated provider/service from the backend stand-in; widgets do not infer caps from status. Sendico ADR 0001 and ListVisibleLimits contracts informed the boundary. No legal/compliance policy is inferred. Real review decisions must be server-authoritative; production backoffice UI/storage is outside this frontend flow.
### Delivery
[PR #21](https://git.sendico.io/tech/sxchnge/pulls/21), branch `kyc-20`. UX planned before implementation in docs/ux/kyc.md. All 86 frontend tests, analyzer in three affected packages, format and web build pass. Browser PNG selection and mobile visual review completed; 320px Russian/large-text, accessibility and recovery covered by tests. Production backend/storage/backoffice/support remain explicit integration boundaries. Not merged.
tech
added the frontend label 2026-09-12 07:06:13 +00:00
tech
self-assigned this 2026-09-12 07:06:13 +00:00
tech
added this to the SXCHNGE project 2026-09-12 07:06:13 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Let users voluntarily verify identity with a passport photo and a selfie holding the passport, understand review outcomes and how verification changes account limits.
Approach
Document UX and measurement before implementation. Add shared KYC models, provider and injectable dummy service, native image selection, EN/RU status/limits overview and guided submission. Model backoffice review, correctable rejection and final denial; preserve basic access. Use existing theme and router.
Acceptance criteria
Notes
Current product has no authenticated backend/backoffice. Deliver explicit dummy workflow with service contracts for later integration, not a live document collection or authorization system. Per user clarification, limits are fetched through a dedicated provider/service from the backend stand-in; widgets do not infer caps from status. Sendico ADR 0001 and ListVisibleLimits contracts informed the boundary. No legal/compliance policy is inferred. Real review decisions must be server-authoritative; production backoffice UI/storage is outside this frontend flow.
Delivery
PR #21, branch
kyc-20. UX planned before implementation in docs/ux/kyc.md. All 86 frontend tests, analyzer in three affected packages, format and web build pass. Browser PNG selection and mobile visual review completed; 320px Russian/large-text, accessibility and recovery covered by tests. Production backend/storage/backoffice/support remain explicit integration boundaries. Not merged.