Onyx Partner Platform is the operating layer for partners that build with Onyx.
It covers two lanes: Connect SDK for identity, consent, trust, communication, and events; and Partner Connectivity for embedded mobile connectivity offers, orders, activation, usage, billing, and support.
Partners get controlled access to the capabilities Onyx enables for their organization. Users stay in control of consent. Sensitive account data, verification evidence, activation material, credentials, and private customer information stay protected.
What Partners Can Build
Partners can build:
- Sign in with Onyx
- scoped account access
- profile and handle permissions
- trust and verification assertions
- consented communication permissions
- app-linked conversation threads
- configured messages and delivery events
- embedded connectivity catalogues
- connectivity orders
- activation guidance
- usage review
- partner wallet and billing workflows
- team access and support operations
Access depends on app review, domain verification, production readiness, user consent, account trust, regional availability, and compliance review.
Partner Portal
Partner Portal is the operating console for partner organizations.
Use it to review catalogue packages, create and track orders, monitor active services, manage wallet balance, review invoices, configure webhooks, invite team members, issue developer credentials, and open support cases.
The portal keeps operating teams aligned without exposing private Onyx systems.
Connect SDK
Connect SDK is the application integration layer for Onyx ID.
Use Connect SDK to add login, scoped consent, capability checks, trust and verification assertions, communication permission checks, pre-send checks, app-linked conversations, webhook delivery, and event handling.
Connect SDK does not give apps unrestricted identity access. Apps receive the scopes, assertions, and communication permissions granted through Onyx ID.
Partner Connectivity
Partner Connectivity is the embedded connectivity lane for partners.
Use it to offer catalogue display, package selection, connectivity order creation, service preparation, activation guidance, usage review, support workflows, wallet operations, billing review, and reconciliation.
Partner Connectivity is not an open resale marketplace. Package access, pricing fields, customer support boundaries, and launch readiness depend on the partner agreement and configured regions.
Connect SDK Catalogue
Connect SDK Catalogue defines the packages a partner can offer.
Each package record includes a public package ID, coverage name, coverage type, region, data allowance, validity period, package status, catalogue version, and available commercial fields.
Refresh the catalogue on the configured cadence, store the catalogue version used at purchase, and stop selling packages that are no longer present in the current catalogue.
Partner Responsibilities
Partners own the experience they build around Onyx capabilities.
Partners manage their own app experience, customer-facing copy, retail checkout, consent presentation, support intake, refund or credit policy under the partner agreement, and secure handling of partner-side credentials, webhooks, and logs.
Onyx controls the Onyx account, identity, consent, trust, connectivity policy, catalogue authority, and service-state checks that belong to Onyx.
Privacy And Consent
Onyx Partner Platform is built around scoped access and data minimization.
Connected apps receive granted scopes and assertions. Connectivity partners receive the information needed to operate the service flow and no unrelated Onyx account data.
Partners must not request identity documents, private verification evidence, wallet secrets, unrelated payment history, unrelated communication history, private device state, activation material outside secure flows, or credentials through support channels.
Before Production
Onyx reviews app identity, redirect URIs, verified domains, allowed origins, scoped permission requests, webhook signing, delivery testing, catalogue display, support paths, privacy handling, and compliance readiness before production access.
Unavailable capabilities should return a clear controlled state instead of failing silently.