Library · Payments · How to run this
Void is not a refund
Voids and refunds make the reverse mix. Refund mix % = refunds ÷ (voids + refunds) × 100. Type both.
Pair: Void vs refund mix on Payments. Clocks: auth / capture / settle. ACH rail: ACH return vs card refund.
What you type
Voids — pre-settle voids / cancels in the window.
Refunds — post-settle refunds in that same window (do not fold chargebacks in).
Refund mix % = refunds ÷ total × 100. Prefer voids while unsettled when refund mix is fat — do not invent a mix chip.
What not to do
Do not invent mix %. Do not mix chargebacks into refunds. Do not treat ACH returns as voids. Do not average every MID when one owns the hole.
Related: Payments, auth / capture / settle, ACH return vs card refund, capture vs auth amount.
Procedure
- Type voids and refunds.
- Read void and refund mix %.
- Prefer voids while unsettled when refund mix is material.
Failure modes
- Inventing mix %.
- Mixing chargebacks into refunds.
- Treating ACH returns as voids.
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
- Void vs refund mix
- Share of reverse decisions that are voids vs post-settle refunds.
Work with us — We run this job on your accounts. Services
FAQ
- Is this auth / capture / settle?
- Sibling clock. [Auth / capture / settle](/manuals/auth-capture-settle) names reverse doors. This page is the count mix of voids vs refunds you typed.
- Is this ACH return vs card refund?
- Different rail. [ACH return vs card refund](/manuals/ach-return-vs-card-refund) is ACH bounce vs card refund. This page is void vs refund mix on card settles.
- What mix % should I invent?
- None. Type void and refund counts from the same Authorize.net / gateway window.