Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Verification Record Account Block for React

What an account has proven and when each proof ends: four rows with the method, the day and a derived end date, a due-soon state, one band that takes a six-digit code or a name, and Undo.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Keep a plain record of what you have checked about someone, with this verification panel for React with Base UI. A hairline frame with a plus mark on each corner holds four ruled rows (email, phone, ID document and address). Each says how it was proven and on which day, and when it ends: a proof is good for 12 months, or 24 for a document, so a row inside 30 days of its end says Due soon and when to re-verify, and a line over the list adds it up ("Phone needs re-verifying in 20 days"). Verify and Re-verify open one band under the list: a six-digit Input OTP with the demo's code printed beside it, or a name Input for the ID document. The matching answer stamps the row with the page's day and a new end date. Undo walks back the last change, and the header's Shine Button starts the next check. It's built from Input OTP, Input, Field, Badge, Button, Shine Button and Guides, with a CSS entrance only. For the account page of a marketplace, a lender or any app that proves people.

FAQ

How do I fill it with my own proofs and rules?

Edit START. Each proof has a label, what it covers (masked), the method in words, months of validity, the ISO day it was proven in on (or nothing), the check it uses (a code or a name) and the prompt the band says. The end date is derived from on and months, "due soon" is SOON days before it, and every date is relative to AS_OF, never the clock, so nothing here goes stale.

Where does the code come from?

In this demo it is printed in the band, because nothing is sent: "In this demo the code is 482 913." Send a new code moves to the next typed one and says so. Six digits check themselves on the sixth, typed or pasted with spaces, and Enter checks a short entry and says how many digits are missing. A wrong code clears the field and keeps focus in it. To make it real, send the code from your server in begin and check it on the server in checkCode; never ship the code to the page.

Does the ID document check read a document?

No. The check asks for a name, any two words of two letters or more pass, and no file is read or sent. It stands where your real document check would report back. The longer flow with uploads and a selfie is the identity verification block.

What stays local?

Everything. Verifying and re-verifying change this page's state and say so in the foot ("Phone is verified until 14 Oct 2027, in this demo"); nothing is checked, stored or sent, and a reload starts again. Undo walks back the last change, which a real server often can't.

Why does the page never jump when I open a check?

The band holds an unseen copy of its field's boxes, so it has the same height whether it says "Choose Verify" or shows the code field. Every row keeps three lines and a button of one size in every state, and the summary line and the foot have room for their longest sentences.

Is it accessible, and how does it look on a phone?

The rows are a real list. State is a word and a glyph (Verified, Due soon, Not verified), never colour alone, and each button says which proof it is for ("Re-verify Phone"). The code field is named for its row, its problem is linked to it, and the foot is a polite live region present from the start. Dates and masked values keep their reading order in a right-to-left page. On a phone the button sits under each row and the foot with Undo stays pinned to the bottom of the screen.

  • Pro

    The addresses on an account with which are proven by a postcard code: three ruled rows with one primary, a verify band with a code field and a resend, a form that checks the postal code by country, and Remove with Undo.

  • Pro

    A document check as one panel: a four-step rail, a document choice with a drop zone for each side, a demo selfie, an address form and a review that lifts the level from Basic to Verified.

  • Pro

    A wallet of verified credentials: three cards in an inset frame, a shop's request for the chosen one with what it would and would not see, an optional extra switch and a Share button.

  • Pro

    An account's recovery options: four numbered ways back in, each with its state in words, a masked value, a quiet test and a one-field form to set it up, and a line that counts how many are ready.

  • Pro

    The identity fields of an account as ruled rows that edit in place: full name, a username checked against taken names, an email that stays unverified until confirmed, a masked phone and a date of birth.

  • Pro

    The rules a managed account must meet by a deadline, as a bento of hairline cells: five rules with their state in words and a Fix button, a segmented bar, days to the deadline and Undo.