Onyx ID is the identity system for the Onyx account.
It gives customers a stable profile, handle, permissions, and trust state across Onyx products and approved connected apps.
What It Does
Onyx ID connects account identity to mobile service.
It supports profile information, handles, verification, consent, connected apps, and permission review as those features become available. The goal is to avoid starting from zero every time an app or feature needs to know who you are.
Why It Matters
Mobile service already depends on trust.
You need account access, plan ownership, payment context, recovery, support, and sometimes verification. Onyx ID gives those actions a common identity base.
What Customers Control
Onyx ID is built around permission.
A connected app can request access. A customer can review the request. The app receives only the approved context. Access can expire or be revoked as controls become available.
Profile And Handle
The profile makes the account recognizable.
A handle supports account presence, connected apps, chat, communities, and connected apps as they become available. It helps people find and trust the right account without exposing private details by default.
Trust And Verification
Some actions need more confidence than a basic sign-in.
Verification confirms eligibility for specific actions. The result stays simple: whether the account is eligible, what is needed, and what happens next.
Connected Apps
Onyx Connect lets approved apps request scoped access to Onyx ID.
This reduces duplicate accounts and gives the customer more control. Instead of building another profile, an app can ask Onyx for the permission it needs.
Privacy
Onyx ID keeps private evidence protected by default.
The product shows the visible result and the permission involved. Sensitive identity details stay protected unless a specific action requires customer review.
What It Is Not
Onyx ID is not a public score, a social profile, or a wallet address.
It is the account identity for service, permissions, communication, and connected apps.
Next
Read Trust & Verification for trust states, and Connect SDK for app permissions.