Arc
Counting
Arc Counting gives crypto-native operators one surface to review outbound payouts, inbound revenue, privacy state, and settlement logic without dropping back into spreadsheets or stitched-together tools.
Private by design
Privacy stays visible in the product through shielded routes, pseudonymous identities, and verified wallet states.
Operator clarity
Teams can review payroll due, pending receivables, usage revenue, and settlement health in the same room.
Workspace preview
Treasury available
$482k
Payroll due
$31k
Pending receivables
$18k
Usage revenue today
$2.4k
Outbound desk
Payroll batch / Shielded
Approved
$18.4k
Vendor invoice / Verified
Queued
$7.2k
Bonus run / Pseudonymous
Draft
$4.1k
Inbound desk
API usage / Multi-wallet
Streaming
$146
Checkout link / Verified
Settled
$2.1k
B2B invoice / Company
Pending
$9.8k
Operating model
The product is not a generic crypto dashboard. It is an operator surface built around two connected realities: outbound finance operations for teams and inbound revenue capture for products.
B2B layer
Run payroll, vendor payouts, and invoice settlement from one control desk instead of separate tools and delayed reconciliation loops.
Private payroll batches on Arc
Receivables with optional liquidity paths
Treasury-aware approvals and routing
B2C layer
Meter usage, collect payment at the moment value is created, and keep inbound demand in the same accounting surface as outbound operations.
WalletConnect Pay for live checkout
Usage, invoices, one-time payments, and reusable links
Programmable settlement logic for software-native revenue
What the shell exposes
Control desk
Overview surfaces treasury available, payroll due, pending receivables, usage revenue, and settlement health as distinct operator concerns.
Visible privacy
Privacy is explicit in the UI through wallet state, routing state, and selective reveal patterns rather than buried configuration.
Wallet-native demand
WalletConnect Pay handles checkout moments for products and agents without splitting inbound revenue into a separate system.
Programmable settlement
Payment rules, settlement assets, privacy modes, and event logs can live closer to the financial surface instead of in disconnected dev tooling.
Design position
The landing is now doing a clearer job: it feels like an operator instrument, and it previews how the actual product is structured instead of repeating generic marketing sections.
Employees and customers are treated as separate counterparts because outbound and inbound money movement behave differently.
Identity and wallets are distinct first-class objects, which is why privacy state and verification state appear repeatedly throughout the system.
The product shell is dense enough for serious work, but it still reads as editorial and controlled rather than like an exchange dashboard.
Settlement path
Arc Counting only works if the rails are legible. The interface has to explain where privacy sits, when collection happens, and how settlement closes back into the ledger.
01
A payroll run, invoice event, or metered call becomes a visible money event inside the workspace.
02
Approve, shield, meter, or collect without losing the operator view of why money is moving.
03
Arc settles, WalletConnect Pay captures, and records land back in one room instead of vanishing across products.
Open the workspace
The landing now points directly at the product idea: a calm accounting room for private payroll, invoices, and programmable revenue on Arc.