Standard card
Under the limit. Approved.
A $5,000 monthly limit approves the expected $200 bill. It also approves a $2,500 mistake, because $2,500 is under the limit.
Pay GuardrailA ContextECF Mode
Cards that only pay when the business context says they should.
Pay Guardrail gives every vendor its own payment card and checks each charge against how the service is used, what was agreed, and who approved it before money leaves your company.
Now in private beta, starting with Microsoft and GitHub spend.
Vendor credential
Microsoft
Incoming charge
$2,500
ReviewExpected bill$200
Card limit$5,000
Usage signalBelow plan
DecisionOwner approval required
The gap at the payment rail
Procurement approved it once. The payment rail never asks again.
Your company has budgets, contracts, approval workflows, and renewal calendars. But when a vendor actually charges you, none of that is consulted. The card just pays.
A subscription keeps billing after the team stops using it. A trial quietly converts. An unrequested add-on appears. Spend analytics finds the problem weeks later—after the money is gone.
Limit versus context
A virtual card with a spending limit isn't enough.
Guardrail Card
Outside the context. Reviewed.
The $200 bill goes through. The $2,500 surprise gets stopped or sent to the owner for review.
A limit sets the maximum you could lose. Context decides whether the charge should happen at all.
How it works
One governed decision at the moment money moves.
01
One card per vendor
Each vendor gets its own locked payment credential, so one vendor's problem can't spread to another.
02
Business context
Usage, agreements, owners, approvals, and past spend are assembled into a governed view of the vendor.
03
A decision on every charge
Pay Guardrail approves, declines, or sends the charge to the right owner for review—in real time, based on policy.
04
Proof for every decision
Every approval, decline, and override is recorded with a signed evidence dossier explaining why the money moved—or didn't.
Four jobs · one enforcement point
From signup to renewal, policy stays attached to the payment.
Signup governance
Decide what you sign up for before it becomes unmanaged recurring spend, with an owner and budget from day one.
Unauthorized subscription watch
Catch rogue signups, shadow subscriptions, trials that turn into paid plans, and charges nobody knowingly approved.
Right-sizing
See where you're paying for more plan, seats, or support than you use—and decide what to do about it.
Lifecycle risk
Stay ahead of renewals, end-of-life dates, and vendor-driven price changes that create avoidable cost.
Built for agent spend
A token and a limit say an agent may spend. They don't say this purchase still fits its purpose.
Pay Guardrail is being built to check that each agent purchase still matches the business intent behind its authority—and to prove it.
Recurring SaaS spend is where we start. Governing spend by people, workflows, and AI agents is where we're headed.
Works with what you use
The decision and evidence layer—not another card program.
Pay Guardrail is designed to sit between your business context and the payment, across existing card programs and emerging payment rails.
Where we are today
Private beta, with careful enforcement.
In beta: vendor-locked virtual cards, Microsoft and GitHub usage monitoring, real-time charge decisions, manual override, full audit trails, and signed evidence dossiers.
Next: more vendors, deeper financial context, and approval workflows. Design partners help decide the order.
Our approach: new rules start in alert-only mode, so you can see what would have been blocked before anything is enforced.
Who it's for
Finance and controllers who feel recurring vendor spend drifting.
CIOs and IT finance managing SaaS, cloud, and seat sprawl.
Procurement leaders who want negotiated policy enforced at the point of payment.
AI platform teams that need to give internal agents controlled spending power.
Part of the Enterprise Context Fabric
One Mode. One shared, governed context.
Pay Guardrail is one Mode in the ContextECF family: focused applications that share a single governed view of your company's vendors, people, agreements, usage, and approvals. It is the first one that acts at the moment money is about to move.
Read the Fabric storyFAQ
The practical questions.
Will this block legitimate charges?
New rules start in alert-only mode, and every decision can be overridden with a recorded reason, so finance keeps control without reviewing every charge.
Do we have to switch card providers?
No. Pay Guardrail is designed to sit above your payment rails, not replace them.
What happens when a charge is declined?
The right owner is notified, the evidence is recorded, and the vendor can retry once the charge is approved.
How is this different from SaaS management tools?
SaaS management tools tell you what you spent. Pay Guardrail decides whether a charge should go through, before it's paid, and keeps the proof.
Private beta
Stop paying for spend nobody would approve.
We're onboarding a small group of design partners with hands-on setup.