Move USDC, settle invoices,
run global payroll — agentically.
For treasury workflows, use the configured USDC route and wallet network. Automatic cross-chain bridging and rebalancing are not established capabilities.
Why the corporate card
doesn't work for this agent.
Manual payroll = expensive
Bank wires for 80 contractors in 22 countries. $30 per send, 3-day settle. The CFO is paying $30k/year in wire fees alone, plus 1–2% FX spread on every leg.
USDC is split across chains
Treasury sits on Base, Polygon, Solana, Ethereum mainnet. Bridges, gas, slippage. No single dashboard. Reconciling end-of-quarter takes a week of finance time.
No attribution on outflows
Who authorized the $42k vendor invoice? Today: a Slack screenshot and a forwarded email. Tomorrow: a court subpoena, a Security review finding, or an audit qualification you can't get past.
Everything this agent needs.
Nothing it doesn't.
From mandate to settlement.
CFO signs
For treasury workflows, configure supported caps, approvals and provider-specific card rules. Enforcement varies by route; multi-signature, anomaly-freeze and guaranteed-recovery behavior are not promised.
Daily reconcile
The agent submits payments through eligible configured routes. Authorization and settlement records depend on the selected path.
Multi-sig threshold
For treasury workflows, configure supported caps, approvals and provider-specific card rules. Enforcement varies by route; multi-signature, anomaly-freeze and guaranteed-recovery behavior are not promised.
One trace, one row
Whether ACH, SEPA, USDC or wire — the same trace ID lands in the ledger. Auditor exports a CSV; reconciles in minutes, not weeks. Re-verifies any signature against the principal's public JWKS.
Plug-and-play merchant lists.
Curated merchant allowlists ship with the wallet template. Add your own in one API call or one click in the portal.
Defaults you can flex.
| Daily cap | $50,000 |
| Monthly cap | $1,000,000 |
| Per-payee max | $25,000 |
| Multi-sig ≥ | $50,000 (2-of-3) |
| Quorum sig ≥ | $250,000 (3-of-3) |
| Cross-chain sweep | Base · Polygon · Solana |
| FX drift refuse ≥ | 50 bps from quote |
| Allowed rails | ACH · SEPA · Pix · UPI · USDC |
Everything else you need to know.
Why a treasury agent needs more than a corporate card.
Corporate cards solve one part of treasury — small recurring software charges — and break on everything else. Bank wires for international payroll cost $25–$45 per send and settle in three days. SWIFT correspondents take an unpredictable FX cut. ACH is only US-domestic and capped at $25k for most banks. And none of these rails carry a signed authorization the auditor can verify cryptographically; you're trusting an email chain.
For treasury workflows, configure supported caps, approvals and provider-specific card rules. Enforcement varies by route; multi-signature, anomaly-freeze and guaranteed-recovery behavior are not promised.
For treasury workflows, payment and refund options depend on the configured provider, route and recipient. Confirm eligibility, fees and settlement estimates before execution; no measured speed or savings are promised.
Multi-sig that actually works for finance teams.
For treasury workflows, configure supported caps, approvals and provider-specific card rules. Enforcement varies by route; multi-signature, anomaly-freeze and guaranteed-recovery behavior are not promised.
When the agent proposes a payment that crosses a threshold, it generates a PaymentMandate, hashes it, and pushes an approval card to each signer over WhatsApp, Slack, or email. Each signer taps approve; their device produces a signed assertion that's bound to the mandate hash. The agent waits until the quorum is met, then executes — and if any signer refuses, the mandate dies and is logged with the rejection reason.
Configured USDC payment paths.
For treasury workflows, use the configured USDC route and wallet network. Automatic cross-chain bridging and rebalancing are not established capabilities.
For treasury workflows, use the configured USDC route and wallet network. Automatic cross-chain bridging and rebalancing are not established capabilities.
How this fits with NetSuite, QuickBooks and your existing GL.
AgentWallet is a payment + ledger system; it is not an ERP. Treasury teams using NetSuite, QuickBooks, Xero, or Sage feed the AgentWallet ledger export into their GL nightly. The export is grouped by your GL code (set per agent or per allowlist entry), so vendor invoices land on the right expense account without manual coding.
Webhook delivery is signed (HMAC-SHA256 over the canonical body), so a fake invoice can't trick the GL ingestion. The webhook payload includes the trace ID, the signed mandate hash, and the rail-specific receipt (ACH file ID, SEPA Instant settlement reference, USDC tx hash, card auth code) so reconciliation against bank statements is fully automated.
Common questions.
- Is the treasury agent allowed to send money without a human?
- For treasury workflows, configure supported caps, approvals and provider-specific card rules. Enforcement varies by route; multi-signature, anomaly-freeze and guaranteed-recovery behavior are not promised.
- Which rails are supported for payroll?
- ACH (US), Wire (US/intl), SEPA Instant (EU), Pix (Brazil), UPI (India), FedNow (US), BACS (UK), Interac e-Transfer (Canada), PayNow (Singapore), PromptPay (Thailand), and USDC on Base, Polygon, Solana. The agent picks the cheapest rail that meets the recipient's preference and the local regulatory floor.
- How does multi-sig actually work when my CEO is offline?
- Approvals expire after a configurable window (default 24h). If quorum isn't reached, the payment is voided and re-queued. The agent can be configured to fall back to a delegate signer (e.g. controller + CFO instead of CEO + CFO + controller) after a configurable timeout, but that fallback path is itself policy and recorded on the ledger.
- What happens to the audit trail if I rotate the principal's WebAuthn key?
- Historical signatures stay verifiable forever — the public JWKS for the previous key version is retained and served at /.well-known/jwks.json keyed by `kid`. Rotation creates a new key version; existing mandates continue to verify against the version they were signed under.
- Does this work for non-US entities?
- Resource and payment availability depends on account eligibility, provider configuration and the selected route.
- Can I export the ledger for Security review or PCI evidence collection?
- For treasury workflows, payment and refund options depend on the configured provider, route and recipient. Confirm eligibility, fees and settlement estimates before execution; no measured speed or savings are promised.
Ship this agent today.
Provision a wallet, attach a verified principal, set caps, plug into your LLM via MCP. Setup depends on account and provider configuration.