Trust & Verification explains how Onyx determines whether your account is eligible for certain actions, services, and connected app permissions.
Some actions require stronger account confidence before they become available. This can include:
- wallet actions
- card issuance
- payment settlement
- number eligibility
- connected app permissions
- account recovery
- regulated services
- organization verification
Your account should always show:
- the current trust state
- whether verification is required
- which action is affected
- what step is required next
Trust state is designed to communicate account confidence and eligibility. It is not a public social ranking system.
Trust
Trust eligibility ladder
Select a trust state to see available actions, blocked actions, and the next account requirement.
Account access
Profile
Card
Regulated number
Complete setup
Why Trust Exists
Onyx combines:
- mobile service
- numbers
- payments
- identity
- communication
- connected apps
Those systems become less safe when accounts are anonymous, disposable, or disconnected from real account ownership.
Trust exists to:
- reduce fraud
- reduce impersonation
- protect account recovery
- protect payment actions
- protect number ownership
- improve communication safety
- allow regulated features where required
The goal is not to create a public verification hierarchy.
The goal is to make the account safer, more recoverable, and more trusted across connected services.
How Trust Benefits You
Trust state affects what your account can do.
Depending on verification and account health, trust can help:
- unlock payment features
- unlock card eligibility
- unlock number eligibility in regulated regions
- improve account recovery confidence
- reduce spam and impersonation
- allow connected apps to trust account assertions
- reduce repeated onboarding across supported services
Instead of re-verifying identity for every supported app or payment flow, approved services can request limited trust assertions through Onyx ID.
Trust States
Onyx currently supports five trust states:
Basic The account exists and core account setup is complete.
Trusted The account has enough healthy signals for common account activity and communication contexts.
Verified The account has stronger confidence through verification, account posture, recovery health, device continuity, relationship trust, or additional review.
KYC Verified The account completed regulated identity verification for supported regulated actions.
Organization / Service Verified The account represents an approved organization, developer, institution, or service identity.
Trust state can affect:
- connected app permissions
- payment eligibility
- number activation
- communication trust
- organization visibility
- supported account assertions
Trust status can appear as:
- active
- pending
- required
- refreshing
- expired
- revoked
- unavailable
If trust status changes, the account should explain:
- which action is affected
- whether additional verification is required
- whether access is temporarily restricted
- whether refresh or review is needed
Verification Requirements
Verification requirements can depend on:
- region
- payment activity
- local telecom regulation
- card eligibility
- connected app permissions
- account recovery state
- transaction size
- 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.
Privacy And Visibility
Verification is designed to stay scoped and permissioned.
Public profiles should not expose:
- raw KYC status
- provider details
- verification documents
- compliance records
- private review information
Connected apps should only receive:
- approved assertions
- approved trust visibility
- approved permission scope
Verification exists to support:
- account safety
- regulated eligibility
- payment security
- communication trust
- account recovery
- connected app trust
without exposing unnecessary personal information.