EP047 — Verification and re-request workflow

Recipient-safe verification completion and recovery. A link is a secure delivery mechanism; it is not a dead end. Internal delivery state never leaks to the recipient.

Recipient verification process

Recipient

Open valid link

Pre-filled listing opens without login. Mark opened once only.

→
Recipient

Review and attest

Correct details; name, relationship and accuracy confirmation are required.

→
Atomic gate

Submit once

Save submission and pending claim; invalidate token only after commit.

→
Required outcome

Acknowledgement

Confirmation, no public changes yet, manual review next, and safe contact expectation.

Unavailable / expired / already-used link recovery

Recovery

Unavailable screen

Plain reason without token leakage. Never display a blank page.

→
Recipient

Request a new link

Business identity and safe contact route; rate limited and acknowledgement-only.

→
Admin gate

Review / reissue

Operator verifies route, explicitly issues new token; old token remains invalid.

→
Delivery

New link delivery

Prepared is not sent. Explicit approved send required.