M5-07 Wallet-Based Disclosure Integration

Milestone: M5 — Disclosure and Verification SOW Reference: FR2, INT2 Requirement Clarity: ✅ Clear Dev Status: ❌ Not started — only the offer/claim side of wallet interaction exists today, not disclosure

Overview

When a candidate clicks the disclosure link/QR code, their wallet handles selecting and sharing the requested credentials back to the platform. Per the SOW, the actual in-wallet disclosure flow is outside this platform's scope — the platform's job is to receive and record the disclosed presentation.

Backend Tasks

• Implement the endpoint(s) that receive a disclosed presentation from a candidate's wallet (via the Velocity Credential Agent)
• Store the disclosed presentation against the presentation-request.entity.ts (schema already exists) and the candidate/disclosure request

Frontend Tasks

• Show disclosure completion status back to the candidate on the landing page
• Update the Staffing Company's view of the disclosure request once received

Dependencies

• M5-03 disclosure email/landing page — the entry point to this flow.
• M5-08 verification integration — what happens to the disclosed credential next.

Acceptance Criteria

• Candidate can disclose credentials through wallet
• Revoked/expired credential handled correctly (per SOW Appendix 3, "Velocity Wallet" integration acceptance criteria)

Existing Reference Material

• SOW Appendix 1, INT2 — "There is no direct code-based integration with the Wallet Ecosystem; access to the wallets are driven by links and QR codes."

Blockers & Risks

None identified beyond general M5 risk.