Skip to content

Identity - XYZ

Like any ID, but anonymized

Note: If you delete your identity, it cannot be recovered, even if recovery steps have been attempted. To avoid losing access to all your work, we strongly recommend that you do not delete your identity under any circumstances.

Identity Examples

Access Card:

  • Functions as a digital or physical pass, granting entry to events, spaces, or systems.

Membership Badge:

  • A hybrid between identity verification and access, symbolizing belonging to a community or group.

Loyalty & Rewards Card:

  • Earned through actions such as recycling or repeated purchases (e.g., “buy 10, get 1 free”), incentivizing positive behavior.

Payment Card:

  • Programmable for various funding purposes, including debit, credit, or prepaid transactions.

Collectibles Card:

  • Represents items like trading cards (e.g., baseball or hockey) or other unique collectibles.

Ownership/Authenticity Certificates: - Provides verifiable proof of ownership or authenticity for assets, both physical and digital.

Vouchers:

  • Includes store credits, IOUs, promissory notes, or gift cards.

Customizable Cards:

  • Developer-branded tokens programmable with unique rules, designed to align with the end-user’s preferences and displayed as part of their digital collection.

Multifunctional Card:

  • Combines any of the above features into a single versatile “card,” tailored to meet diverse needs and use cases.

Identity Roles

Funder

Any vendor or developer or entity that provides a microenvironment to an end-user via the XYZ app. Anonymous login is just one of the functionalities which the Funder can outsource to XYZ.

Client

An application (browser or mobile app) that is linked to XYZ, and is allowed to do the following: * Trigger user authentication (e.g. via a Login button) * Receive an access token from the XYZ authorization server.

The client is created by a developer for a company or governmental entity, and allows the end user to anonymously authenticate with the client with the help of the XYZ mobile app.

End user

This is the human that uses the client application to authenticate with the Funder.

For the purposes of anonymous login functionality, it is the person who clicks the Login button on the Funder’s website or mobile app, and who is then taken to XYZ to give consent to the scope requested by the Funder. In the process of giving consent, the user is authenticated anonymously and gets logged in to the Funder’s app or website.

Identity

Who the end user presents themselves as to the Funder.

In most cases, it is unnecessary for the end-user to provide their real identity to a Funder in order for the interaction to take place to the satisfaction of both parties. For example, a person can use different nicknames or email addresses on different online portals.

As a result, as long as the bearer of an identity presents said identity to the Funder correctly, all the requirements for a successful exchange are satisfied. Unbox Studio

Unbox’s product that allows developers to build and sign transactions, create identities, etc. For logging in untracked users, this is where the developer can implement a login button and obtain a piece of code to paste into their site to create a functional login sequence for their end-users.