Target: first OTC/conversion workflow. Current blockers: trader mandate, settlement account proof, technical owner.
Jump to the screen needed for the next CS action.
Working status for today.
Missing item, blocked workflow, owner, next action.
Owner, blocker, and next outbound.
Ask Braiins who can approve OTC/conversion instructions and which internal policy governs trade approval.
API/reporting cannot be prepared without a technical contact, webhook owner, and test credential workflow.
Separate what Lunar can serve now from partner-routed or product-direction services before client expectations harden.
Selected service, status, blocker, activation requirement.
Qualified quote and execution workflow for Bitcoin treasury conversion or larger settlement needs.
Convert mining or platform revenue into the settlement asset Braiins needs for operations.
Route approved account data into Braiins systems after technical owner is named.
Define who can move funds, request settlement, approve conversions, and operate within limits.
Not in first activation. No client ask.
Potential mining ecosystem value, but should not be offered as a live onboarding promise yet.
Use one state only: live, partner-routed, internal review, or deferred. If the state is not known, do not ask the client for documents yet.
Entity/jurisdiction, authorization, activity, source, risk tier. Open blockers: trader, technical owner, settlement proof. Internal review only.
Every gate has an owner, a blocker state, and a plain client ask when something is missing.
Legal entity, registration jurisdiction, operating model, and Banking House purpose are prepared from discovery.
Ownership chart is submitted, but reviewer needs confidence on 20%+ UBO scope and control logic.
Trader authority, fund movement approval, and technical executor scope need explicit confirmation.
Mining revenue and treasury movement story exists, but CS should attach a short plain-English narrative.
Monthly volume, currencies, transaction types, counterparties, and first-use milestone need final confirmation.
Wallet ownership, address screening, and transaction context should be attached for Bitcoin rails.
Backend-only check state with false-positive handling and reviewer notes. Not customer-facing.
Define whether Braiins can proceed with a temporary limit while authority or technical evidence is finalized.
Each document and field maps to a Sumsub submission field, owner, and status.
Every document should say what it unlocks. No random compliance scavenger hunt.
Confirms legal entity, jurisdiction, and current standing.
Maps UBOs, directors, and control logic for account permissions.
Identifies who may approve quotes, trades, and treasury conversion instructions.
Bank letter or account statement confirming the settlement account Braiins will use for fiat rails.
Shows mining infrastructure, pool/software activity, revenue logic, and expected flows.
Plain explanation of mining/software revenue, treasury movement, and why conversion is expected.
Wallet ownership, expected address use, screening state, and escalation notes for Bitcoin flows.
Names API/reporting contact and expected integration path.
Captures call context, pains, service goals, and promises already made.
CS needs to know who can answer, who can approve, who can trade, and who owns implementation.
Authorized representative expected to sign onboarding review and confirm company authority.
Prepared UBO/control person. Needs invite, liveness, address proof, and ownership evidence.
Prepared as authorized trader, but needs Tomas or board-level confirmation before first quote.
Finance/document owner for upload follow-through and settlement account evidence.
Still unnamed. Owns API/reporting test path, webhook questions, credential handling, and security model.
Owns next touchpoint, client-facing clarity, document chase, and activation handoff.
Reviews evidence bundle only after CS has attached context, service links, and missing items.
Tasks CS can execute today.
Ask for trader, technical owner, and settlement account proof. Blocks first quote, API prep, and account movement.
Confirm API/reporting/conversion availability and limits before next client message.
Add discovery notes, selected services, and first-use intent to the review file.
Choose measurable activation milestone: first quote, conversion test, reporting handoff, or movement setup.
Owner: CS. Reviewer: compliance. Status: missing authority proof.