Building Revela: Identity Verification (Part 4)

Trust through verified identities—without storing more than we need.

Why Verify?

In a marketplace for valuable art, anonymity is a liability. We verify identity so we can:

• Reduce fraud — Real identities discourage bad actors.
• Meet expectations — Know-your-customer style checks are normal for money and high-value goods.
• Resolve disputes — Real identities make follow-up and recourse possible.
• Signal seriousness — Verified users make the platform feel like a place for real collectors.

One Flow, Human in the Loop

Flow is simple: registration → document upload → admin review → verified. We accept ID card (front + back), passport, or driver's license. Documents are stored privately with short-lived access for reviewers. We don't extract or store document numbers, DOB, or address—only what we need to confirm identity and run the platform. On rejection, we delete the documents and tell the user why so they can fix and resubmit.

Tiered Access

Not everything requires verification. Browsing is open. Account creation needs email. Bidding requires verified identity. Selling adds bank-account verification. That keeps friction where it matters and avoids asking for more than we need.

GDPR and Control

Users can request deletion; we remove documents and clear verification data. Access to documents is logged and time-limited. The design is: collect only what's needed, keep it secure, and make it easy to delete. That's good for users and for compliance.

Series Wrap

Revela is built around four ideas: event-driven order flow (Part 1), escrow with clear states and manual payouts (Part 2), live bidding with anti-sniping (Part 3), and identity verification with minimal data (this part). Together they make a curated place where collectors can bid and sell with confidence.

Try it: revela.club. Building a marketplace or trust-heavy product? Get in touch—we focus on lean, human-centred design.