BTC$68,420▲ 0.82% / ETH$3,841▼ 0.31% / LTC$94.05▲ 1.14% / SOL$221.60▲ 3.02% / USDT·TRC20$1.0000 / USDC·ERC20$0.9999 / XMR$168.42▼ 0.18% / TON$6.02▲ 0.47% / XRP$2.41▼ 0.09% / GAS·ETH18 gwei / Indicative prices · illustrative ticker / No-KYC · non-pooled · 0.4% flat / BTC$68,420▲ 0.82% / ETH$3,841▼ 0.31% / LTC$94.05▲ 1.14% / SOL$221.60▲ 3.02% / USDT·TRC20$1.0000 / USDC·ERC20$0.9999 / XMR$168.42▼ 0.18% / TON$6.02▲ 0.47% / XRP$2.41▼ 0.09% / GAS·ETH18 gwei / Indicative prices · illustrative ticker / No-KYC · non-pooled · 0.4% flat
OrbChain
UTC 18:47:02 Get started →
Feature · Multi-Brand ▓ N BRANDS · ONE LEDGER Per-brand keys + webhooks

One account.
Every brand.

Run any number of customer-facing identities on a single OrbChain account. Each brand carries its own logo, theme and checkout identity, its own webhook endpoint and secret, and its own scoped API keys — while every coin settles into one balance you control.

Many faces · One treasury
§ Part I / IV · What a brand carries

Everything the customer
sees — per brand.

Isolation surface
Ledger stays unified
SymSurfaceHow it isolatesStatus
IDIdentityName, URL-safe slug, logo, theme and brand color — the hosted checkout renders the paying brand, not your parent company.PER BRAND
KEYAPI keysMint scoped keys bound to a brand. Every payment created with that key is tagged to the brand automatically — no extra field to remember.SCOPED
WHWebhooksEach brand can point at its own endpoint with its own signing secret. Brand set → brand's secret signs; unset → inherits the account webhook. Same HMAC-SHA512 semantics.PER BRAND
RPTReportingPayments carry their brand tag through listings and exports — per-brand revenue is a filter, not a spreadsheet reconstruction.TAGGED
TRSTreasuryBalances, payouts, Auto Settle and sweeps stay account-level — one treasury regardless of how many faces it wears.UNIFIED
ARCLifecycleBrands archive cleanly: history and tags stay queryable, the identity stops being usable for new payments. A default brand always exists.SAFE
§ Part II / IV · The setup

Brand, key,
done.

Two steps
Dashboard or API
POST /dashboard/brandsthen mint a key bound to it
// 1. Create the brand (also two clicks in the Brands tab)
{
  "name":        "Neon Arcade",
  "slug":        "neon-arcade",
  "logo_url":    "https://cdn.neonarcade.example/logo.svg",
  "brand_color": "#39ff88",
  "webhook_url": "https://api.neonarcade.example/webhooks/orb"
}

// 2. Mint an API key scoped to the brand (API Keys tab → brand selector).
//    Every payment created with that key:
//      – renders Neon Arcade's checkout identity
//      – fires webhooks at Neon Arcade's endpoint, signed with its secret
//      – lands tagged brand=neon-arcade in listings and exports
§ Part III / IV · What it's for

Operators with
more than one face.

Common shapes
All on one login
SymOperatorHow multi-brand runs itBrands
AGNAgenciesOne brand per client: the client sees their own name on checkout and receives webhooks on their own infrastructure — you keep one dashboard, one balance, one rev-share.per client
STOMulti-store operatorsEvery storefront checks out under its own identity with its own key — a leaked key from store A can't create payments as store B.per store
RSLWhite-label resellersShip "your own" payment product on OrbChain rails: your customer's brand end-to-end on the checkout, your account underneath.per product
GEORegional identitiesSame business, different market-facing names — separate identities and webhook pipelines, unified treasury and payout schedule.per region
§ Part IV / IV · Questions

Things operators
ask first.

Short answers
No fine print
Q.01Do brands have separate balances?

No — that's the point. Identity, keys and webhooks isolate per brand; funds unify in one account-level balance per coin. If you need separate treasuries, run separate accounts and settle between them with zero-fee internal transfers.

Q.02How many brands can I create?

No enforced cap. Create, rename and archive brands freely from the Brands tab or the API; every account starts with a default brand.

Q.03What happens to webhooks if a brand doesn't set its own URL?

They fall through to your account-level webhook and secret. Brand-level settings override only when present — safe defaults, no double delivery.

Q.04Can I see revenue per brand?

Yes — payments are tagged at creation, so per-brand filtering works across dashboard listings and API list endpoints.

Q.05Is this the same as the white-label payment product?

Complementary. White-label payments control what a single checkout looks like; Multi-Brand manages many distinct identities — each of which can use any payment product.

Stop juggling
accounts per storefront.

Unlimited brand identities, isolated keys and webhooks, one treasury. Live on every account today.