Solidgate processor funding-confirm miss ledger is not Primer orchestrator funding-confirm miss desk

Pin one Solidgate processor funding-confirm miss ledger. Tally silent funding confirms that never posted when the processor had them booked. Divide by booked funding confirms on that ledger. Multiply by 100 for SG funding-confirm-miss %. Primer orchestrator funding-confirm desks, processor funding-ack miss ledgers, and processor funding-window miss ledgers stay off this funding-confirm cut.

Pair: Funding-confirm miss share on Payments. Primer twin: PR funding-confirm-miss. Funding-ack twin: SG funding-ack-miss.

Processor funding-confirm fields

Missed funding confirms — Solidgate funding confirms the processor funding-confirm miss ledger marked booked but that stayed silent.

Expected funding confirms — Solidgate funding confirms that ledger had booked in the same processor window.

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

Hard stops

Never invent SG funding-confirm-miss %. Never fold silent funding acks or empty funding windows into the silent-confirm tally. Never paste Primer orchestrator funding CSVs into Solidgate processor boxes. Never blend processors when one Solidgate processor funding-confirm miss ledger owns the silent pile.

See also: Payments, PR funding-confirm-miss, SG funding-ack-miss, SG funding-batch-miss.