Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Identity Wallet Account Block for React

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.

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

Let people share one fact instead of a whole document, with this identity wallet for React with Base UI. Three credentials are drawn as cards in an inset Frame: a verified email, "Over 18" and a verified address, each with its issuer and the days it was verified and ends. The card you choose is outlined, and a native radio laid over each card means a click, Space and the arrow keys all choose it. Under the cards a shop asks for the chosen credential ("The Gilded Hare asks for Over 18") and the panel says what it would see ("Yes, you are over 18") and what it would not (your birthday, your other credentials, your last name). A Switch adds one optional extra, the first name, to what the shop sees, and the Shine Button shares. The result says it was a demo and the card remembers who it was last shown to. On a phone the cards scroll sideways. It's built from Frame, Switch, Badge, Shine Button and Guides, with a CSS entrance only. For a digital ID, a membership or any app that holds proofs for its users.

FAQ

How do I fill it with my own credentials and shops?

Edit CREDENTIALS (a name, what it holds masked, the issuer, and the ISO days it was verified and ends) and ASKS, one per credential: who asks, sees (the answer they get), the three hidden things and the extraSees line the switch adds. The card icon is a small if-chain in CredentialIcon. Nothing here is a real person's data and no credential is checked.

Does Share send anything?

No. It adds an entry to this page's log, says what the shop would have seen and that nothing was sent, and stamps the card's last line with the shop and the day. To make it real, send only the seen lines to your verifier from share, never the whole credential, and record the share on your server.

What does the extra switch do?

It adds one line to what the shop would see, your first name, and nothing else. It is remembered per credential while you stay on the page and it resets the status line, so what you read always matches what Share would do. The lists of what a shop would and would not see never change height, so the Share button stays where it was.

How do the cards work with a keyboard and a screen reader?

The cards are a group of native radios named after each credential and described by its issuer and dates, so a screen reader hears "Over 18, radio, 2 of 3" and the issuer. Tab goes to the chosen card and the arrow keys move to the next one, which also chooses it. The outline is more than colour: a badge on the chosen card says Chosen.

What stays local?

Everything: the choice, the switch, the log and the status line. A reload starts again. The names of the shops and issuers are invented.

How does it look on a phone?

The cards scroll sideways in a snapping row with the next card showing, so the choice and the request are both on the first screen or close to it. Below the cards the lists and the switch stack, and the Share button spans the width. In a right-to-left page the dates and masked values keep their reading order.

  • Pro

    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.

  • 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

    The certificates that sign an account in on a device: ruled rows with the issuer, the end date and days to go, a details row with serial number and fingerprint, Renew, Revoke and an add dialog.

  • Pro

    A signature and the key behind it: key facts with a fingerprint and a public key download, a signature pad with a typed route, the signature at three sizes, and a new key that asks first.

  • Pro

    A person's consent choices as an accordion of purposes with switches beside a consent receipt, an ordered log that gains a line for each choice and saves as a real PDF or JSON file.

  • Pro

    The sign-in providers linked to an account: each with its address, link date and use history, an Unlink that asks first and refuses on the only way in, an Undo line and quiet buttons to link more.