FOLLOW ONE APPROVAL
Many agents.
One approval.
Follow one fictional $10 payment through a lost reply, an Agent handoff and a restart. The original approval stays in view.
See the Agent handoffPayment control for AI agents
Delegate the work.
Keep control of the money.
HALTSEAL prevents one approved payment from becoming two across agent handoffs, retries, and connected payment paths.
Free Workspace Sandbox. Sign in and create a company.
No card required. Live payment control requires qualification.
Scott Lee in ACM QueueRead the founder’s article
RELEASE CONTROLSIMULATED
One payment. One authority.
Original unresolved. Backup on hold.HOLD
AUTHORIZED$10MOVE-1042 · USD
RESERVED$10Original may still settle
BACKUP ELIGIBLE$0No second release
BACKUP PATHProvider B
HOLD · A timeout does not restore capacity.
Fictional example. No live payment calls. An ACCEPT here sends nothing. It shows conditional eligibility only, without reserving capacity.
HOW IT WORKS
Three checks.
Before money moves.
01 / ONE SHARED APPROVAL
Agents change.
The approval stays.
Your company’s approval, reservations and payment history stay with the same obligation across Agents, retries and connected payment paths.
const obligation = {
id: "MOVE-1042",
authorized_minor: 1_000,
currency: "USD"
};
// Different request.
// Same capacity.Release attempts
ILLUSTRATIVEProvider AMOVE-1042 · original attempt
OPENMay still settle
Provider BMOVE-1042 · backup attempt
HOLDCapacity reserved
New request IDMOVE-1042 · same obligation
HOLDSame reservation
Worker retryMOVE-1042 · release boundary
HOLDOriginal unresolved
EVIDENCE CHECK
ORIGINAL ATTEMPT
MOVE-1042 / provider_a / attempt_01
SELECT AN OBSERVATIONHOLD
No response is not proof of no effect.
RESTORATION CONDITION
exact_original.cannot_create_effect02 / RESOLVE THE ORIGINAL
A lost reply
isn’t a failed payment.
Agent B can take over the work. The original may still pay, so its amount stays reserved until authoritative closure.
03 / CHECK BEFORE RELEASE
Original closed.
Fresh approval required.
Authoritative closure can restore capacity. The exact replacement still needs fresh financial approval and a current release check.
RELEASE DECISION
HOLDOriginal unresolved
EXACT ATTEMPTProvider B · $10 USD
Original openCapacity reserved
Many agents.
TRY THE WORKFLOW
Take over the work.
Keep the limit.
Open a prepared $10 Sandbox. Change the Agent or payment path, recover the original and inspect the record.
Try the prepared demoKeep what already works
Keep your banks. Keep your payment stack.
Banks, ERP and payment platforms keep their roles.
ILLUSTRATIVE ARCHITECTURE
Your stack. One release boundary.
Original unresolved$10 reserved $0 available
- ERP / AP
- Platforms & agents
BEFORE RELEASE
HALTSEAL
Shared release check
HOLDNo second release
- Payment paths
- A path to account for
One obligation. Across every connected path.
Explore a logo to see where the shared check belongs.
New path. Same obligation. Same limit.
Keep the control that works.
One control governs every relevant payment path.
Define the next control.
Repair the workflow or separately qualify execution control.
As agents choose new payment paths, the same limits must still apply.
How the control fitsEvidence before authority
Follow the authority.
Inspect the evidence.
Review original approvals, agent handoffs and recovery in the separately scoped installed Sandbox evidence. SDK fixture checks are local and synthetic. Each record states its scope and limits.
More Agents.
The same company control.
Start free in Workspace. Keep one workflow’s original approval, handoffs and recovery record together.
Developer evaluation is available today. Production activation requires workflow and provider qualification.