Creator view

Their account, their answers.

A tenant-branded portal where creators log in to see what they earned, why, and when they'll get paid. They tap any number to trace it back. They pick how they want to be paid. They sign off on receipt. The "why is this my number?" email never gets sent, because they already see the answer.

The home screen

What every creator sees the moment they log in.

Their current period, their balances, their payout method, their full history. Branded as the tenant they earn from, grouped across every brand they earn from on a single login. Mobile-first, so the answer is one tap away on the phone they always have.

Welcome back, Maren
Signed in · iPhone 15
Northwind Audio Meridian Studio Lighthouse Academy
Current period
Apr 2026 · monthly Northwind · Net to you
USD10,367.28
Reserve · 30-day refund $0.00 releases May 31
Advance balance $0.00 no advance outstanding
Payout
Default · for Northwind PayPal Payouts maren@example.com
Last paid May 6 · $9,128.40
Recent statements
Apr 26 Northwind · Apr 2026 Ack'd $10,367.28
Mar 26 Northwind · Mar 2026 Ack'd $9,128.40
Apr 26 Meridian · Apr 2026 Ack'd $4,212.00
01 · Tenant-branded
The brand they earn from, not yours.
Logo, primary color, statement footer language. The creator sees the brand they have a contract with, not "CleaRoyalty." Every brand they earn from gets its own visual identity inside the same portal.
02 · Cross-brand by default
One login, every brand grouped.
A creator who earns from multiple brands signs in once and sees all of them across the top. Royalties stay calculated independently per brand; the portal just stops making the creator juggle three logins to find one number.
03 · Current period at the top
The number they came for.
The most recent published statement is the first thing on the screen, not buried under settings. With reserves, advances, and recoupment state surfaced one strip below.
04 · Mobile-first
Designed for the phone they always have.
Not a desktop-first dashboard squeezed onto mobile. Statements, balances, and payout settings all work in one thumb on a 6-inch screen.
05 · Acknowledge in one tap
Receipt logged to the second.
A "tap to confirm" on every published statement. Timestamp, device, and the lines they tapped land in your audit log. If they don't open it, that's logged too.
Their answers, self-served

Every number on the statement opens to the answer.

Creators don't ask "why is my payout this number?" by sending an email. They tap the number on their statement and it expands to the source data, the clause that authorized it, and the contract version that ran. Same trace your auditor would see. Same trace the engine produced.

Why is my April payout $10,367.28?
Gross sales SRC 17,424.00
1,224 units × $14.24 avg sale price · App Store · Apr 1–30
Store fee 30 % SRC −5,227.20
App Store standard cut, deducted at source before creator share applies
Creator share §4.1 × 0.85
Tier reached at $1M cumulative LTV (CR-01847 §4.1) · share increased from 70 % to 85 % prospectively
Net to you $10,367.28
Source data on every input
Where the number came from.
Each input cites the platform it was pulled from and the period it covers. Units, prices, fees, refunds: all traceable to the source row CleaRoyalty pulled.
Clauses on every multiplier
Why the rate is what it is.
Tier rates, base shares, reserves, recoupment: each one points to the exact clause and contract version that authorized it. Not a label, the actual quoted clause.
Most questions resolve in the portal
Three taps to the answer.
When a creator can see their own "why" without asking — the sale, the clause, the split — most questions never need a thread. Your support volume drops, their trust goes up, and the answer is on the record either way.
When a thread is needed, it's on the record
A button on the line in question.
If something does need a conversation, the creator taps the line and raises it. The question goes to your inbox and theirs as a real email — every reply lives in both inboxes, where neither side can rewrite it later. The objection-window clock keeps running, the period banner reflects the open question, and the resolution lands as either an amendment or a closure note in the audit log.
Their account, their settings

Creators manage their own payouts.

Creators pick how they want to be paid by each tenant from the providers that tenant has connected. Multiple methods per tenant are supported, with one flagged as default. Change anything any time. Every change lands in the audit log.

Payout methods · for Northwind
3 connected · 1 default
Default
PayPal Payouts
maren@example.com
Used for: monthly statements
Backup
Bill.com vendor
Vendor ID: V-029471
Used for: corrections, manual payouts
Backup
Lob · paper check
123 Main St, Austin TX 78701
Used for: year-end summary checks only
+ Add another method
Available providers (this tenant has connected)
PayPal Payouts Bill.com Wise Stripe Treasury Lob check
Pick from connected providers
Their choice, from your shelf.
Each tenant decides which payout providers to connect. Each creator picks from those, per tenant. A single creator on three tenants can have three different default rails, and each tenant only sees the methods relevant to them.
Multiple methods per tenant
A default and as many backups as they want.
A PayPal email for fast monthly statements, a Bill.com vendor record for corrections, a mailing address for year-end check delivery: all live on the same creator record, all routable per statement.
Encrypted, not shared
Payout details stay scoped.
Provider-specific details (vendor IDs, bank tokens, mailing addresses) are encrypted with the tenant's key. Other tenants the creator works with cannot see them. Other creators cannot see them.
Change anytime, audited
Every edit on the record.
When a creator changes their payout details, the change lands in the audit log with timestamp, device, and the values before and after. Tenant admins see the change in their dashboard the same period.
History & export
Their full record, downloadable.
Every published statement they've ever received, downloadable as PDF or CSV. Their personal record of what was sent, what was acknowledged, what was paid, and when.
Sign in, securely

An auth model designed around creators, not security theater.

Passwordless login, second factor where it matters, single login across every brand. Built so creators can get to their statement in seconds and so sensitive actions still require an explicit signal.

Magic-link login
Passwordless
Creators enter their email, get a one-tap link, and they're in. No password to forget, no reset flow that takes a week. The link is single-use and expires quickly.
Every action is on the record
Attribution
Changing payout details, exporting data, raising a dispute, opening a statement — every action is attributed to the creator's authenticated session, timestamped, and surfaced to the tenant admin's audit log. The traceability is the friction; nothing happens off the record.
Cross-brand single login
One identity
A creator with relationships across multiple tenants signs in once and sees all of them. No "create an account for the new brand," no separate password to lose. The tenant relationship is what changes, not the identity.
Session & device records
Audit log
When the creator signed in, from which device, which statements they opened, which lines they tapped: all logged. Visible to tenant admins, exportable in the audit-package bundle.
Acknowledgement on the record
Receipt
Confirming a published statement is logged against the creator's identity, with timestamp and device. Counsel can see exactly when the statement was received, by whom, on what.
Close access when the relationship ends
Tenant control
When the relationship ends, the tenant admin closes the creator's active access. Past statements stay visible and downloadable. Open objections preserve access: the platform blocks closure until they resolve.

See what your creators see, before they do.

Book a demo Back to the overview