Fraud holds that reach authorization too late
Card authorization approves six purchases on an account already on hold, because the hold is still moving through a pipeline.
An identity check flags a new application from account R1’s device.
- Application R2 comes in from the same device as R1, an open card account at the lender.
- The lender’s identity check links the two and flags R2 for the fraud team.
- Card authorization checks account status before every purchase. It reads that status from a cache, which a pipeline keeps in step with the case system.
Illustrative scenario. Timings show the shape of the problem, not a measurement of any one company.
Watch the walkthrough
Your stack today, and with the Tacnode Context Lake™
Today
Most lenders keep fraud decisions in a case system and card authorization in another, joined by a pipeline: change capture, a stream, a stream job, a cache. That was fine when fraud moved at human speed. Rings that open accounts with stolen identities now run AI agents that spend the moment an account is live, in bursts that last a few seconds. Authorization reads account status from the far end of the pipeline, and the agent spends during the delay.
With the Tacnode Context Lake™
- The hold was readable once committedThe case system wrote it where authorization reads, with no pipeline in between.
- Agents spend in secondsA few seconds between a decision and the system that acts on it is enough to empty a card.
- Every decline was savedThe next check on that device or that ring reads all six.
Questions to ask your team
- 1When your fraud team places a hold, how long until card authorization declines on it?
- 2Have you seen bursts of card-not-present purchases on an account in the seconds after it was flagged?
- 3Do your fraud decisions and your authorization path read account status from different systems?
Go deeper
More replays
All replaysCard issuing
False declines on newly issued virtual cards
A store card approved at checkout is declined on its first purchase, because the fraud check can’t yet tie it to the customer’s history.
AI customer support
Duplicate credits from concurrent AI agents
Three AI support agents each give one customer a goodwill credit, because each checks a synced copy of credits that hasn’t received the others yet.
Sports betting
Late market suspension in in-play betting
After a goal, a sportsbook accepts bets at the pre-goal price for seven seconds, because the suspension reaches bet acceptance through the odds pipeline.

