What a payment decision packet looks like
Every payment decision monitored by Kontext produces a structured evidence record. This is what a reviewer, auditor, or partner sees when they ask “what happened with this payment?”
Why evidence packets matter
When a sponsor bank reviewer, internal auditor, or enterprise partner asks about a specific payment, they need more than a transaction hash. They need to see the full decision context: what checks ran, what the results were, who approved it, and proof that the record hasn't been modified.
A payment decision packet is the structured artifact that answers these questions. It combines the payment summary, compliance checks, sanctions screening, approval chain, and a cryptographic integrity marker into a single exportable record.
Sample evidence packet
This is a representative packet for a $25,000 USDC payout on Base. Every field is captured automatically by Kontext.
Amount
$48,200 USDC
Type
Vendor payout
Corridor
US → EU (Base)
Timestamp
2026-03-21 09:14 UTC
Enforcement
Blocking mode
Initiator type
AI agent
Agent ID
treasury-rebalancer-v2
Instruction ref
payout batch #A-449
SDN v2026.03.21 · Checked at 09:14:02 UTC · 38ms
Disposition
Approved after dual review
Fallback
Blocked if approval missing
Policy version
payout-policy@2026.03
Treasury Ops
09:12 UTC
Compliance
09:13 UTC
Execution
09:14 UTC
Verification proof
digest #2,341 returned with event
Content hash
sha256:a4f2c8...7e1d3b
Packet types
Examiner, diligence, incident
Redaction mode
First6...last4 masking
SAR / erasure log
Preserved in audit trail
How Kontext creates these packets
- One integration captures payment summary, policy checks, screening results, and approval chain automatically
- Every record is cryptographically linked in a tamper-evident digest chain
- Packets export in JSON, CSV, or examiner-ready formats
- Evidence is structured — not reconstructed from logs after the fact