How it works

The real flow, in order. Nothing here is aspirational. This is what happens today when you use ArcLedger.

Add a wallet by its public address

That's the only thing ArcLedger ever asks for. No seed phrase, no private key, no wallet-connect signing prompt. Public address in, and that's the entire trust bar you're crossing.

Import runs in the background

ArcLedger reads the wallet's USDC transaction history from Arc and imports it. This can take a little time for wallets with a lot of history, but you're never stuck watching a blocking spinner, and re-running an import never creates duplicate records.

Transactions land in your list, uncategorised

Every incoming and outgoing USDC transfer shows up with its amount, direction, and counterparty address. Anything ArcLedger structurally recognises as a transfer between your own tracked wallets is flagged with a suggested internal-transfer badge.

Add business context

Open a transaction, set a category, link it to a customer or supplier, add a description. Confirm or override the internal-transfer suggestion. Every change you make is recorded in that transaction's audit history.

Turn repeat patterns into rules

If the same counterparty or pattern keeps showing up, create a rule once and it classifies future imports automatically. If you already have matching history, apply the rule retroactively. ArcLedger shows you exactly how many transactions would change before you confirm anything.

Check your monthly numbers

Income, expenses, and net cash flow for the period, broken down by category, with drill-through from any number back to the transactions behind it.

Export for your accountant

A structured CSV with every field an accountant would actually need: dates, categories, counterparties, amounts, and the underlying transaction references, ready to hand off.