Authorize.net merchant funding-confirm miss rack is not NMI gateway funding-confirm miss book

Pin one Authorize.net merchant funding-confirm miss rack. Tally silent funding confirms that never posted when the merchant had them booked. Divide by booked funding confirms on that rack. Multiply by 100 for AN funding-confirm-miss %. NMI gateway funding-confirm books, merchant funding-ack miss racks, and merchant funding-batch miss racks stay off this funding-confirm cut.

Pair: Funding-confirm miss share on Payments. NMI twin: NM funding-confirm-miss. Funding-ack twin: AN funding-ack-miss.

Merchant funding-confirm fields

Missed funding confirms — Authorize.net funding confirms the merchant funding-confirm miss rack marked booked but that stayed silent.

Expected funding confirms — Authorize.net funding confirms that rack had booked in the same merchant window.

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

Hard stops

Never invent AN funding-confirm-miss %. Never fold silent funding acks or empty funding batches into the silent-confirm tally. Never paste NMI gateway funding CSVs into Authorize.net merchant boxes. Never blend merchants when one Authorize.net merchant funding-confirm miss rack owns the silent pile.

See also: Payments, NM funding-confirm-miss, AN funding-ack-miss, AN funding-batch-miss.