The CAST architecture is vertical-agnostic. Confirm & Pay — the accounts-payable instantiation — is where we prove it. AP is not a niche; it is the cleanest place to demonstrate the bilateral event loop and capture the first units of proof.Documentation Index
Fetch the complete documentation index at: https://docs.cast.digitalfinancehq.com/llms.txt
Use this file to discover all available pages before exploring further.
See Confirm & Pay in action
How it works, the covered controls, and the interactive walk-through live on the main site. Request a demo there.
Four reasons AP goes first
The damage is concentrated
First payment to a new vendor, a bank-account change, a rush payment, a threshold breach — a handful of triggers account for most unilateral-instruction fraud. We start exactly where the risk lives.
The loop is provable in one screen
Propose → confirm → release is the entire architectural claim, demonstrable end-to-end without downstream GL automation.
The vendor adopts nothing
The counterparty is a signer, not a tenant — a browser link, three actions, no app, no account. Adoption friction is near zero.
Every other vertical is configuration
The same architecture extends to other verticals — association and HOA payments, GPU compute financing, and institutional grant disbursement — with different event types and policies, not a re-architecture.
What the buyer evaluates
The case for AP first rests on four things a CFO already recognizes: an acute problem ($2.9B in annual U.S. BEC losses), measurable ROI (reconciliation from days to minutes), an existing budget (AP controls and fraud prevention are funded line items), and a foundation for broader CAST adoption.
How it sits with your existing systems
CAST sits alongside your ERP — not in place of it — and produces posting-ready exports with the lineage hash in the memo field. Confirm & Pay is a pre-release control: covered payments remain held until the vendor confirms the terms or an exception is reviewed. It does not replace the ERP, create seller-side ledgers, or require vendors to adopt a new system.What CAST is not
The boundaries, stated plainly.