Security
Keep payment authority under company control.
Understand how HALTSEAL separates Workspace access, Agent delegation, and financial approval. Review the controls, credential boundaries, and evidence for each supported workflow.
Free Sandbox evaluation. Financial Production requires separate qualification.
02 / Payment continuity
Keep the original approval intact.
The reviewed control profiles retain the same original obligation, approval limits and complete attempt history across supported Agent handoffs, retries and restarts. An unresolved original remains UNKNOWN and reserves its amount. An observed PAID fact continues to consume capacity.
A replacement requires authoritative evidence that the original can no longer create the payment effect, followed by fresh financial approval and validation. A new request, Agent or route cannot supply that evidence by itself.
Controlled BILL installation profile
Check the conditions again before release.
The explicitly installed release-perimeter profile requires fresh evidence before a new reservation and immediately before provider CREATE. Observed code, account, credential or gate changes, missing evidence and expiry produce HOLD. A late failure preserves an already reserved UNKNOWN attempt; original lookup and authenticated recovery remain available.
This is controlled installation evidence. Native IAM collection, provider-side fencing, hidden-path discovery and customer deployment require their own qualification. A valid host signature identifies the installed producer; it does not independently prove the host's claims or complete route coverage.
03 / Data and credentials
Know where credentials live.
Custody depends on the connection you use. Source access, Agent keys and payment approval have distinct purposes and storage boundaries.
| Connection | Credential and record custody | Authority boundary |
|---|---|---|
| Company Workspace | Clerk processes authentication. Cloudflare retains company membership, configuration and permitted operating projections, with server-side company access checks. | Company administration and access to retained views. Signing in or selecting a Production plan does not activate payment control. |
| Local BILL collector | Credentials are entered through hidden local prompts and are neither stored nor sent to HALTSEAL. Original bill/vendor responses stay in the owner's local journal and separate witness. Workspace receives signed typed observations and hashes. | Fixed Sandbox source reads. Local raw records are not encrypted by this collector. Source observations are not financial approval or bank settlement evidence. |
| Customer BILL connection | The separately enabled server connection receives the Sandbox sync token over HTTPS and encrypts it with distinct company AES-GCM keys. Encrypted original responses and the observation key remain in Cloudflare operating records. The developer key stays in server secret configuration. | Current Owner or Technical admin access and recent Workspace MFA are required for native connection operations. Fixed Sandbox authentication and data-read endpoints provide no payment, approval, cancellation or reissue operation. |
| Agent and installed host | Agent possession keys stay in external Agent clients. Financial signing and provider credentials remain in the reviewed executor's private custody. Host service credentials are separately provisioned; the browser receives neither financial signing keys nor host service credentials. | Host and verifier trust are independently pinned to one company and workflow. Uploaded evidence cannot configure that trust or activate a company. Host/root and signing-key compromise remain trusted-boundary exclusions. |
Local disconnect removes the customer connector's encrypted sync token and withdraws observer access while preserving original identifiers and history. The administrator separately revokes the original token in BILL. Connection removal, provider retention and downloaded copies have distinct lifecycles.
Disposable evaluation examples follow their inactivity limits. Confirmed installation and operating history are retained separately; deleting an example, removing a member or reinstalling code does not reset unresolved payment history. See the Privacy Notice for processing, retention, providers and deletion requests.
04 / Scoped evidence
Review evidence by environment.
Each result belongs to its recorded release, environment and test scope. Actual provider Sandbox calls and controlled provider fixtures remain separate evidence populations.
| Environment | What the record establishes | Scope and next condition |
|---|---|---|
| Browser examples and SDK fixtures | Synthetic learning and client-contract behavior. SDK v2 has its own October 7 release record. | Fixed synthetic responses. Fixture closure and PAID observations are injected. Review the SDK record. |
| Actual Increase Sandbox | The October 9 installed reference records recovery and payment-control observations against actual Increase Sandbox APIs. Later October 11 control records retain their separate scope. | One Linux host, fictional own-account USD 10, two paths both using Increase, HALTSEAL-controlled test companies. Cross-provider enforcement and customer installations are not established. Review the installed records. |
| Controlled BILL and Agent installation | Current controlled source profiles exercise original signatures, retained journals/witnesses, A-to-B handoff, lost replies, restart and release-boundary checks. | Provider effects and test custody are controlled. A genuine BILL source read establishes a source observation, separately from financial approval and native payment execution. Request exact release records. |
| Customer installation and real-money operation | External customer acceptance remains NOT_PERFORMED. Native BILL payment execution remains NOT_QUALIFIED. Real-money Production remains NO_GO. | Actual customer paths, permissions, custody, independent review, recovery and operating authorization require separate evidence. Review the qualification conditions. |
Supporting records identify the date, fixed source, environment, scenarios, observations and remaining conditions. Historical verification does not renew current access or permit a new payment. Test counts are not combined across releases.
These records do not establish an availability percentage, independent security certification, complete customer route coverage or regulatory compliance. The Evidence page preserves the published records and their individual limits.
05 / Customer qualification
Qualify your deployment.
Start with one agreed workflow. Qualification binds the actual company, original approval, installed release and payment paths to evidence from that environment.
- Define the scope. Identify the source obligation, company, supported accounts and execution paths, including known manual, portal and alternate-credential routes.
- Verify access and custody. Check deployed company roles, required MFA, source consent, issuer authority, Agent keys and host/verifier trust. Inspect actual permissions and environment separation.
- Rehearse failure and recovery. In an agreed non-production environment with an independent mechanism preventing real funds from moving, observe lost replies, handoff, restart, original recovery and replacement against the same retained history.
- Review the exact deployment. Retain independent findings and retest, confirmed path enforcement, recovery/incident ownership and customer acceptance. Host loss, joint-history rollback and independently usable external credentials need explicit treatment.
- Authorize operation separately. Define supported scope, data handling, retention, recovery responsibilities and operating commitments in the applicable written agreement before live deployment.
A declaration, connection screenshot, signed observation or passing source test cannot establish every path's enforcement. Website publication and a scoped Sandbox result grant no financial Production authority.
06 / Review and disclosure
Contact and disclosure.
Review your security requirements.
Contact scott@haltseal.com with a non-confidential description of your workflow and the evidence you need. Agree on scope and a secure exchange channel before sharing payment credentials, private keys, financial account details, production secrets or customer records.
Report a security issue.
Send a minimal, redacted report to scott@haltseal.com with "HALTSEAL security report" in the subject. The Responsible Disclosure Policy defines research scope and good-faith reporting. The current contact file is security.txt.
Public website, demonstrations and optional AI guide
Public website
HALTSEAL Inc. operates HALTSEAL's public website. Public pages provide product information, optional review details and synthetic learning. Private Workspace source connections have the separate boundaries described above. The Legal Notice identifies the operator and registered office.
Demonstration and browser behavior
The browser demonstration uses synthetic information and predetermined scenarios. It initiates no real payment, calls no live payment provider and sends no demonstration inputs to a remote AI model. Theme preferences stay in your browser. Inquiries use Contact or email, separately from demonstration inputs.
SDK sandbox and prepared demo
The SDK sandbox sends real HTTP requests through the published client to fixed synthetic fixtures. Short-lived session credentials, bounded requests and call limits constrain the exercise. The fixture service has no access to the retained payment kernel, issuer keys, customer accounts or payment providers. The prepared shared demo has its own isolated, expiring synthetic session. Its login provides no access to a company Workspace or financial authority. See Sandbox privacy details.
Optional AI guide
Hana is an AI-generated guide powered by Anam for public product questions. It loads when you open the guide and starts a conversation when you choose its start button. Microphone access requires browser permission; camera and payment permissions remain disabled. Closing the guide ends its connection.
The guide has no payment authority or access to your payment systems and does not make ACCEPT, HOLD or REFUSE decisions. It can make mistakes. Keep questions non-confidential and confirm customer-specific details with Scott. The Privacy Notice explains provider processing and possible conversation records.
Configured authentication and email providers process verification and welcome messages. Their processing and deletion limits are in the Privacy Notice. Source regression checks remain separate from a witnessed deployed signup or mail-delivery check. No published availability commitment is established for these evaluation interfaces.
Explore the workflow in a free Workspace Sandbox.
Start free in Workspace