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 vault-rail AU miss is not Authorize.net CIM-refresh

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

Open one Spreedly lifecycle AU desk. Count payment-method updater calls the network rejected. Divide by updater pulls in that desk window. The chip is SP AU-drop % — leave Solidgate settle-rail PAN pages alone.

Pair: Account-updater fail share on Payments. Solidgate twin: SG PAN-refresh. CIT twin: SP CIT fail.

Lifecycle AU fields

AU drops — Spreedly lifecycle payment-method updater calls the card network rejected.

AU pulls — Spreedly lifecycle payment-method updater calls attempted in that same desk window.

SP AU-drop % = AU drops ÷ AU pulls × 100. A fat SP AU-drop % chip means repair Spreedly network enrollment on that gateway — blank chips stay blank.

Hard stops

Do not invent SP AU-drop %. Do not fold CIT or MIT declines into AU fields. Do not load vault-token fails into AU pulls. Do not dump Solidgate settle-rail or NMI gateway AU CSVs into Spreedly boxes. Do not blend gateways when one lifecycle desk owns the drop pile.

Related: Payments, SG PAN-refresh, SP CIT fail, SP vault-token.

Procedure

  1. Type updater fails and updater tries.
  2. Read SP card-refresh miss %.
  3. Repair Spreedly network enrollment when SP card-refresh miss % is material.

Failure modes

  • Inventing SP card-refresh miss %.
  • Folding CIT or MIT declines into AU fields.
  • Dumping Authorize.net CIM-refresh or NMI gateway AU CSVs into Spreedly boxes.

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 card-refresh miss %
Hard-fail card refreshes ÷ refresh attempts × 100 on one Spreedly vault-rail export.

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

FAQ

Is this Solidgate account-updater fail share?
Spreedly lifecycle AU desk vs Solidgate settle-rail PAN refresh. [Account-updater fail share](/manuals/solidgate-account-updater-fail-share) stays on Solidgate. AU drops / AU pulls belong on this Spreedly lifecycle desk.
Is this Spreedly CIT fail share?
Lifecycle account-updater drops vs shopper-started charge declines. [CIT fail share](/manuals/spreedly-cit-fail-share) ratios CIT declines. Here you only ratio AU drops against AU pulls.
What SP AU-drop % should I invent?
None. Pull AU drops and AU pulls from the same Spreedly lifecycle AU desk.