FIELD NOTES · ACCEPTANCE EXERCISES

Commission a capture window, not a paid badge

An equipment booking business may want to authorise funds before confirming a charge. The website must distinguish money held from money captured. Commission an operator queue with actual expiry evidence, rather than a green “paid” badge after authorisation.

Primary evidence and claim boundaries

Stripe documents manual capture, the requires_capture state and the card capture_before field. Expired authorisations release funds; eligible methods and windows differ. Primary reference · Read 17 October 2026.

Filled acceptance example

Synthetic teaching scenario, not a client case, provider integration test or business result. Scroll the example table on narrow screens.

Synthetic bookingEvidence at reviewQueue outcome
H17: authorised AUD300capture_before=18 Oct 10:00Z; now 17 Oct 10:00Z24 h remaining; eligible for staff review, not automatic capture
H18: same amountnow 18 Oct 10:00Z; expiry reachedStop capture path; reconcile current provider state
H19: approved capture AUD240authorised 300; ordinary single partial captureCapture240 proposal; remaining 60 released under documented flow
H20: method/window unknownNo capture_before or supported-method evidenceDo not promise a seven-day hold

Practical handover procedure

  1. Agree cancellation, capture approval and customer wording with the merchant. Keep the provider state, authorised amount, capturable amount and final captured amount separate.
  2. Build a queue sorted by actual expiry with a warning margin chosen by operations. Exercise just-before, exactly-at and after-expiry inputs in UTC; display the local time separately.
  3. In the authorised supplier test account, verify a normal capture, a partial capture and an expired hold against provider records. Record staff approval and reconciliation evidence.

Interpret the outcome

At the declared review instant H17 has 24 hours, while H18 must leave the capture-ready queue. A timer does not extend the provider authorisation. The proposed 240 is a merchant instruction requiring its own execution record; this worksheet has not charged anyone.

Acceptance decision

The operator must be able to identify an expired hold without reading logs or assuming a universal window. Verify captured/released amounts and show unresolved settlement separately.

Limits and unverified work

Hypothetical booking and timing only. No financial action, eligibility decision or extension was performed. Multicapture, overcapture and method-specific arrangements require separate provider evidence.

Download the filled bilingual acceptance record — Contains these inputs, steps, expectations and limits. This is a teaching record, not an executable integration.