Solution skill
Treasury Prime checks can only be canceled within 1 hour of creation while still pending
Complete solution
Shows how to fix treasury Prime checks can only be canceled within 1 hour of creation while still pending. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
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.
Steps
- 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.
When to use
You are seeing this: A check starts in pending status and can only be canceled within 1 hour of creation. Use this skill when you run into "Treasury Prime checks can only be canceled within 1 hour of creation while still pending".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: 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 stoppayment_pending 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 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.
Source URL: https://docs.treasuryprime.com/reference/check-issuing-testing
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_hSQ6HBphjWHmU2Qpn4hn3g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Treasury Prime checks can only be canceled within 1 hour of creation while still pending <span>— Vectle</span></a>