The economics of synthetic fraud push toward scale. Building one fabricated
identity and raising it into a creditworthy customer takes patience; the effort
only pays if it can be repeated. So the same operator tends to run many
accounts at once, and running many accounts efficiently means reusing the same
plumbing. That reuse is the fifth signal.
The shared trail
Accounts that were manufactured together tend to overlap in ways real,
unrelated members do not:
- Shared funding sources. The money that seeds or feeds several
accounts traces back to the same counterparty, the same originating account,
the same handful of instruments.
- Shared payees. Different "people" who supposedly have nothing to do
with each other keep paying the same destinations, moving money to the same
places on the way out.
- Clustered openings. Applications and account openings bunch in time
and sometimes in channel, a batch of new members that all appeared in the
same narrow window and then behaved alike.
- Parallel lifecycles. The accounts move through provenance,
coherence, ramp, and inflection on similar schedules, because they were
started and worked together.
None of these is proof on its own. Real people share landlords, use the same
popular payment apps, and open accounts during the same promotion. The signal
is not a single shared edge; it is a cluster of accounts that share
plumbing and each independently show the earlier tells.
Why one flag should widen the search
Here is the practical instruction that follows from all five notes. When a
single account trips the earlier signals, the right next move is not to close
the file on that one account. It is to ask who its neighbors are: which other
accounts share its funding source, its payees, its opening window. A lone
flagged account is a question. A neighborhood of accounts that share plumbing
and independently show the same behavioral signature is a different kind of
answer, and it is usually a bigger one than the first account suggested.
This is also why the ring signal is the one a single-account view structurally
cannot see. If you look at accounts one at a time, the shared funding source is
just a counterparty on one statement. It only becomes a cluster when you can
place many accounts side by side and notice they lean on the same few nodes.
The relationship is the evidence, and relationships are invisible unless you
are explicitly looking across the book rather than down a single account.
The payoff is leverage. The work of confirming one flagged account is
substantial; the marginal work of asking which accounts share its plumbing is
small, and it frequently turns a single finding into a set. A cluster is also
easier to act on with confidence than a lone account, because independent
accounts arriving at the same behavioral signature through the same shared
nodes is a coincidence that gets less plausible with every additional member
of the cluster. One account can be explained away. A neighborhood behaving
identically is harder to wave off, and cheaper to have found by looking than
by waiting for each one to bust out on its own.
Reading the five together
That completes the series. Provenance asked whether an economic origin ever
showed up. Coherence asked whether a life was actually lived through the
account. Ramp asked whether its appetite for credit outran its real income.
Inflection asked whether it broke from its own pattern all at once near the
end. Ring asks whether it was doing all of that alongside a cluster of accounts
doing the same thing.
No single signal is a verdict, and none of them requires a bureau, a
consortium, or a subpoena. They live in data an institution already holds, read
backward, each account measured against its own history and, in the end,
against its neighbors. That is the whole method: not a smarter gate at signup,
but an honest look at what the accounts already on the book actually did.
Sources & notes
This is a conceptual,
operator-facing description of one behavioral signal. It makes no factual
claims about any specific institution, portfolio, or case, cites none, and
describes no Delegate engagement or result. The relationships it names
(shared funding counterparties, shared payees, clustered openings) are
ordinary properties of account data. You can see the signal families run on
a simulated book in the Portfolio Explorer.
Field notes
New teardowns and notes on how synthetic losses hide, sent occasionally.
Occasional field notes on synthetic fraud, plus Delegate product updates. Unsubscribe anytime.