Agentic payment security
VulSight verifies every proposed payment against the customer mandate, live state, and exact transaction before the signer can execute.
VulSight Authorization
Execution boundaryTransaction request
Authorized0xA882...11E7
Requested0x71A4...9C2E
DENY
Recipient mutation deniedPolicy decision
Every proposal receives an explicit outcome, a reason code, a scoped authorization when allowed, and an evidence ID for review.
{
"request_id": "req_1842",
"principal_id": "org_acme",
"agent_id": "invoice_agent",
"mandate_id": "md_vendor_1842",
"action": {
"type": "stablecoin.transfer",
"rail": "base-mainnet",
"asset": "USDC",
"amount": "24800.00",
"recipient": "0x71A4...9C2E"
},
"payload_hash": "0x6f2a...b901"
}{
"decision": "DENY",
"reason_code": "recipient.allowlist_mismatch",
"authorization_id": null,
"evidence_id": "evt_7f42c9",
"retryable": false,
"next_action": "return_to_principal"
}Authorization path
The agent can propose. Policy can decide. Only the customer signer can execute an approved payload.
Normalize
Verify
Enforce
Exact payload authorization
Natural-language approval is too elastic for irreversible writes. VulSight produces a scoped authorization envelope for the exact economic fields and payload the signer receives.
Any change to the recipient, asset, amount, network, expiry, or payload requires a new authorization.
Authorization envelope / Payload bound
vs-auth-7f42c9Authority separation
Keys, policy administration, approval, recovery, and emergency controls stay outside the agent runtime.
The model submits a typed action, but never receives a raw key, reusable credential, or direct path to a payment rail.
Rules outside the model evaluate the mandate, live state, and exact transaction with a deterministic result.
The signer validates a scoped authorization against the payload it receives. Any mutation requires a new decision.
Agent payment security pilot
Start with one agent, one transaction type, and one signer. VulSight maps the authority path, replays adversarial cases without moving funds, and defines the controls required for safe execution.
Trace one agent, one action, one rail, one signer, and every route that can reach execution.
Run adversarial workflow traces in shadow mode without moving customer funds.
Define the controls required to enforce safely, redesign the flow, or keep execution manual.