Use cases
Each one replaces chat messages and spreadsheets with a single governed record. Every release is approved by a named person, or released under a standing rule a named person approved.
Pain today Payout approvals run through chat messages and spreadsheets. FX is checked by hand before each batch.
What changes The send flow drafts the payout, screens it and routes it by amount threshold. The FX reference rides on the draft.
Human control Every release is approved by a named person. Two-tier approval applies above a set threshold.
Surfaces · send workflow template · Payment Core API · evidence events
Pain today Incoming settlements arrive without clear reference matching. Reconciliation is manual.
What changes The receive flow matches inbound funds to references and queues exceptions.
Human control A named person confirms every proposed posting. Unmatched items route to finance.
Surfaces · receive workflow template · reconciliation · signed webhooks
Pain today Three entities, three sets of statements, nightly manual reconciliation.
What changes Per-entity accounts with segregated records and an exception queue tiered by amount.
Human control A finance lead approves exceptions above threshold.
Surfaces · accounts · reconciliation workflow · control plane roles
Pain today Building approval logic, evidence trails and FX handling in-house takes months of engineering.
What changes Connect through REST and webhooks. Approval and evidence come from the control plane.
Human control The approval chain is configured by the customer. Empty approval chains are rejected.
Surfaces · REST API · OAuth · signed webhooks · live
Pain today Staff prepare payout batches by hand and chase missing documents.
What changes An agent reads balances, drafts payouts, classifies transactions, collects documents and submits for review.
Human control The agent cannot approve or release. Every controlled write needs named approval and IP restriction.
Surfaces · Next MCP · live · read + draft