Partner Portal is the operating console for approved Onyx partners.
Use it to review your catalogue, create and track connectivity orders, monitor active services, manage wallet balance, review invoices, configure developer access, manage webhooks, invite team members, and open support cases when Onyx action is required.
The portal is built for day-to-day partner operations. It gives commercial, support, finance, and developer teams the same source of truth without exposing private Onyx operating details.
What You Can Manage
Partner Portal gives approved teams access to:
- catalogue packages
- order creation and order history
- active service records
- usage snapshots
- wallet balance and reserved balance
- ledger activity and invoices
- webhook endpoints and webhook event history
- developer credentials
- team members and invitations
- support cases
- launch and environment readiness
Your role controls which areas you can view or change.
Catalogue
The catalogue area lists the packages available to your organization.
Each package has a partner-facing package ID, coverage name, coverage type, region, data allowance, validity period, status, and commercial fields approved for your account.
Use the catalogue to decide what your customer experience can offer. Do not create your own package names, allowances, validity periods, or coverage promises outside the approved catalogue.
Orders And Services
Orders connect a catalogue package to a customer reference from your system.
After you create an order, the portal lets your team follow the order through preparation, activation-material readiness, install state, and service status. Use the order record when support, billing, or reconciliation needs a shared reference.
Active service records help your team review current install state, package, usage, and timing without exposing sensitive activation material in public channels.
Wallet, Billing, And Invoices
The wallet area shows how much partner balance is available, how much is reserved for open orders, and how much has been spent in the current billing period.
Ledger entries record reserves, captures, releases, credits, refunds, and monthly commitment adjustments. Invoices summarize the billing period, currency, commitment, true-up, and status.
Finance users should reconcile invoices against the order and ledger records in the portal.
Developers And Webhooks
The developers area manages credentials for approved API access.
Credentials can be active, rotated, or revoked. Treat credentials as secret material. Never place them in client-side code, public repositories, analytics tools, or support screenshots.
The webhooks area lets your team configure event endpoints, review delivery history, replay eligible events, and investigate failed deliveries.
Team Access
Team access is role-based.
Owners and admins can manage the organization. Developers manage API and webhook work. Billing users handle finance areas. Support users work with orders, services, and support cases. Viewers can review approved information without changing it.
Invite only the people who need access for their role.
Support Cases
Support cases should include the order ID, package ID, service identifier, customer reference, current state, and the customer-facing issue.
Do not include secrets, activation codes, private identity documents, full payment details, or unrelated customer data in support cases.
Environment Readiness
The portal can separate sandbox access from live access.
Sandbox lets your team test catalogue display, order creation, webhook handling, support flows, and reconciliation without live customer impact. Live access begins only after Onyx approves production readiness.

