Spreedly vault funding-confirm miss ledger is not token-rail funding-ack miss clock

Open one Spreedly vault funding-confirm miss ledger. Count mute funding confirms that never cleared when the vault had them booked. Divide by booked funding confirms on that ledger. Multiply by 100 for SP funding-confirm-miss %. Token-rail funding-ack miss clocks, Authorize.net merchant funding-confirm racks, and vault funding-batch miss ledgers stay off this funding-confirm cut.

Pair: Funding-confirm miss share on Payments. Funding-ack twin: SP funding-ack-miss. Authorize.net twin: AN funding-confirm-miss.

Vault funding-confirm fields

Missed funding confirms — Spreedly funding confirms the vault funding-confirm miss ledger marked booked but that stayed mute.

Expected funding confirms — Spreedly funding confirms that ledger had booked in the same vault window.

SP funding-confirm-miss % = missed funding confirms ÷ expected funding confirms × 100. When SP funding-confirm-miss % climbs, chase funding-confirm delivery on that vault — never invent an SP funding-confirm-miss chip.

Guardrails

Skip inventing SP funding-confirm-miss %. Skip folding mute funding acks or empty funding batches into the mute-confirm tally. Skip dumping Authorize.net merchant funding CSVs into Spreedly vault boxes. Skip blending vaults when one Spreedly vault funding-confirm miss ledger owns the mute pile.

Related: Payments, SP funding-ack-miss, AN funding-confirm-miss, SP funding-batch-miss.