The Frozen Score: Account Takeover Approved on a Ten-Hour-Old Risk Score
The risk score says low. It was computed at 2 a.m., and at noon someone else took over the account. This one follows a single customer through four moments. At 2 a.m. the nightly job scores every customer, and this one comes out low risk. Just after noon the email and phone number on the account both change. Two minutes later there's a new payee and a higher transfer limit, and two minutes after that a large transfer goes to that payee. The check reads the feature store, which still holds the score from 2 a.m., and approves it. Nothing failed. The score was ten hours old. Then the same four moments with the check reading from Tacnode: same events, same model. This time the check reads what just happened (the changed email, the new payee, the higher limit) and holds the transfer. Account changes stream into Tacnode from the systems you already run, and you choose how fresh each feature has to be. The ones a transfer depends on are computed when the check asks. The hold is written back, so the next check knows about it.
Overview
One of the fourteen Pipelies lies: why a transfer check approved a payment on a risk score that was ten hours old, and the same moments with the check reading from Tacnode.
Topics Covered
- •A nightly job that scores every customer at 2 a.m.
- •An email, a phone number, a payee and a transfer limit changed within four minutes
- •A feature store still handing out last night's score
- •The same check reading what just happened
- •The hold written back for the next check
Key Takeaways
- ✓Nothing failed: the check read a score that was ten hours old
- ✓The model and the events are the same in both runs; only what the check reads changes
- ✓You choose how fresh each feature has to be, and the ones a transfer depends on are computed when the check asks
- ✓When the hold is written back, the next check knows about it
More Product Demos

The Peak-Hour Lag: A Velocity Check Counts 3 Card Attempts Out of 9
A short walkthrough of a velocity check that reads a replica at the lunch peak and counts three card attempts when there were nine.

The Agent's Alibi: Two AI Agents Overspend One $5,000 Budget
A short walkthrough of two agents that each read a $5,000 budget and between them commit $7,500.

The Stale Segment: A Welcome Offer for a Customer with Six Orders Today
A short walkthrough of a campaign engine that reads last night's segment and sends a 20% welcome offer to a customer with six orders today.
Ready to get started?
Book a demo to see how Tacnode can power your real-time data infrastructure.
