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-token reject mix is not Authorize.net CIM miss

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

Sit on one Spreedly vault-token seat. Count network-token rejects. Divide by token tries. The chip is SP network-token fail % — leave Authorize.net CIM pages alone.

Pair: Network-token fail share on Payments. Authorize.net twin: AN network-token fail. Fallback twin: network-token fallback.

Vault-token columns

Network-token rejects — Spreedly vault network-token uses the seat marked failed.

Token tries — Network-token attempts inside that same Spreedly seat window.

SP network-token fail % = network-token rejects ÷ token tries × 100. A fat chip usually points at vault-token → PAN fallback lag on that Spreedly gateway — staff the vault seat; blank chips stay blank.

Hard stops

Do not invent SP network-token fail %. Do not load Authorize.net CIM rejects into Spreedly boxes. Do not fold capture fails into network-token reject counts. Do not treat coverage gaps as SP network-token fail share.

Related: Payments, AN network-token fail, network-token fallback, network-token coverage.

Procedure

  1. Type network-token fails and token attempts.
  2. Read SP network-token fail %.
  3. Chase vault-token rail when SP network-token fail % is material.

Failure modes

  • Inventing SP network-token fail %.
  • Pasting an Authorize.net CIM reject file into Spreedly boxes.
  • Dumping capture-fail rows into network-token fields.

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 network-token fail %
Network-token fails ÷ Token attempts × 100 on one Spreedly vault-token seat.

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

FAQ

Is this Authorize.net network-token fail share?
Spreedly vault-token seat vs Authorize.net CIM merchant seat. [Network-token fail share](/manuals/authorize-net-network-token-fail-share) stays on Authorize.net. Rejects / tries never leave Spreedly here.
Is this Spreedly network-token fallback?
Reject mix vs fallback path. [Network-token fallback](/manuals/spreedly-network-token-fallback) tracks fallback uses. Here you only ratio network-token rejects against token tries.
What SP network-token fail % should I invent?
None. Pull network-token rejects and token tries from the same Spreedly vault-token seat.