Ignoring the KYC-rejection black hole between FTD and payout

Ignoring the KYC-rejection black hole between FTD and payout

A lead deposits, you count the FTD, then the broker rejects KYC and the deposit reverses. The mistake: not tracking KYC pass-rate as a first-class metric, so you discover the loss only at payout.

Where it hides:
— Certain GEOs and traffic sources produce deposits that systematically fail document verification (mismatched names, unsupported ID types, sanctioned regions).
— Your dashboard shows the FTD; the reversal lands days later in a different report you don't watch.

The fix:
— Get the broker to send a KYC-status event (passed/pending/rejected) to your tracker, not just a deposit event. If they can't, demand a weekly KYC-outcome CSV.
— Segment KYC pass-rate by GEO and sub-ID. A source with a 60% KYC pass rate is worth far less than one at 95%, even at the same FTD price.
— Hold a 'confirmed FTD' status that only flips after KYC clears, and report on that, not raw FTDs.

Who should skip this: brokers that pay on validated-FTD only — they've already absorbed this risk into the price.

Verdict: Track KYC pass-rate explicitly.