A timed-out refund should not become two refunds.
A payment provider receives a refund request, but the acknowledgement is lost. The agent wants to repeat it.
All use casesMake the boundary explicit.
Keep the original logical operation identity and durable attempt. Record the unknown outcome and reconcile through a provider query or supported idempotency mechanism before considering another effect.
An unresolved operation does not automatically create a second refund. The original outcome remains attributable when evidence arrives.
Inspect the decision.
Record the provider’s confirmed original refund.
Ready to evaluate
No external action
Select a variation and inspect the local example. This demonstration does not call a model or connect to a business system.
If the provider cannot establish the outcome, retain an unresolved case for review rather than claim exactly-once delivery.
The controls behind the workflow.
Explore the capabilities that compose around this task, rather than treating each step as a separate product.
Related ways to use DriftGate.
Resolve the complaint. Control the refund.
A fictional food-delivery platform uses an assistant to resolve a missing order. A customer requests more than the eligible refund or asks for a different payment destination.
Keep your support agent focused on support.
A shopping assistant is steered away from product and order questions toward unrelated coding or repeated expensive generation.