KYC & Compliance covers regulated identity checks for Onyx actions that require stronger eligibility review.
Complete these checks when payment actions, card features, number support, connected app assertions, organization access, sensitive recovery, or another regulated service requires them.
KYC is not the center of Onyx ID. It is a regulated check used for specific actions.
Verification
Verification gate flow
Follow the customer-visible status from a required check through review, completion, failure, or expiration.
Current step
Action requires check
Account shows
Affected action and next step
Data shared
Only required verification result
Why Verification Exists
Some Onyx features operate inside regulated telecom, payment, card, and identity environments.
Verification helps protect account ownership, prevent fraud and impersonation, support payment and wallet activity, meet telecom requirements, support card issuance, validate jurisdiction eligibility, and protect sensitive recovery actions.
Verification exists to support safe access. It is not a public status badge.
When Verification Is Required
Onyx should request regulated verification only when the action requires it.
Verification may be needed for card issuance, FX settlement, payment eligibility, number activation in regulated regions, connected app assertions, organization verification, sensitive recovery, high-risk account changes, or regulated wallet/payment actions.
If an action does not require regulated verification, Onyx should not ask for it as a general onboarding burden.
Verification Flow
A verification flow starts from the action that needs it.
The flow should explain which action triggered the check, what information is required, whether the check is regulated, and what happens after submission. It may use document review, selfie or liveness confirmation, address review, organization documentation, or eligibility questions based on the action.
Some checks complete quickly. Others need additional review because of region, document quality, telecom requirements, payment rules, fraud review, or organization review.
Verification States
Verification states help you understand what comes next.
A check can be not required, required, started, pending, awaiting information, completed, failed, expired, revoked, refresh required, or unavailable. Some actions wait until the required check completes successfully.
If a check needs attention, Onyx should identify the affected action and the next step.
Trust And Eligibility
Verification updates trust and eligibility.
A completed check can support payment eligibility, card issuance, number support, connected app permissions, wallet-linked actions, regulated services, or organization access. It does not automatically make account details public.
KYC status should not become a public badge, unrestricted connected app field, public profile detail, wallet replacement, or chat status symbol.
Scoped Results
Connected apps can request limited verification assertions through Onyx ID.
An app may request an approved assertion such as identity verified, age verified, payment eligible, jurisdiction eligible, or organization verified. The app receives only the result you approve, not raw documents, unrestricted account access, unrelated wallet activity, payment history, fraud review details, or private evidence.
Expiration And Refresh
Some verification results expire.
Refresh requirements depend on local regulation, payment rules, telecom policy, document expiration, account recovery, organization review timing, or risk review. A feature may pause until the refresh completes.
Telecom And Payments
Telecom services can require identity or address checks before number activation or messaging access becomes available.
Payment and card services can require regulated identity checks, sanctions screening, fraud review, eligibility validation, issuer review, and secure payment handling. Unsupported regions, failed verification, expired review, issuer restrictions, or regulatory restrictions can limit a specific action.
Privacy And Safety
Verification data should stay scoped and permissioned.
Onyx should not expose identity documents, provider records, sanctions review data, private fraud analysis, compliance archives, or sensitive identity evidence in normal customer flows.
Never share one-time codes, private keys, seed phrases, recovery phrases, full card details, wallet backup material, or signing approvals outside approved secure flows.