Security & trust
Fail-closed decisions, conserved delegation, minimum disclosure and evidence you can verify - plus an honest account of what is sandbox today, what is proposed and what is off.
The authority model
Six properties every decision has.
Deterministic authority
Language models help compile intent and write explanations. They never decide money, data, commitments or delegation. Every decision is produced by deterministic policy, envelope, delegation and approval logic.
Fail closed
If a dimension cannot be checked - no standing authority, an undeclared commitment, an unknown counterparty - the answer is not AUTHORIZED. Ambiguity never expands authority.
Narrowing only
A task, an envelope or a delegated grant can only reduce what the standing policy allows. Agents may narrow their own envelope; only the owner may widen it, and every version is append-only with provenance.
Single-use binding authorizations
A binding authorization expires, can be revoked and is consumed exactly once. Changing the amount, merchant, commitment class or agent fails the consumption guard.
Conserved delegation
Children never add up to more than the parent holds. Issuance is atomic; unspent authority returns when a child is revoked or expires.
Purpose-bound disclosure
Protected fields are released only for a necessary purpose, to a named recipient, once. Payment secrets, credentials and identity documents are never disclosable. Dry runs never return values.
Honest status
What is real, what is test, what is off.
Developer preview. Every decision is real; every payment rail runs against a test provider or a sandbox ledger. We never present a simulated capability as production money movement.
- Stripe live mode, live seller payouts, x402 mainnet and MPP production are gated OFF platform-wide.
- Authorization pricing is not activated; usage is metered in neutral units only.
- The legacy direct-card rail is retired and not offered.
- authorize · explain · outcome · revoke · approvalsAVAILABLE IN SANDBOX
- Intent compilation · authority envelopes · latest safe questionAVAILABLE IN SANDBOX
- Conserved delegation · purpose-bound disclosureAVAILABLE IN SANDBOX
- Merchant checkout via Stripe Shared Payment TokenTEST INTEGRATION
- Sandbox Credits · agent-to-agent marketplace · ledgerAVAILABLE IN SANDBOX
- x402 machine payments (testnet)TEST INTEGRATION
- MPP adapter (card SPT on Stripe test · stablecoins simulated)TEST INTEGRATION
- Authorization pricingPROPOSED
- Stripe live settlement · live seller payouts · mainnet · MPP productionFUTURE
Under the hood
Engineering controls, described accurately.
Quattrino treats agents, merchants, services and tools as untrusted by default. These are the controls that enforce it - without absolute claims and without certification we do not hold.
Agents are isolated
Buying a service never grants access to another agent’s memory, credentials, prompt, files, tools or organization. A bidirectional firewall runs on every message.
Least-privilege access
Agents hold a scoped, revocable credential - never a card, a login or a master key. Resource access is a time-limited grant for exactly the approved operations.
Payment credentials stay with the provider
Card details are tokenized and held by the payment provider (Stripe, test mode). No agent, and no model, can read them.
Idempotent, never twice
Every binding call and every execution carries an idempotency key; a retry can never authorize or charge twice. Uncertain provider outcomes are reconciled, not retried blindly.
Untrusted by default
Merchant pages, MCP tools, agents and service content are treated as untrusted input. Injected instructions are flagged and never override deterministic authority.
Tenant isolation
Every record is organization-scoped. One organization can never read or modify another’s agents, policies, envelopes, authorizations or evidence.
Append-only evidence and ledger
Authorizations, outcomes and compliance findings are hashed and immutable; sandbox money lands on a double-entry ledger. Corrections add entries - history is never edited.
Human emergency controls
Freeze all agent activity with one switch, revoke a credential or an authorization, suspend a service or disable a provider - without a deploy. Every emergency action is itself audited.
Human controls
The owner always holds the brake.
The emergency brake is one switch
The same control exists in the product; this one only illustrates it.
Agents may request authorization; every request is intersected with the standing, task and delegated authority first.
Providers and responsibilities
Quattrino is an authority and transaction-control layer.
It is not a bank, money transmitter, card network or financial institution. Regulated functions are performed by the providers below.
Payments
Stripe (test mode)
Tokenizes and holds card details; settles sandbox merchant checkout. Live mode is gated off platform-wide.
AI models
Model providers via a universal key
Classification and explanation only. Never final authority over money, access or permissions.
Transactional email provider (operator-configured)
Verification, approval requests, authority questions, security notices. Nothing is sent without a verified sender configuration. Secrets are never emailed.
How we test
Proven under attack, failure and ambiguity.
We describe categories, never exploit details.
Adversarial suites
Authentication, tenant isolation, prompt injection, schema abuse, replay, mutation, expiry and revocation of authorizations - the system must fail closed.
Financial failure injection
Provider timeouts, declines, duplicate webhooks and ambiguous outcomes are injected to prove sandbox money is never lost, duplicated or double-charged.
Live-safety gate
A dedicated suite asserts that live payments, mainnet and production settlement stay OFF and that every simulated capability is labeled as such.
If something goes wrong
Contain first, then investigate on the record.
Pause what needs pausing - an agent, an authorization, a service, a provider - reconcile sandbox money against the provider, and keep an immutable trail of who did what and when. Every emergency action is itself audited.
Responsible disclosure
Found a security issue? Report it to our security team; we acknowledge receipt, investigate, keep you updated and remediate. We do not pursue good-faith researchers who follow this process.
Honesty is a feature.
Anything simulated is labeled as a simulation - on this site, in the API and inside the product. We never present something as production when it is not.
