HALTSEAL
Start free

Payment control for AI agents

Change the agent.
Keep the authority.

One invoice. Two agents. One shared payment limit.

Take over the work. Test the next request. Or follow the guided payment walkthrough.

One shared approval ILLUSTRATIVE-1042

Illustration · No money moves

One payment obligation

Invoice #1042 Example supplier

$10 USD · authorized once

Reserved
$10
Confirmed paid
$0
Available
$0
Agent A
Assigned
Agent B
Not assigned
Original · Provider A
UNKNOWN

ONE ORIGINAL OBLIGATION

Change the Agent.
Keep the original limits.

Illustrative scenario · No money moves

Follow one fictional invoice through a lost reply, an Agent handoff and a restart. No account or connection needed.

Invoice #1042 · Example only$10 USD

Original approved limit

ILLUSTRATIVE-1042
Original outcome
Not submitted
Reserved amount
$0
Agent A
Assigned
Agent B
Not assigned
Replacement request
Not proposed

A new Agent or route cannot create another approved limit.

    Step 1 of 6

    Invoice #1042 · Original limit $10

    One original approval.

    Agent A starts with the work. The original approved limit belongs to the obligation.

    What stays the same

    The original obligation, its approval and its limit remain together.

    Continue with your own Sandbox.

    Sign in when you are ready. This example carries no financial approval or installation evidence.

    Start free and keep your placeInspect recorded tests and their scope

    Only example learning progress can be saved in this browser for seven days. No account or payment data is stored here.

    Inspect original evidence

    Synthetic evidence · exact original request A-1042

    Already dispatched · may still complete

    Closure requires both facts. A timeout, a cancellation request or a no-payment observation alone is insufficient.

    • No payment occurred

      No authoritative outcome has been applied.

      Not established
    • No later payment is possible

      The original can still complete.

      Not established

    These buttons apply predefined example evidence and approval. They do not contact a provider, obtain a real signature or authorize a payment.

    Scenario activity 1 action
    1. Agent A lost the original reply. $10 remains reserved.

    Latest 32 actions in this tab. This illustrates a history; it is not an engine-produced audit record.

    Scope and preview settingsNo live execution

    Provider A, Provider B and Bank C are fictional connected paths. An unconnected bank portal remains outside real control. Live enforcement requires verified coverage, reliable evidence and operating approval.

    Decision only. No payment authority.

    Shadow ACCEPT illustrates a proposed decision. Enforcement concept ACCEPT illustrates one modeled allocation. Both send nothing. Available capacity is not release permission. The moving marker is a request, not delivered money.

    Synthetic browser illustration. Handoffs, receiving proof, restarts and decisions are modeled, not performed by the payment engine. No live payment calls.

    Inspect recorded installation tests and their exact scope.

    Continue with your own workflow

    Start with one workflow.
    Keep the authority in view.

    Free Workspace Sandbox. Sign in and create your company. No card required. Your workflow needs its own source approval and installation verification.

    Start freeRun the SDK quickstart

    Only the example learning step can continue into Workspace. Example approvals, receipts and payment state never carry over. Live payment control requires separate qualification.