For finance teams
A policy of record. A gate before every click. A report you sign.
Your agents, or your vendors’ agents, are about to pay. Enruta lets them pay only inside a policy you signed, interrupts a person only where the policy says so, and leaves one verifiable record per payment, so the auditor’s test of your electronic evidence becomes a mechanical one.
What you hold
The rules and the signature. Enruta holds the evidence.
| Detail | |
|---|---|
| Policy, budget, approval rights | You hold the rules and the signature. Enruta enforces them twice and keeps the evidence. |
| Objects | Policy (read, write, sign), approval, consent record, the weekly reconciliation report, the compliance export |
| Interfaces | The console; POST /v0/policies; the approval page /a/{id}; exports |
| Billed by | The mandate plus approval seats. B2B payments are large and few; a deny and a step-up are free and still sealed. |
Five things
What a finance team actually buys, and the state of each.
| What | Form | Status |
|---|---|---|
| Policy of record | One signed, versioned document; the same policy compiled onto every rail | Live on Stripe Issuing; Mercury December 2026, Ramp January 2027, Bill.com read-only from January 2027 |
| The gate before the click | Decided before a credential exists; above the threshold a named person signs with a passkey | Live |
| One record per payment | Denials included; verifiable offline, chained, time-stamped | Live |
| Weekly report | One line per mandate, exceptions coded with a suggested action, signed by the controller | Live |
| Audit export | A zip with the verifier, by person, period and kind, with the consent records | Live |
Two phases
Shadow first. Then release under policy.
Turn a policy on with shadow: true and it observes: every request is decided and sealed as observe, with what an enforcing policy would have done, and nothing is interrupted. Four weeks later the report says what would have been stopped and why. Take the flag off and the same policy issues the credentials. The twelve-week read-only pilot is this first phase with a readout at the end.
How much autonomy
A named level on every policy, so the extra step is visible.
The console shows the level at the top of every policy: which fields set it, what a person still signs. One company can run three agents at three levels in one console.
| Level | Meaning | Example |
|---|---|---|
| L2 | A locked target: merchant, category, time fixed in advance | The travel agent: one night, one city, under $300 |
| L3 | Autonomous inside the boundary, a person beyond it | The procurement agent: $200 a payment, a person above $150 |
| L4 | Autonomous for the scene | Payments to verified suppliers under a cap, nobody in the loop |
When something goes wrong
Pause the agent. Revoke the consent. Every action is a record.
A controller pauses any agent in one click; every later request is denied and the pause is a sealed record. A consent revoked stops new mandates and leaves a signed trail; a refund above the policy’s threshold needs a person’s signature like a payment; a cleared amount that differs from the authorized one raises a candidate reversal and a dispute packet.
Price
Per mandate, plus approval seats. Never a percentage of the flow.
| Mandated flow a year | Annual | Mandates included | Above that |
|---|---|---|---|
| Up to $10M | $24,000 | 5,000 | $0.25 a mandate |
| Up to $25M | $40,000 | 15,000 | $0.25 a mandate |
| Up to $100M | $80,000 | 50,000 | $0.25 a mandate |
Approval seats, the policy signature and the auditor readout on every band; the console, the weekly report and the exports included. Full sheet on the pricing page.
Start with the read-only pilot; release under policy when the report says so.
A small number of finance teams and agent vendors are shaping the first records with us. If your agents already pay, or are about to, write to us.
hello@enruta.ai