Use case · Financial · OI-500
Bots at the payment boundary.
Money is the one action you cannot un-take. A refund clears, a transfer settles, a payout lands — and an agent issuing them at machine speed can drain an account before a finance team finishes its morning coffee. Every action through the Stripe connector is authority-bound: tokens are single-use and TTL-bounded, replay is refused at the gate, and audit-ready evidence falls out of the runtime as a side effect. The 8-category Financial Operations domain is the vocabulary.
01 · Irreversible by default
An API key that can refund one charge can refund all of them.
A support agent wired to issue goodwill refunds holds a credential scoped to refunds — not to this refund. Replay a request, loop a workflow, or fall for a prompt injection, and the same valid key moves real money it was never meant to move. Intended scopes each Authority Token to the originating charge, bounds it to a short TTL, and refuses any reuse at the Stripe boundary. The token authorizes one action, once.
$12.00 refund to the original customer and a $12,000.00 transfer to a new payee are the same Stripe call shape. Intended sees the amount, the destination, and the deviation from your declared AP workflow — and raises the composite risk score before either clears.02 · The OI-500 surface
Every financial action resolves to one of 8 canonical intents.
The Financial Operations domain (OI-500) covers the full money surface — from payables and payroll to treasury and tax — so the same gate that governs a refund also governs a payroll run or a treasury sweep.
Accounts Payable
Accounts Receivable
Billing & Invoicing
Payroll
Treasury & Cash
Budgeting & Planning
Procurement
Tax & Compliance
03 · What gets gated
Refunds, single-use
Refund tokens are scoped to the original charge ID and TTL-bounded. Reuse, or a refund exceeding the original amount, is refused at the Stripe boundary.
Invoice & payout approvals
Bot-driven AP approvals run through conformance scoring against your declared approval workflow. A payout to an unrecognized payee deviates from the sequence and escalates.
Subscription lifecycle
Creation, modification, and cancellation are token-gated; the full lifecycle is visible and reconstructable from the audit chain.
AML / SAR signal
Out-of-pattern actions raise the composite risk score before they execute — a continuous control, not a post-hoc finding handed to an examiner months later.
04 · Evidence as a side effect
Receipts, by construction.
You do not build a separate evidence pipeline for finance. Every decision — what was attempted, the intent it anchored to, the risk factors that fired, the token minted or refused — is sealed and hash-linked into the audit chain. Your auditor replays it against the signed chain, with Intended nowhere in the loop; per-tenant public-key (JWKS) verification is live. That is what makes the Financial Operations surface defensible to an examiner, not just observable to an operator. See the compliance use case for the export profiles.