Library · Payments · How to run this
eCheck return share is not ACH return share
Authorize.net can mark an eCheck accepted and still take a bank return later. Bounce share % = returned eChecks ÷ submitted eChecks × 100. Type both.
Pair: eCheck return share on Payments. Argyle ACH path: ACH return share. Card book: void vs refund mix.
What you type
Returned eChecks — eCheck transactions that came back from the bank after submit in the Authorize.net settle window.
Submitted eChecks — eCheck transactions you sent in that same settle window.
Bounce share % = returned eChecks ÷ submitted eChecks × 100. Tighten prenote / account checks when the bounce share is fat — do not invent a bounce chip.
What not to do
Do not invent bounce share %. Do not fold card declines into returned eChecks. Do not count voids as bank returns. Do not blend every gateway seat when one MID owns the bounce.
Related: Payments, ACH return share, void vs refund mix, partial capture gap.
Procedure
- Type eCheck returns and eCheck attempts.
- Read return %.
- Fix bank / account validation when return % is material.
Failure modes
- Inventing return %.
- Mixing card declines into eCheck returns.
- Treating voids as eCheck returns.
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
- eCheck return share %
- eCheck returns ÷ eCheck attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this ACH return share?
- Different processor book. [ACH return share](/manuals/argyle-ach-return-share) is Argyle ACH returns ÷ ACH attempts. This page is Authorize.net eCheck returns after accept.
- Is this void vs refund mix?
- Card-side Authorize.net grain. [Void vs refund mix](/manuals/authorize-net-void-vs-refund-mix) counts voids vs refunds. This page is eCheck bounce share.
- What bounce share % should I invent?
- None. Type returned eChecks and submitted eChecks from the same Authorize.net settle window.