Rank merchant-test sequences within review capacity
Early warning signals can look harmless until they form a costly sequence.
Catching more risk can also create work that obscures the cases that matter.
“I can replace a card, but I don’t want every normal purchase turning into a fire drill.”
Mads Persson · Head of Finance
Oversees employee card access at a growing venture-backed company with frequent SaaS and travel spend.
What pulls against what
- early intervention vs. false-positive burden
- sequence recall vs. reviewer capacity
- network signals vs. local transaction context
- loss prevention vs. cardholder continuity
What is at stake
Missed early signals can turn into larger card losses. Over-alerting, however, can disrupt legitimate company spending and overwhelm review teams
Why Mercury
For Mercury, it tends to matter when card controls must protect customer funds without unnecessarily interrupting legitimate spend.
Written for
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.