PAYMENT CONTROL FOR AI AGENTS
See what happens when another Agent tries the same payment.
Free Workspace Sandbox · No card required
Start freeWhat if A’s reply is lost and B tries the same payment?
YOUR FREE SANDBOX
Continue the example. Connect your own source when you are ready.
Free to start. No card required.
Checking workspace availability…
Complete account verificationNew here or coming back? Use the same sign-in.
By continuing, you agree to the Workspace terms and acknowledge the Privacy notice.
One sample invoice. Two simulated Agents.
Continue the same learning example after sign-in.
Connect your Sandbox source when you are ready.
Start in Sandbox. Live payment control requires separate qualification and operating approval.
ONE ORIGINAL OBLIGATION
Follow one fictional invoice through a lost reply, an Agent handoff and a restart. No account or connection needed.
Original approved limit
ILLUSTRATIVE-1042A new Agent or route cannot create another approved limit.
Step 1 of 6
Invoice #1042 · Original limit $10
Agent A starts with the work. The original approved limit belongs to the obligation.
The original obligation, its approval and its limit remain together.
Elapsed time, a handoff and a cancellation request do not prove that the original cannot pay. No automatic retry follows this example.
LEARNING PROGRESS ONLY
This fictional example stays separate from your company’s source records, approvals and installation evidence.
ONE ORIGINAL OBLIGATION
Follow one fictional invoice through a lost reply, an Agent handoff and a restart. No account or connection needed.
Original approved limit
ILLUSTRATIVE-1042A new Agent or route cannot create another approved limit.
Step 1 of 6
Invoice #1042 · Original limit $10
Agent A starts with the work. The original approved limit belongs to the obligation.
The original obligation, its approval and its limit remain together.
Elapsed time, a handoff and a cancellation request do not prove that the original cannot pay. No automatic retry follows this example.
COMPANY WORKSPACE
Keep ownership with the company as people and workflows change.
Next, connect BILL and choose one invoice. Source access and original financial approval are separate steps.
These roles grant no source payment approval. Production activation requires a separately qualified scope and operating approval.
Only the specified verified email can accept this link.
Copy a reviewed configuration plan into this company's Sandbox. Original records, native bindings and reserved payment authority stay in the personal workspace.
Configuration activity is labelled with its environment. Team changes apply to the company.
COMPANY · SANDBOX
Workspace Sandbox is free and needs no card. This separate billing test uses Stripe Sandbox payments and creates no live charge. Production pricing and qualification are agreed separately.
Manage one workflow's service access while retaining its payment history.
Only a current company Owner can manage billing. Pausing service or canceling renewal preserves unresolved reservations and the original execution history.
Pause new financial commands and request cancellation at the period end. Continue original lookup and closure evidence with current installation access. Complete offboarding after every retained outcome is verified terminal.
The download is an operating readout. Preserve the original runtime stores and independently retained witness on the installed host.
COMPANY · SANDBOX · PINNED RELEASE
Your host keeps the payment history and provider credentials. A Sandbox connection check sends a key to HALTSEAL over HTTPS for fixed account reads; the installation handler does not store the key or raw account responses. Cloudflare stores signed state reports and fictional account and entity identifiers.
Withdrawing the reporting key blocks new reports and downloads. It does not revoke the provider key or stop the installed payment engine. Retained payment history stays in place. Data handling and retention
Connection security has not been checked.
Server settings are separate from independent deployment verification. Payment control is not enabled; production remains NO_GO.
Select a company and Sandbox to qualify its own installation.
Download issued, installation confirmed and sandbox API verified are separate checks. Customer application coverage requires separate review. The reference treasury workflow has its own verification below.
COMPANY TREASURY · REFERENCE WORKFLOW
The same installed runtime controls both entry points.
On a new fictional workflow, register its key and install the company engine. Then use the workflow archive's README to bind the scheduler and open the authenticated recovery console on your Linux host. Source approval remains separate. Provider credentials stay on that host. Use the treasury exercise instead of the earlier engine-only exercise below. Preserve an existing installation and create a separate reference workflow when its source binding needs review.
python3 company-treasury.py --binding treasury-binding.json install --archive haltseal-company-treasury-0.1.0a1.zip --code treasury-codeThis is a HALTSEAL-owned example using Increase's public sandbox contract. Customer installations, cross-provider paths, manual portals and production are separately qualified.
One Linux host, Python 3.11+ and OpenSSL Ed25519. Fictional Increase own-account USD 10 only. Keep code, keys and retained runtime outside Git.
umask 077
python3 haltseal-company-install.py keygen --key private/collector.pemRegister the printed public key below. Keep the private key on your host.
Download the archive and binding after registration.
python3 haltseal-company-install.py install --binding binding.json --archive haltseal-company-sandbox-0.1.0a1.zip --code code-1This earlier engine-only command creates a fresh fictional fixture. For the treasury reference application, follow its downloaded README instead. Run one chosen exercise for a new installation; retain an existing runtime for recovery.
python3 haltseal-company-install.py exercise --binding binding.json --code code-1 --run-native-sandbox --output /absolute/private/native-proofFor the treasury reference, use its README's engine confirmation and treasury report commands with the retained treasury runtime. The connection example below applies to the earlier engine-only exercise.
python3 haltseal-company-install.py confirm --binding binding.json --code code-1 --runtime /absolute/private/native-proof/runtime --key private/collector.pem
python3 haltseal-company-install.py connect --binding binding.json --code code-1 --runtime /absolute/private/native-proof/runtime --native-result /absolute/private/native-proof/result.json --key private/collector.pemThe connection check sends an ephemeral sandbox key for server account GETs. The key is not retained. API evidence expires after five minutes.
Install the same archive into code-2, then repeat confirm using code-2 and the existing runtime. Preserve the journal, witness, audit and configuration. Never run a fresh exercise to recover an unresolved execution.
WORKFLOW OPERATIONS
Reporting, recovery ownership and source payment approval stay independently checked.
Use the package README and client.py to connect the scheduler and operator requests to the same retained engine. Report every 30 seconds using watch; evidence expires after 90 seconds. Preserve the original request ID after a lost response, look up the exact original, and obtain a fresh signed source approval after proven closure.
Back up the ledger before planned maintenance. Restore requires the same host, runtime path, independent live witness, configuration pins and audit history. Old or unverifiable snapshots keep execution on HOLD. Restore never resumes execution automatically. Reinstall code into a fresh directory with the same retained runtime. Never create a qualification fixture as a repair step.
Fictional sandbox qualification only. A Workspace role or incident acknowledgement never authorizes a payment. Customer enforcement requires separate integration review and scope approval. Production NO_GO.
ONGOING COMPANY WORKFLOW
Check the signed history from the same retained installation.
Preserve the installed runtime and its independent witness. Reconcile the complete prior history after stopping the legacy executor, then follow the downloaded README to admit it into the existing journal. Every new obligation requires a signature from the separate source owner. PAID stays refused; unresolved principal stays reserved. Assign the coordinator in Workflow operations above.
Increase sandbox, own-account USD 10, one Linux host. Signed host history does not establish a customer installation or production qualification. Production NO_GO.
Withdrawing a key blocks future reports and downloads. It preserves the installation identity and native history.
ONE COMPANY · ONE WORKFLOW
Select a company workflow to review its installation and operating checks.
The server checks the exact company, workflow, accounts, routes, configuration and installed release.
These checks qualify the supported fictional reference workflow. A paid subscription, Workspace role or sandbox record does not authorize a payment or activate Production.
Execute on your infrastructure. Manage configuration, operating status and recovery evidence in HALTSEAL Workspace. Keep source approval, provider credentials and retained payment history on the installed host.
ONE WORKFLOW. EVERY RETAINED PAYMENT.
Understand the recorded outcome and the control for the next request.
Increase Sandbox · own-account USD 10 per payment · one retained Linux host. Execution and signed source approval stay in your infrastructure. Production requires separate qualification.
FIND THE AUTHORITY. FOLLOW ITS HISTORY.
Find retained authority and payment records across your company’s workflows. No Tracking ID needed.
Search the references your team already knows, including existing ID aliases. Results are limited to the retained evidence available in this company and environment.
Registration identifies a verified record. Discovery observations and IDs do not grant payment permission. Every execution requires its own exact authorization and qualified release check.
COMPANY AUTHORITY. ONE CONTINUOUS RECORD.
Follow one payment obligation across its approvals, execution attempts and paths.
Tracking identifies an obligation; it does not grant payment permission. The map shows retained evidence and disclosed coverage. Each execution still requires fresh validation of the exact payment.
ONE ORIGINAL AUTHORITY. EVERY NEXT STEP.
Your supplier payment workflow, from original approval to verified handoff.
ONE PAYMENT. ONE CONTINUOUS RECORD.
See what happened to the first payment, what is still unknown and what to check next.
No connection needed for the sample. You can bring your own invoice when you are ready.
Its record and limit stay together.
The payment may still go through.
A different Agent does not create another limit.
The original payment may still settle. Check its exact outcome before considering a replacement.
ONE CONTINUOUS RECORD
Choose one company workflow to begin.
Assisted evaluation uses the existing USD 1 test invoice. Customer enrollment requires a separate qualification.
01 / CONNECT
Choose your BILL Sandbox invoice and link its separate financial approval.
Open workflows →02 / ASSIGN & HAND OFF
Preview the change, end the previous Agent’s access and wait for the successor’s signed receipt.
Review your invoice →03 / VERIFY
Inspect the same original authority, retained payment history and independent work verification.
Review evidence →If the original payment may still take effect, another payment stays on hold. A handoff or a downloaded proof never creates a new right to pay.
RECORDS YOU CAN INSPECT
Keep original approval, Agent receipts and independent verification distinct.
Selected workflow: Choose a workflow first. Every record belongs to the company and environment shown above.
Inspect the retained original, source checkpoint and exact obligation. The original evidence screen includes the available record exports.
Inspect who received this invoice, when previous access ended, and whether the work has independent verification.
Connect your Sandbox and choose its workflow to inspect the original evidence.
Browser exercises explain the control contract. They remain separate from your company’s original approval.
Open saved examples →Exports are historical evidence. They are not a current execution permit. Payment execution and customer installation acceptance require separate qualification.
COMPANY AUTHORITY. ONE CONTINUOUS RECORD.
See what is recorded, what needs review and where payment control still needs qualification.
YOUR FIRST INVOICE
Connect your Sandbox organization, choose an invoice and keep its original record in view.
Create or select your company workspace to keep its records and access together.
Set up your companyYour company administrator connects BILL. You can inspect the retained records once the source is connected.
View company & teamPartner API access and company credential storage must be configured before connecting. Existing retained records remain available.
Get setup help →The first release supports USD ACH invoices with auto-pay off and individual approvers. Currency and the exact source are verified after selection.
ONE INVOICE. CONTINUOUS AUTHORITY.
Link the original, assign its review and keep the same authority through handoff.
Choose your BILL invoice.
Amounts belong to this obligation. They are not a bank balance.
No Agent assigned yet.
The original financial limit and UNKNOWN / PAID history stay with the original record.
Connect your original authority and enrolled Agents.
Results appear after independent evidence verification.
A payment draft will appear here after verification.
Original approval, financial limits and past outcomes remain with this invoice.
Changing Agents keeps the same Authority and Obligation. It creates no additional payment rights.
Original evidence remains available in Tracking.
ORIGINAL AUTHORITY
Retain an independently issued receipt that connects this BILL obligation to its original owner.
Workspace login and BILL read access do not make someone a financial approver. Recording a receipt creates no payment permission or financial limit.
Reading the retained original-owner receipt…
Only a company owner or technical administrator can record a public receipt. That Workspace role does not issue financial authority.
YOUR NEXT DECISION
APPROVAL & CAPACITY
A BILL approval is one source of evidence. Separate financial approval and qualified execution are still required.
Per-obligation history stays with its original record. Company totals are shown only when the shared authority and its complete scope are verified.
Review selected authority →FIND THE RECORD. FOLLOW EVERY PATH.
| Obligation / workflow | Recorded amount | Original outcome | Next request | Source evidence | Open record |
|---|
Recorded amounts are not spendable balances. Search includes only retained evidence in this company and environment.
CONNECTION DOES NOT MEAN CONTROL
See what HALTSEAL can observe, and which paths still need qualification.
START WITH THE SYSTEM YOU USE
Choose a workflow, connect its source and review the retained obligation. HALTSEAL provides the tracking ID.
Name its original path, possible alternative and the person responsible for the next decision.
SAVED WORKFLOW
Paths and decision owner retained.
Loading the current review.
Local hooks and closure evidence need technical review.
Requires separately qualified release checks and operating approval.
Local profile: synthetic own-account USD 10. Application hooks and live system coverage need separate verification.
Up to three emails in your first 14 days.
ONE PAYMENT. EVERY PATH.
Configure one workflow. Carry the same payment reference across its paths.
Configuration prepares your evaluation. Bank and provider access requires separate setup.
YOUR SYSTEMS
See the access and setup each path needs.
PLAID LINK · SANDBOX
Choose accounts in Plaid. Return here to verify access.
Account access
Not connectedPayment control for this connection
Not enabledPayment calls require a separately verified control path.Before you connect: Plaid hosts test-account sign-in. Cloudflare stores selected account details and encrypted access tokens. Revoking access blocks reads here; confirmed removal deletes those tokens and account details. Retained payment history stays in place. Data and access details
Complete the test connection in Plaid, then check the result here.
Open Plaid Sandbox Opens a new tab. Use Plaid’s Sandbox test credentials.Revoke Plaid access for this workflow? Account data will be removed from this view. Retained payment history and control rules remain in place.
This connection reads selected test account names and masked identifiers. It grants no payment authority and provides no evidence that a payment has closed. Account data and access
APPROVAL SOURCE · SANDBOX
Keep the exact bill and its approval observation attached to one retained obligation.
Approval observations grant no payment permission. Supplier execution remains on HOLD until separately qualified.
FROM EVIDENCE TO A REGISTERED RECORD
Connect the company's signed authority and exact financial approval to this obligation's original runtime.
Connect the source and complete its retained review.
The company's authorized signers approve the parent limit, delegation, exact payment and obligation membership. Your technical owner imports these into the existing runtime.
HALTSEAL shows the Authority ID after the original runtime confirms the signed relationship.
Open Authority Tracking →Use the existing BILL company-authority runtime and its authenticated registration service. Submit the downloaded request with the independently signed control package. Keep signing keys and access tokens on the runtime host. Importing authority makes no payment calls.
python3 authority_registration_client.py --endpoint http://127.0.0.1:PORT --request authority_registration_request.json --package signed_authority.json --output new_registration_receipt.json --publishUse the port supplied by your original runtime owner. The client asks for the scoped access token privately and publishes the original observer's signed tracking report. It sends no payment.
Customer BILL v3 requires an independently provisioned exact company, invoice, source contract and original owner policy. Existing USD 1 controlled records keep their original contract. Actual customer acceptance and native execution require separate evidence.
A registered tracking record is separate from current financial eligibility and verified payment execution. Native execution remains unqualified.
THE DECISION. THE REASON. THE NEXT STEP.
Review the original and alternative attempts for one workflow.
RETAINED RESULTS
Saved snapshots of the fixed USD 10 recovery exercise.
Synthetic HTTP fixtures · Browser fixture 1.0.0 / RC4 client · Separate from SDK v2 and the payment engine. No real money or provider calls.
SDK V2 · 0.2.0-rc.2
Choose a client, verify the archive and run the local recovery quickstart.
Python 3.12+ · SDK 0.2.0rc2
curl --fail --location --output haltseal_payments-0.2.0rc2-py3-none-any.whl \
https://haltseal.com/developers/payments/sdk/0.2.0-rc.2/haltseal_payments-0.2.0rc2-py3-none-any.whl
printf '%s %s\n' 'becd257048668520bec2ff13b31d62a36c14d0bd84ed65ed120b83825ed7d451' \
'haltseal_payments-0.2.0rc2-py3-none-any.whl' | sha256sum -c - && \
python3 -m pip install --no-index --no-deps haltseal_payments-0.2.0rc2-py3-none-any.whlNode.js 22+ · SDK 0.2.0-rc.2
curl --fail --location --output haltseal-payments-0.2.0-rc.2.tgz \
https://haltseal.com/developers/payments/sdk/0.2.0-rc.2/haltseal-payments-0.2.0-rc.2.tgz
printf '%s %s\n' 'da620ee9432f7d124cb67364a620efb9e42f38948f19b9895d6dafc6ee84241c' \
'haltseal-payments-0.2.0-rc.2.tgz' | sha256sum -c - && \
npm install --offline --ignore-scripts --no-audit --no-fund haltseal-payments-0.2.0-rc.2.tgzUse the pinned local fixture to exercise both installed clients.
Run the SDK v2 quickstart →The retained engine package is supplied through a scoped local review.
Review API setup →These clients are for evaluation. This workspace does not issue production API keys or enable real payments.
DEFINE ONCE. CONTINUE TOGETHER.
Name the paths. Keep the responsible people with the workflow.
YOUR CODE. ONE REVIEWABLE RECORD.
Request the private kit. Verify it locally. Connect the paths you own.
This pinned kit retains its original release documentation. New pilot sales have ended; current pricing and qualification govern new engagements. Existing accepted orders retain their terms.
Extract the approved ZIP into a private directory outside Git. Open a terminal there.
python3 kit.py doctor --language pythonpython3 kit.py reference --language python --output /tmp/haltseal-reference-01This checks the kit. Customer code is still unconnected.
python3 kit.py init --language python --workspace /tmp/haltseal-workflow-01The helper creates an unconfigured adapter, workflow input and your next command. Use fresh private paths. If you selected both languages, connect and evaluate one adapter per language. This starter begins with Python.
Engineering, operations and the budget owner review the integration map, JSON evidence and owner decision.
Your browser verifies the approved archive before saving it. A local pass does not establish production readiness.
Full integration guide →Retain current controls, complete missing evidence or request operating qualification. Optional implementation assistance is separately scoped. No pilot purchase is required to start Sandbox.
Approve only the recorded release and permitted scope. Access expires after 30 days. Withdrawal blocks future downloads; previously downloaded copies remain subject to the license.
REVIEWS & EXISTING ORDERS
New standard pilot sales have ended. Existing price, scope, payment, refund and delivery terms remain attached to your order.
YOUR ACCOUNT
Export your evaluation or clear the saved workspace.
After reading a reply, receiving an inquiry or confirming a booking, stop automated tips for that exact email.
Workspace results and outlines are removed after 180 days without account activity. Inquiry, invoice and authentication records follow their separate retention policies.
This clears saved results, workflow outlines, kit requests and download access, and scope review and historical pilot references. Contact us about submitted inquiry or commercial records.
Contact about account or privacy requests ↗