Clean money, or it doesn't move.

Summer-managed wallets are backed by Fireblocks — the institutional custody platform used by exchanges, market makers, and crypto-native treasuries. Keys live behind MPC and hardware isolation, never on a Summer server, and never visible to a Summer operator. Where it fits the workflow, you can also bring your own self-custody wallet and use Summer purely as the accounting layer on top.

• Institutional MPC custody for managed wallets
• Bring-your-own self-custody wallets are first-class
• No private keys ever held by Summer
• Per-wallet role assignment (view / send / approve)

Incoming transactions and wallets are screened for risk before funds touch your treasury, so you can safely convert through exchange and banking partners. Each check returns a risk score, a risk level, and a blacklist status — visible on the transaction, exportable to the compliance file, and attached to the invoice it reconciles against.

• Risk score + risk level + blacklist status per check
• Decision recorded against the inflow and the invoice
• Exchange-safe treasury — only screened funds in
• Exportable trail for compliance sign-off

Fraud rarely lives in a single transaction — it lives in the connections between wallets. Anti-fraud monitoring runs real-time graph analysis across every wallet you watch, with block-to-alert in under 15 seconds. It uses read-only on-chain data only — no keys are accessed, no ledger writes, no off-chain account access. Detections are exportable as part of the compliance audit trail.

• 8 detection patterns (kickback, round-trip, splitting, fresh wallet…)
• <15s alerts, 4 chains, 0 keys accessed
• Read-only on-chain data — no ledger access
• Exportable audit trails for compliance review

When privacy matters, payouts can be routed so the receiving party never sees the originating treasury wallet. Transit transfers move through rotating wallets, a single payout can be split across multiple sources, and one-time disposable receiving addresses can be issued for inbound funds. The full operation remains fully reconciled on your side.

• Transit transfers via rotating wallets
• Split a payout across multiple sources
• Disposable one-time receiving addresses
• Payees never see your treasury

Summer is an accounting and operations layer, not a custodian. For teams that prefer to hold every key themselves, the entire workflow — invoicing, AML screening, reconciliation, approvals, P&L — runs on top of self-custody wallets. Summer never holds, signs, or sees your private keys, and there is no path by which a Summer engineer can move funds without your signature.

• Self-custody-only mode supported end-to-end
• No Summer signature ever required on a payout
• No internal admin override on customer wallets

Every payout, approval, role change, and configuration change is written to an append-only audit trail. Approvals reference the policy that was in effect at the time. Reconciliations reference the invoice and the AML decision. Exports are CSV or JSON, scoped per entity or per client, ready for your accountant, your auditor, or your regulator.

• Per-payout approval log (who, when, which policy)
• Reconciliation chain back to invoice + AML check
• Scoped exports per entity / client
• Role-based access to logs — least privilege by default

Summer ingests public on-chain data and the metadata you give it (invoices, recipients, categories). We do not custody private keys, do not read your bank accounts, and do not require off-chain account access to operate. Sensitive fields are encrypted at rest. Data residency and broader compliance posture (including SOC 2) are on the roadmap — ask us where things stand before signing.

• Encryption at rest for sensitive fields
• Least-privilege internal access — audited
• No private keys, no banking credentials
• SOC 2 and data residency on the roadmap