The Linked Accounts: Four Accounts Get Past a Per-Person Position Limit
Account 7741 holds 4,000 contracts, under the limit. With three linked accounts, the group holds 24,000 of a 25,000 limit. At five past nine, account 7741 opens. It's funded from the same bank account as three accounts opened this week, and the job that links them runs tonight. Late in the morning the three older accounts buy 20,000 contracts on one event. The position limit is 25,000 per person. Then the new account buys 4,000 of the same contract. The order check sees 4,000. The group holds 24,000. Five minutes later the new account orders 10,000 more. The check only knows about one account, so it accepts. The group now holds 34,000, well past the limit for one person. Then the same morning with the order check reading from Tacnode. It finds the shared funding source, adds up all four accounts, and holds the order. Onboarding, payment and order data stream into Tacnode. When an order comes in, the check finds the accounts tied to it and adds up what they hold. Its verdict is written back, so the next order from the group sees it. Your surveillance rules and vendors stay.
Overview
One of the fourteen Pipelies lies: how accounts that only get linked by a nightly job get past a per-person position limit, and the same morning with the order check reading from Tacnode.
Topics Covered
- •A new account funded from the same bank account as three others
- •A linking job that runs tonight
- •20,000 contracts across the three older accounts
- •An order check that knows about one account
- •Linked accounts added up when the order arrives
Key Takeaways
- ✓The shared funding source was in the data from the day the account opened; the job that links accounts runs at night
- ✓The check saw 4,000 contracts while the group held 24,000
- ✓Reading from Tacnode, the check finds the shared funding source and adds up all four accounts
- ✓Surveillance rules and vendors stay
More Product Demos

The Frozen Score: Account Takeover Approved on a Ten-Hour-Old Risk Score
A short walkthrough of a transfer check that reads a risk score computed at 2 a.m., ten hours before someone else took over the account.

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.
Ready to get started?
Book a demo to see how Tacnode can power your real-time data infrastructure.
