Use Case
Incident reconstruction for payment operations
When a payment is flagged or goes wrong, you need to reconstruct exactly what happened — fast. Kontext gives you the complete decision context in seconds.
Typical risks
- Incident reconstruction takes hours of log-diving across multiple services
- No single source of truth for what checks ran on a flagged payment
- Approval chains are reconstructed from chat logs and memory, not structured records
- Post-incident reports lack verifiable evidence, relying on narrative assertions
What Kontext captures
- Complete decision context for any payment — searchable by transaction hash, agent, or time range
- Immutable timeline of screening checks, approvals, and execution in sequence
- Incident case packet export in seconds, not hours of manual assembly
- Tamper-evident proof that the audit trail hasn't been modified after the fact
- Structured evidence that connects the decision, the checks, and the outcome
Evidence output for an incident review
Every flagged payment produces a complete case packet for review.
Payment Decision Packet
CompliantPayment Summary
Amount
$48,200 USDC
Type
Vendor payout
Corridor
US → EU (Base)
Timestamp
2026-03-21 09:14 UTC
Initiation Source
Initiator type
AI agent
Agent ID
treasury-rebalancer-v2
Instruction ref
payout batch #A-449
Policy Checks
Counterparty allowedPassed
Threshold exceeded → dual approval requiredTriggered
Daily volume limitWithin limit
Sanctions Screening
OFAC/SDN checkClear
SDN v2026.03.21 · Checked at 09:14:02 UTC · 38ms
immutable logpolicy versionscreenedinitiation sourceexportable