See what an AI-initiated payment packet looks like
When an AI agent initiates a payment, reviewers need to see exactly what happened — the agent identity, instruction context, policy checks, approvals, and execution evidence.
Why AI-initiated packets include additional fields
Standard payment evidence captures what checks ran and whether the payment was approved. When an AI agent initiates the payment, reviewers also need to know which agent acted, what instruction triggered the action, and what authority the agent had at decision time.
Kontext adds initiation source fields to every evidence packet automatically — no additional integration required. The same packet format works whether the payment was initiated by a human, workflow, API, or AI agent.
Sample AI-initiated evidence packet
This packet shows a $48,200 USDC vendor payout initiated by treasury-rebalancer-v2. Every field is captured automatically.
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
Required fields for AI-initiated payments
- Initiator type (human, workflow, API, or AI agent)
- Agent ID or service identity
- Instruction context (task, batch, or prompt reference)
- Approval chain with authority and timestamps
- Policy trace — rules evaluated and results
- Execution metadata (transaction hash, chain, settlement)