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

Spreedly refund miss is not Authorize.net refund miss

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

Pull one Spreedly refund route cut. Count failed refunds. Divide by submitted refunds. The quotient is SP refund-fail %.

Pair: Refund-fail share on Payments. Authorize.net twin: AN refund-fail. Void twin: void-fail.

Route counts

Failed refunds — Spreedly refund requests that errored, declined, or bounced on the route cut.

Submitted refunds — Refund requests pushed through Spreedly on that same route cut.

SP refund-fail % = failed refunds ÷ submitted refunds × 100. When SP refund-fail % fattens, chase vault token / gateway route state on that Spreedly seat before you invent a chip.

Hard stops

Do not invent SP refund-fail %. Do not paste an Authorize.net refund CSV into Spreedly boxes. Do not treat voids as failed refunds. Do not merge gateways when one Spreedly seat owns the fail pile.

Related: Payments, AN refund-fail, void-fail, retry-success.

Procedure

  1. Type refund fails and refund attempts.
  2. Read SP refund-fail %.
  3. Chase vault token / gateway route when SP refund-fail % is fat.

Failure modes

  • Inventing SP refund-fail %.
  • Loading Authorize.net refund rows into Spreedly boxes.
  • Folding voids 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

SP refund-fail %
Refund fails ÷ refund attempts × 100 on one Spreedly refund route cut.

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

FAQ

Is this Authorize.net refund-fail share?
Spreedly vault/route refund cut vs Authorize.net Transaction Detail desk. [Refund-fail share](/manuals/authorize-net-refund-fail-share) stays on Authorize.net. Failed / submitted refunds never leave Spreedly here.
Is this Spreedly void-fail share?
Refund misses vs void fails. [Void-fail share](/manuals/spreedly-void-fail-share) ratios void fails. This page ratios failed refunds ÷ submitted refunds.
What SP refund-fail % should I invent?
None. Pull failed refunds and submitted refunds from the same Spreedly refund route cut.