White-Label — One Card Platform, Two Relationships

"Northstar — an online brokerage offering an Arta-powered, portfolio-secured card to eligible investors." The product sits inside Northstar's own app shell: Northstar owns discovery, navigation, brand and the customer relationship; Arta powers eligibility, decisioning, compliance, security and AI guardrails.

The visual language adapts; the decision integrity stays consistent.

Arta core · Locked

Regulated card capabilitiesEligibility & eligible-asset logic, limit decisioning, required data, disclosure completeness, consent records, authentication & fraud, decision/error states, AI safety boundaries, audit trail, servicing.

Guardrailed configuration

Adjustable, with rulesBrand colour within contrast requirements, type within supported scale, radius & surfaces, tone of voice, AI assistant name, card artwork, product naming, benefit descriptions, order of non-critical modules.

Partner-owned shell

Northstar's appNavigation, account home, card discovery entry point, campaigns & cross-sell, segmentation, loyalty, general support entry, marketing communications.

Arta — theme #1

9:41▪▪▪

Changed — partner expression

App shell & navigation entirely Northstar's
Entry point & discovery partner decides where the card lives
Brand, theme, card art via partner token file, contrast-validated
Product name Northstar Reserve Card
Value-proposition copy & benefits
AI assistant name Northstar Assistant
Support destination

Unchanged — Arta-governed

Limit result & calculation logic same eligible-asset math
Required explanations "why this limit", market-movement risk
Fee information hierarchy
Consent requirement nothing pre-checked, all logged
Decision & error states
AI boundaries data shown, confirm-before-action, escalation, audit
Accessibility & security signals

Northstar Invest — partner shell

9:41▪▪▪

Platform ownership model

Layer	Arta controls	Partner configures / owns
Distribution	Card capability & eligibility API	App shell, entry point, promotion
Product	Eligible-asset & limit logic	Product name, benefits, card artwork
Application	Required data & decision states	Theme, tone, supporting content
Compliance	Mandatory disclosures & consent	Jurisdiction-approved brand wording
Security	Authentication & fraud standards	Partner login entry, account shell
AI	Data permissions, explanation, confirmation, escalation	Assistant name, visual identity, notification tone
Servicing	Card status, payment & dispute capabilities	Navigation, support-handoff presentation

What partners cannot change

Hide or de-emphasise fees, or reduce the prominence of critical warnings with brand styling
Remove the portfolio / market-movement risk explanation
Alter a decisioning outcome — or present pending as approved
Remove the next step from a decline or adjusted offer
Pre-check any consent
Let the AI move money or sell assets without explicit confirmation
Hide which data the AI used

In implementation: theme tokens, content schemas, protected components and partner-level configuration permissions — the token pipeline already rejects governance violations at build time.