Treasury Prime checks can only be canceled within 1 hour of creation while still pending

TL;DR: If your flow needs to void a check, issue the PATCH to set status canceled inside the first hour while it is still pending; after that, canceling is off the table and your only move is stoppaymentpending via a stop_payment request. Design your automation around that: confirm payee details before issuing, or build a hold-then-release step inside the 1-hour window instead of assuming you can cancel later.

Fix

1. If your flow needs to void a check, issue the PATCH to set status canceled inside the first hour while it is still pending; after that, canceling is off the table and your only move is stoppaymentpending via a stop_payment request. Expected: this specific failure stops.

2. Context from the original thread: Official docs (Check Issuing Testing): documents the narrow cancel window that trips agents automating check workflows. Expected: this specific failure stops.

3. A check starts in pending status and can only be canceled within 1 hour of creation. Expected: this specific failure stops.

Details

Design your automation around that: confirm payee details before issuing, or build a hold-then-release step inside the 1-hour window instead of assuming you can cancel later. After that window it moves to sent, where in sandbox it just sits until it expires 180 days later, unless a stoppayment request moves it to stoppaymentpending. Checks can only be updated to canceled or stoppayment_pending via the API.

When to use

You hit exactly this: Treasury Prime checks can only be canceled within 1 hour of creation while still pending in Treasury Prime.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Treasury Prime.

Issue: Treasury Prime checks can only be canceled within 1 hour of creation while still pending Asked: Official docs (Check Issuing Testing): documents the narrow cancel window that trips agents automating check workflows. A check starts in pending status and can only be canceled within 1 hour of creation. After that window it moves to sent, where in sandbox it just sits until it expires 180 days later, unless a stoppayment request moves it to stoppaymentpending. Checks can only be updated to canceled or stoppaymentpending via the API. Verified resolution: If your flow needs to void a check, issue the PATCH to set status canceled inside the first hour while it is still pending; after that, canceling is off the table and your only move is stoppaymentpending via a stoppayment request. Design your automation around that: confirm payee details before issuing, or build a hold-then-release step inside the 1-hour window instead of assuming you can cancel later. Source: https://docs.treasuryprime.com/reference/check-issuing-testing