Skip to article
ecomservices.io
Payments · How to run this
LedgerReconNot on this page yetFeesCalculatorSettlementCalculatorReservesCalculatorStatementsEntitiesNot on this page yetCommerce reconNot on this page yet

Library · Payments · How to run this

SeamlessChex refund miss is not Spreedly refund miss

How to run thisPayments3 steps
CalculatorSeamlessChex refund-fail share · Calculator lives in the articleOpen

Pull one SeamlessChex ACH refund batch. Count failed refunds. Divide by submitted refunds. The quotient is SM refund-fail %.

Pair: Refund-fail share on Payments. Spreedly twin: SP refund-fail. Cutoff twin: batch-cutoff miss.

Batch counts

Failed refunds — SeamlessChex refund requests that errored, declined, or bounced in the ACH refund batch.

Submitted refunds — Refund requests pushed through SeamlessChex in that same ACH refund batch.

SM refund-fail % = failed refunds ÷ submitted refunds × 100. When SM refund-fail % fattens, chase ACH return / settle state on that SeamlessChex seat before you invent a chip.

Hard stops

Do not invent SM refund-fail %. Do not paste a Spreedly refund CSV into SeamlessChex boxes. Do not treat batch-cutoff misses as failed refunds. Do not merge MIDs when one SeamlessChex seat owns the fail pile.

Related: Payments, SP refund-fail, batch-cutoff miss, retry-success.

Procedure

  1. Type refund fails and refund attempts.
  2. Read SM refund-fail %.
  3. Chase ACH return / settle state when SM refund-fail % is fat.

Failure modes

  • Inventing SM refund-fail %.
  • Loading Spreedly refund rows into SeamlessChex boxes.
  • Folding batch-cutoff misses into refund fails.

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

SM refund-fail %
Refund fails ÷ refund attempts × 100 on one SeamlessChex ACH refund batch.

Work with us — We run this job on your accounts. Services

FAQ

Is this Spreedly refund-fail share?
SeamlessChex ACH refund batch vs Spreedly vault/route cut. [Refund-fail share](/manuals/spreedly-refund-fail-share) stays on Spreedly. Failed / submitted refunds never leave SeamlessChex here.
Is this SeamlessChex batch-cutoff miss?
Refund misses vs batch-cutoff misses. [Batch-cutoff miss](/manuals/seamless-batch-cutoff-miss) ratios late batches. This page ratios failed refunds ÷ submitted refunds.
What SM refund-fail % should I invent?
None. Pull failed refunds and submitted refunds from the same SeamlessChex ACH refund batch.