Partner & white-label
White-label surfaces and partner ops without exposing upstream brands.
Partner ledger isolation edge cases
Edge cases where partner exports and debits never cross tenant boundaries — refunds, shared jobs, and support macros stay scoped.
Partner ops: multi-tenant habits
Operate many partner brands on one IOSOR platform without mixing wallets, logs, keys, or night exports across tenants.
Partner incident without exposing rails
When partner traffic fails, keep status white-label — no upstream rail brands in UI, webhooks, or support macros during outage.
Partner surface gate: no brand leak
Gate partner UI copy, API errors, and webhooks so upstream rail brands never appear — white-label status language only before production volume.
White-label one account: first honest path
Partners start on one prepaid IOSOR account for many services — wallet, catalog honesty, and no upstream brands — before multi-tenant complexity.