ACTEX / Pay / How It Works

How it works

Your AI agent tries to buy cloud credits. The checkout gets stuck.

Nobody knows the status. Support gets pulled in. Someone has to untangle what happened, whether the charge went through, and who approved it.

ACTEX prevents that. Every agent purchase flows through five objects that recover automatically, resolve exceptions without escalation, and leave a clean record that proves exactly what happened.

The five-step flow

From stuck checkout to clean, provable record.

Contract Result Verification Receipt Casefile
  1. Contract
  2. Result
  3. Verification
  4. Receipt
  5. Casefile
1

Contract

The rules your agent must follow — budget limits, approved sellers, and what counts as success.

Without a contract, agents buy blind. With one, violations are caught before money moves.

2

Result

The structured outcome of what the agent actually did — what it bought, from whom, and at what price.

No more digging through logs. The result is a clean, machine-readable record of the execution.

3

Verification

An automatic check that the result matches the contract — did the agent stay within bounds?

If the checkout got stuck or a policy was violated, ACTEX catches it here and recovers automatically.

4

Receipt

The final, settled record that links the contract, result, and verification into one reference.

Exceptions are resolved without support tickets. The receipt closes the loop.

5

Casefile

A portable proof bundle you can export and hand to Security, Finance, or Audit.

No platform access needed. Anyone can verify what happened offline, from the exported file.

Under the hood

How recovery actually works

When a checkout gets stuck — a policy violation, a timeout, a merchant error — ACTEX does not just log the failure. It catches the exception at the verification step and attempts recovery automatically:

  1. Detect. Verification compares the result against the contract. If something is out of bounds, it flags the violation.
  2. Reroute. ACTEX retries the operation within the contract's guardrails — different merchant, adjusted parameters, or a safe fallback path.
  3. Settle. Once the retry succeeds (or exhausts options), ACTEX finalizes the receipt and attaches all evidence — original attempt, recovery path, and final outcome.

The contract defines what "within bounds" means — budget limits, approved sellers, and acceptable fallback actions. Recovery never goes outside those rules.

The result

Stuck checkouts recover. Exceptions resolve. Clean records prove it.

Recovered automatically

Policy violations are caught, retried within bounds, and settled — no human needed.

Resolved without escalation

Returns, refunds, and disputes are handled end-to-end. No support tickets, no status calls.

Clean record proves it

Export the Casefile and verify offline. When someone asks "what happened?", the answer is already packaged.

Ready to try it?

Create your first contract and see the full flow in under five minutes.