Onyx ID | Onyx Docs

Onyx ID is the identity system attached to your Onyx account.

It controls how your account appears across:

Onyx Mobile Network
Chat
Communities
connected apps
support
wallet-linked payment features
public profile surfaces

Onyx ID manages:

profile identity
account trust state
verification state
connected app permissions
consent history
linked devices and sessions
account recovery posture
identity visibility

The same identity remains attached to your account across supported devices, regions, and services.

Onyx ID

Profile visibility preview

Switch viewer context to see which identity fields are visible and which remain private.

Display name

Available

Shown on public profile

Handle

Available

Public profile path

Verification evidence

Blocked

Private by default

Wallet activity

Blocked

Not exposed

Account

Onyx ID

donald.onyx

Viewer: Public

Visible: Display nameVisible: HandlePrivate: Verification evidencePrivate: Wallet activity

What Onyx ID Is

Onyx ID is designed as:

a portable account identity
a trust and consent system
a connected app authorization layer
a profile and visibility system
a verification and recovery layer

It controls:

how your profile appears
which apps can access account information
which verification states are shared
who can contact you in supported contexts
which actions require additional verification

The system is designed around consent and visibility instead of public identity exposure.

What Onyx ID Is Not

Onyx ID is not:

a crypto identity wallet
a public KYC profile
a decentralized identity protocol
a wallet-first onboarding flow
a public claims marketplace
a banking onboarding product

Wallets, attestations, verification providers, and compliance systems can exist underneath the product, but the account experience stays focused on:

profile
permissions
verification
consent
trust
account access

Your Profile

Your profile can include:

display name
handle
avatar
bio
status
public profile path
selected public content
approved external links

Depending on visibility settings, parts of the profile can appear in:

chat conversations
communities
connected apps
support interactions
public profile views

Some profile information may remain hidden depending on:

account visibility settings
relationship context
verification state
connected app permissions

Public profile visibility is controlled from the account.

Profile Projection

Onyx ID does not expose the same profile to every viewer.

Different viewers can receive different profile views depending on:

relationship context
community membership
connected app permissions
public visibility settings

Examples:

public visitors can see public profile details
contacts can see additional relationship context
communities can see community-specific roles
connected apps only receive approved fields

Connected apps never receive unrestricted identity access.

Connected Apps

Supported apps can request access to Onyx ID through permission-based authorization.

An app can request:

profile access
verification status
handle access
account assertions
communication permissions
community-linked permissions
identity-linked app access

Before approval, the app should show:

app name
requested permissions
requested account access
expiration timing where supported

You can:

approve access
deny access
revoke access
review connected apps
review permission history

Some permissions expire automatically depending on app policy or account state.

Permission States

Permissions can appear as:

requested
pending approval
granted
limited
expired
revoked
denied

Permissions can become restricted if:

verification expires
the app loses eligibility
account recovery begins
regional policy changes
trust state changes

Your account should show:

which apps are connected
what each app can access
when access expires
when access was granted
whether revocation is available

Trust And Verification

Some account actions require stronger trust or regulated identity verification before they become available.

This can include:

wallet actions
card issuance
payment settlement
number eligibility
connected app permissions
account recovery
regulated services

Your account should always show:

the current trust state
whether verification is required
which action is affected
what information is required
what step must be completed next

Current trust states include:

Basic
Trusted
Verified
KYC Verified
Organization / Service Verified

Trust status can appear as:

active
pending
required
refreshing
expired
revoked
unavailable

Trust state is designed to communicate account confidence and eligibility. It is not a public social ranking system.

Verification Requirements

Verification requirements can depend on:

region
local telecom regulation
payment eligibility
connected app permissions
card availability
transaction size
account recovery state
fraud and abuse review

Some actions may require:

identity verification
address verification
age verification
organization review
payment verification
recovery confirmation

Verification states can appear as:

not required
required
started
pending
awaiting information
completed
failed
expired
revoked
refresh required
unavailable

Some account actions remain unavailable until verification completes successfully.

Regulated Verification

Onyx supports regulated identity verification through trusted verification providers including:

Sumsub
Persona

These providers can be used for:

identity verification
age verification
jurisdiction checks
payment eligibility
fraud review
telecom compliance requirements
organization verification

Verification providers process:

document review
selfie matching
liveness checks
sanctions screening
compliance review
risk analysis

The Onyx account does not expose raw provider systems directly in normal product flows.

Instead, your account receives:

verification status
trust state updates
eligibility results
action availability
refresh requirements
verification expiration state

The product intentionally avoids exposing:

raw KYC payloads
provider internals
compliance jargon
document archives
sensitive verification evidence

KYC verification exists to support regulated actions. It is not the purpose of Onyx ID.

KYC status should not appear as:

a public social badge
unrestricted app data
public profile metadata
a wallet replacement
a chat status symbol

Scoped Verification Results

Connected apps can request limited verification assertions through Onyx ID.

Examples include:

identity verified
age verified
payment eligible
jurisdiction eligible
organization verified

Apps only receive the specific assertion you approve.

Apps should not receive:

raw KYC documents
unrestricted account access
unrelated wallet activity
unrelated payment history
private verification evidence

Solana Attestation Service

Onyx ID can use Solana Attestation Service (SAS) as part of the account trust and activation system.

SAS is used as a trust and attestation layer for supported identity and activation events.

Examples can include:

Onyx ID activation
account trust assertions
account-linked activation state
connected service eligibility
regulated verification references where supported

SAS operates underneath the product experience.

Normal users should not need to understand:

onchain account structure
transaction mechanics
attestation schemas
rent calculations
wallet signing internals

The product language stays focused on:

identity active
verification completed
trusted account
eligible service access
connected app authorization

Wallet linkage does not automatically verify the account.

Attestations can contribute to trust and activation state, but they are not the entire trust model.

Onyx ID should still work meaningfully without:

wallet setup
crypto knowledge
direct blockchain interaction

Some connected services may use SAS-backed trust references to:

validate account state
validate verification eligibility
validate connected service permissions
support portable trust across approved apps

These flows remain permissioned and scoped through Onyx ID.

Wallet Connection

Wallets can attach to Onyx ID as optional linked capabilities.

Wallet linkage can support:

payment actions
account authentication
wallet-linked verification
supported trust signals

Wallets are not required for Onyx ID to function.

Wallet connection alone does not automatically verify the account.

Privacy And Consent

Onyx ID is designed around permissioned identity access.

Connected apps should only receive:

approved profile fields
approved identity assertions
approved verification states
approved communication permissions

Apps should not receive:

raw KYC payloads
unrestricted account access
unrelated wallet activity
unrelated payment history
unrelated chat history
private verification evidence

Verification data remains private by default unless explicitly required for a supported action.

Sessions And Recovery

Onyx ID also manages:

linked devices
session visibility
recovery posture
trusted session restoration
account-linked authentication state

Recovery state can affect:

connected app access
wallet-linked features
verification state
communication permissions

Some recovery actions may temporarily restrict account capabilities until verification completes again.

What Can Affect Availability

Identity features can become unavailable because of:

unsupported region
expired verification
revoked trust state
connected app restrictions
account recovery state
regulatory requirements
wallet disconnect
provider availability

The account should show the current restriction before an identity action begins.