Library · Payments · How to run this
Cancel in CRM is not a void
Sticky-class CRM cancel stops the profile. It is not a gateway void. An open auth can still capture after CS said cancelled. Type cancels and post-cancel captures in the same window.
Pair: Post-cancel capture on Payments. Hold death: auth expiry / re-auth. Void vs refund clocks: auth / capture / settle. MIT words: pause vs skip vs cancel.
What you type
Cancels — CRM profiles cancelled in the window (MIT stopped in CRM).
Post-cancel captures — captures on those profiles after the cancel timestamp.
Capture share = captures ÷ cancels. Void open auths when cancel fires — do not invent a “good” void %.
What not to do
Do not treat CRM cancel as a void. Do not invent a void rate. Do not leave open auths when cancel macros fire. Do not mix refunds into this capture count.
Related: Payments, auth / capture / settle, auth expiry / re-auth, pause vs skip vs cancel.
Procedure
- Type CRM cancels for the window.
- Type captures after those cancel timestamps.
- Void open auths when cancel fires.
Failure modes
- Treating CRM cancel as a void.
- Inventing a void rate.
- Leaving open auths when cancel macros fire.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Post-cancel capture
- A gateway capture that posts after CRM cancel. CRM cancel is not a void unless the open auth is closed.
Work with us — We run this job on your accounts. Services
FAQ
- Is this auth expiry?
- Related clock. [Auth expiry / re-auth](/manuals/auth-expiry-reauth) is hold death before capture. This page counts captures that landed after CRM cancel.
- Does CRM cancel void the gateway?
- Not always. Cancel in the CRM stops the profile. An open auth can still capture unless you void.
- Can I invent a void success rate?
- No. Type cancels and post-cancel captures. We invent none.