The Linked Accounts
Four accounts share a funding source. The job that links them runs tonight.
Account 7741 opens, funded from the same bank account as three accounts opened this week.
Where this shows up
Why the ETL job gets it wrong
The data that links accounts, such as devices, funding sources and identity checks, lives in onboarding and payment systems, away from the orders. So the links get worked out by a batch job or a surveillance vendor, usually overnight. Until it runs, the order check only knows about one account at a time.
By the time the decision ran, its context was incomplete. We call that a context gap.
Add up the linked accounts when the order arrives.
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 on this event and related ones, then writes its verdict back so the next order from the group sees it.
If an engineer asks how
Linked accounts and their positions are found on demand against committed data when the order runs. If the link search is too expensive at peak, the groups become a view refreshed on a schedule you set.
Questions to put to your team
- How quickly can you see that several accounts are trading the same event together?
- Does your pre-trade check include every account the customer controls?
- When did your linking job last run?
Is your pre-trade check telling this lie?
Bring it to a demo, and we’ll trace what it reads and how old that data is by the time it runs.
Book a demo →