Stripe refund control
What we’re testing
DualKey intercepts AI-issued refund commands before they reach Stripe.
In Phase 0, DualKey runs in shadow mode: it evaluates attempted refund actions, records the policy decision, and produces a structured audit artifact without executing live Stripe actions.
No action proceeds without policy clearance. In a live deployment, flagged actions would require a second authorization step before execution.
Why this exists
Pre-execution control before money moves.
For teams operating AI-assisted customer support or billing workflows.
AI agents are increasingly being allowed to issue refunds, modify billing, adjust subscriptions, and take financial actions.
Most teams have logging. Few have pre-execution authorization.
Without a pre-execution control, incorrect refunds are only detected after the money has already moved.
DualKey introduces a second key before financial actions execute.
Boundaries
Narrow by design.
DualKey is not:
- another AI observability dashboard
- post-hoc fraud detection
- a compliance reporting tool
- a refund automation system
- a replacement for Stripe
- a customer support platform
It is a narrow authorization layer for high-risk financial actions.
Current scope
Closed validation scope
One action. Deterministic policy. Shadow mode. Structured audit artifact.
The current demo policy uses fixed refund thresholds to prove decisioning and audit output. Additional integrations are not currently active.
Contact
By invitation only.
DualKey is currently in closed validation with a small group of operators.
To request access, reply to your invitation or contact hello@dualkey.ai.