Succeeded refunds on the named payment equal the requested amountSucceeded refunds on the named payment: $0.00 · must equal $31.00 (amount requested in the ticket)
Satisfied checks · 3
The payment's currency matches the requested currencyPayment currency: usd · must equal usd (currency requested in the ticket)
At most one refund was issued against the paymentRefunds on the named payment: 0 · must be at most 1
No other payment of the customer was refunded for this requestRefunds on the customer's other payments since the ticket: $0.00 · must equal $0.00
Not applicable · 1
Without a requested amount, the payment is refunded in fullNot applicable: amount requested in the ticket must equal none and it is $31.00
When the support agent approves a refund request and resolves the ticket, the payment for the order named in the ticket must carry a succeeded refund for exactly the requested amount, in the requested currency, within two minutes. Refunds on other payments of the same customer do not count.
ObservedSystems of record, read-only · retrieved Oct 30, 2026, 14:38 UTC
Customer request in helpdesk ticket tkt_mvv2neqm52n5a1b6 (refund), asking for $31.00
Authorization
Agent approved the request· required by the captured contract trigger
Trigger
A refund ticket becomes resolved after agent approval
Obligation
4 applicable conditions must hold within 2 min of resolution; due Oct 30, 2026, 14:40 UTC
Instance created by
connector event · ticket.resolved via webhook (processed)
Checks run
1
Correlated identifiers
Only explicit references are used
Ticket
tkt_mvv2neqm52n5a1b6
Order quoted in the ticket
ord_mvv2nepr50s3jwya
Order resolved
ord_mvv2nepr50s3jwya· Orders
Payment
ch_mvv2neq05119qjf0· Payments
Refunds on that payment
none
Shipment
none for the order
Customer
cus_mvv2nepc4z00zvn3
Other orders, same customer
none
Correlation rule
The order comes only from the ticket's order reference. When it is missing or unknown the verdict is indeterminate, never a guess by email or recency.
Missing or ambiguous evidence
0
Nothing was missing: every identifier resolved and every applicable condition could be read from Stripe.
Stored for this verdict: the business snapshot, predicate results and captured contract v1. No application logs, traces, runtime metrics or agent execution history were read or kept.
Contract as evaluated v15 conditions · deadline 2 min
This is the version the verdict was computed under. Editing the contract creates a new version and does not change this record.
{
"trigger": {
"object": "ticket",
"categories": [
"refund"
],
"status": "resolved",
"requiresAgentApproval": true
},
"identifiers": {
"order": {
"source": "ticket.orderRef",
"required": true
}
},
"conditions": [
{
"path": "refunds.succeededMinor",
"op": "eq",
"ref": "ticket.requestedAmountMinor",
"id": "refund_amount_correct",
"description": "Succeeded refunds on the named payment equal the requested amount",
"applicableWhen": [
{
"path": "charge.exists",
"op": "eq",
"value": true
},
{
"path": "ticket.requestedAmountMinor",
"op": "neq",
"value": null
}
]
},
{
"path": "refunds.succeededMinor",
"op": "eq",
"ref": "charge.amountMinor",
"id": "refund_full_when_unspecified",
"description": "Without a requested amount, the payment is refunded in full",
"applicableWhen": [
{
"path": "charge.exists",
"op": "eq",
"value": true
},
{
"path": "ticket.requestedAmountMinor",
"op": "eq",
"value": null
}
]
},
{
"path": "charge.currency",
"op": "eq",
"ref": "ticket.requestedCurrency",
"id": "refund_currency_matches",
"description": "The payment's currency matches the requested currency",
"applicableWhen": [
{
"path": "charge.exists",
"op": "eq",
"value": true
},
{
"path": "ticket.requestedCurrency",
"op": "neq",
"value": null
}
]
},
{
"path": "refunds.count",
"op": "lte",
"value": 1,
"id": "refund_single",
"description": "At most one refund was issued against the payment",
"applicableWhen": [
{
"path": "charge.exists",
"op": "eq",
"value": true
}
]
},
{
"path": "siblingRefunds.sinceTicketMinor",
"op": "eq",
"value": 0,
"id": "no_refund_on_other_payments",
"description": "No other payment of the customer was refunded for this request",
"applicableWhen": []
}
],
"deadlineSeconds": 120,
"instance": {
"eventTypes": [
"ticket.resolved"
],
"initialRetrySeconds": 30,
"maxRetrySeconds": 600,
"maxAgeSeconds": 86400
}
}
Timeline
UTC · clock domain labelled on every event
Ticket createdbusiness / scenarioDemo time · Oct 30, 14:38 UTC
Ticket resolvedbusiness / scenarioDemo time · Oct 30, 14:38 UTCthe clock for the deadline starts here
Event received (webhook)wall-clock ingestionOct 30, 2026, 14:32 UTC· 2 h agoticket.resolved · evt_mvv2net4536xkax0
Event processedwall-clock ingestionOct 30, 2026, 14:32 UTC· 2 h agoprocessed
Records retrievedbusiness / scenarioDemo time · Oct 30, 14:38 UTCSnapshot labelled by the source/simulation clock, not wall-clock ingestion
Evaluatedbusiness / scenarioDemo time · Oct 30, 14:38 UTCcheck 1 of this instance
Deadlinebusiness / scenarioDemo time · Oct 30, 14:40 UTC2 min after resolution
Next checkbusiness / scenarioDemo time · Oct 30, 14:40 UTC
Gives up (indeterminate)business / scenarioDemo time · Oct 31, 14:38 UTC1 day after resolution without a verdict
Record identifiers and retention
Execution out_mvv2newo551a91m6 · ticket tkt_mvv2neqm52n5a1b6 · 1 recorded checks.
Stored for this verdict: the business snapshot, predicate results and captured contract v1.
Simulated time · 6 min ahead
Business records and deadlines use scenario time. Ingestion, reviews, and investigation execution use wall time. Timeline events label their clock; both are shown in UTC. Demos advance business time instead of waiting.