Integration Overview explains how approved partners connect to Onyx.
The goal is controlled access. Apps can request what they need from Onyx ID without asking customers to rebuild identity from scratch.
What Integrations Do
An integration connects an app to approved Onyx account context.
That context can include profile permission, handle access, trust status, communication reach, or another approved scope. The customer remains in control of consent.
Why It Matters
Good integrations reduce repeated work.
Customers do not need a new identity for every partner app. Partners do not need broad account data to confirm one permission or eligibility result.
The Basic Flow
A partner app requests access. Onyx presents the request. The customer approves or denies. The app receives the approved result.
If access changes, the app must respect the new state.
App Identity
A connected app identifies itself clearly.
The customer needs to recognize the app before making a permission decision. Hidden or unclear app identity breaks trust.
Requested Access
A request stays specific.
"Profile access" is different from "verification assertion." "Communication reach" is different from "payment context." The product names the permission in plain language.
Ongoing Control
Permission is not a one-time black box.
Customers need visibility into connected apps and the ability to manage access as controls become available.
What Integrations Cannot Do
Integrations do not receive the whole account.
They cannot bypass consent, collect private evidence, mutate mobile service, or access unrelated wallet and communication history.
Where This Fits
Integrations make sense after the Onyx account is useful on its own.
Connectivity gives the customer a reason to belong. Identity gives apps a safe way to connect. Payments and communication can add specific utility where permissions allow.
Next
Read Connect SDK for consent flow, and Trust & Verification for scoped assertions.