Library · Payment orchestration · How to run this
ACH and card approvals are different piles
ACH approvals and card approvals are separate rails. Mix % = rail ÷ (ACH + card). Gap pp = |ACH share − card share|. Type both counts.
Pair: ACH vs card approval on Orchestration. Prenote: ACH prenote lag. Returns: ACH return vs card refund.
What you type
ACH approvals — approved ACH auths in the window (gateway / CRM).
Card approvals — approved card auths in the same window.
ACH share = ACH ÷ total. Card share = card ÷ total. Gap = absolute difference in points. Route or price rails when one pile owns the book — do not invent a mix chip.
What not to do
Do not invent mix %. Do not fold ACH returns into approvals. Do not mix prenote holds into the approval count. Do not treat network “typical ACH share” as your book.
Related: Orchestration, ACH prenote lag, ACH return vs card refund, first-try vs net.
Procedure
- Type ACH approvals and card approvals.
- Read ACH share, card share, and gap.
- Route or price rails when one pile owns the book.
Failure modes
- Inventing mix %.
- Folding ACH returns into approvals.
- Mixing prenote holds into the approval count.
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
- ACH vs card approval mix
- ACH share = ACH ÷ (ACH + card); gap pp is the absolute share difference.
Work with us — We run this job on your accounts. Services
FAQ
- Is this ACH prenote lag?
- Sibling ACH clock. [ACH prenote lag](/manuals/seamless-ach-prenote-lag) delays first ACH cash. This page is approval share ACH vs card in one window.
- Is this ACH return vs card refund?
- Different rail pain. [ACH return vs card refund](/manuals/ach-return-vs-card-refund) is bounce vs card refund. This page is approved volume mix by rail.
- What mix % should I invent?
- None. Type ACH approvals and card approvals from the gateway / CRM for the same window.