ClaraWideSEE IT. SHOP IT. SUPPORT IT. SHARE IT.
0
MAKER WORKSPACE · FINANCES

Know what sold, what ClaraWide charged, and when your money becomes available.

This workspace separates gross merchandise sales, ClaraWide fees, refunds, payout holds, completed payouts, and statement records so makers are never guessing where their money went.

No banking credentials are stored in this prototype.

Live transfers, identity verification, bank details, tax forms, and processor settlement data must come from the production payment provider. The records below model ClaraWide’s maker-facing accounting and payout experience only.

Available balance$0.00Eligible for next payout
Pending balance$0.00Waiting on fulfillment milestones
Paid this month$0.00Completed payouts
ClaraWide fees$0.00This month after reversals
PAYOUT STATUS

Your payout queue

Every maker order keeps its own payout state. New shops remain protected by the graduated trust schedule rather than receiving immediate payouts before fulfillment is proven.

Current tier: New Shop
PAYOUT VERIFICATION

Identity, business & tax readiness

ClaraWide reads current verification status and provider requirements before preparing a payout. Raw identity documents, tax identifiers and full banking credentials are intentionally not stored in this application layer.

PAYOUT EXECUTION

Prepared transfers & provider status

Once an eligible balance is prepared for payout, Clara freezes the exact amount and destination evidence. A prepared transfer can be held if the destination, refund state, or safety evidence changes before submission.

TRANSACTION LEDGER

Every adjustment stays attached to the order.

Sales, ClaraWide fees, refunds, fee reversals, disputes, payout holds, and payouts are shown as separate ledger entries instead of silently changing a balance.

PAYOUT TRUST LADDER

Faster access is earned by reliable fulfillment.

Payout timing can improve as a maker builds a clean history, and can slow again if serious risk appears.

Makers cannot buy, manually select, or theme-upgrade their way into a faster payout tier. Reliability and account standing control progression.

Production handoff still required. This foundation uses browser-local demonstration records. Launch requires processor webhooks, authoritative order/refund accounting, payout reconciliation, immutable server ledger entries, generated statement files, tax-document workflows, bank-account verification, admin finance controls, and audit logging.