Skip to main content
The treasury surface gives finance teams a real-time view of cash across all Sly-managed accounts: how much is where, in what currency, committed to what, and where it’s running low. This is where your CFO or finance ops lives — distinct from the developer-facing transfer/stream endpoints.

Dashboard snapshot

Response:

Currency exposure breakdown

Understand where money is committed:
Shows:
  • Active mandates — AP2 pre-authorized spending not yet executed
  • Scheduled transfers — future-dated moves committed
  • Open streams — money flowing out per second; runway at current rate
  • Pending disputes — money in escrow during dispute
  • Reserve holds — chargeback / compliance reserves
Partner treasury teams use exposure numbers for cash-flow forecasting and liquidity planning.

Treasury accounts

Internal accounts your treasury team operates against (distinct from customer accounts):
Treasury accounts have balance limits that trigger alerts:
  • min_balance — alert if balance drops below
  • target_balance — rebalancing target
  • max_balance — alert if balance rises above (idle cash)

Record a treasury transaction

For entries that aren’t customer-originated (e.g. your CFO wiring funds in from the corporate bank):
Types:
  • inbound — external money in (partner funding, bank deposit)
  • outbound — external money out (payout, bank withdrawal)
  • rebalance — internal move between treasury accounts
  • fee — operating fees (rail charges, provider costs)
  • adjustment — manual correction

Auto-rebalancing

When one treasury account is above max_balance and another is below target_balance, auto-rebalance moves funds:
Can be automated by linking rebalancing to a settlement rule.

Alerts

Active alerts cover:
  • Balance below min_balance
  • Balance above max_balance (idle cash)
  • Currency exposure approaching limit (regulatory or internal)
  • Rail connectivity down (can’t settle)
  • Reconciliation gap above threshold
Subscribe to treasury.alert.opened webhook for real-time paging.

Endpoints

Typical treasury workflows

Daily:
  • Check dashboard for any alerts
  • Review overnight rebalancing moves
  • Confirm reconciliation reports clean
Weekly:
  • Review currency exposure forecast vs. actual
  • Adjust rebalancing thresholds if inventory is drifting
  • Review alert history for recurring issues
Monthly:
  • Close-out treasury account reconciliation against GL
  • Review idle-cash metrics and max_balance tuning
  • Update rail counterparty limits if volume grew

Permissions

Treasury endpoints require the treasury:* scope on API keys. By default only owner and admin users can access them via the dashboard. Don’t grant treasury scope to integration-layer API keys.