Out-of-order payment event acceptance worksheet
Fone, 28 October 2026

All revisions below are synthetic. These scenarios have not been executed as a
new database or chain test. Fill in actual results for your target integration.
Do not treat the article's source review as a passed production acceptance test.

Event | API snapshot | Local revision | Expected behavior | Actual result
paid r7 | full refund r8 | r8 | no new delivery | Not run
refund r8 | paid r7 | r6 | reject old snapshot, retry | Not run
paid r7 | paid r7 | r8 | retain newer local state, no delivery | Not run
paid r7 | partial refund r8 | r7 | apply explicit partial-refund policy | Not run
paid r7 | API unavailable | r6 | no speculative delivery, defined retry | Not run
paid r7 | paid r7, then refund races | r7 | investigate cross-system window | Not run

Capture event ID, local/platform order references, event revision, API revision,
local revision before/after, task outcome and entitlement count. Keep these records
private. Do not copy real customer data, secrets or recovery tokens into public issues.

Decisions to agree
- Which refunds block future delivery?
- What happens when access was already issued?
- Who handles a stale API snapshot or repeated query failure?
- Which downstream action has an idempotency key and an outcome lookup?

Original Fone worksheet. Copy/adapt with attribution and the scope notice retained.
