# Watch accounts and alert on new or unusual transactions

> Watch accounts and alert on new or unusual transactions: 5 companies fully do it, 4 with a limit, 16 carry the tag. Every listing in Bank data & open banking with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/banking-data.watch-alert/
- Markdown: https://www.anchorterminal.com/niches/banking-data.watch-alert/index.md (~1,400 tokens)
- Slim: https://www.anchorterminal.com/niches/banking-data.watch-alert/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/banking-data.watch-alert/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 5 | 4 | 16 | 7 | 3 |

## What counts as done

A webhook or scheduled check reports a new matching transaction to the channel, and states when the account was last refreshed.

Measured, for our own tests: the alert arrives within the provider's stated refresh interval.

How agents ask for it: tell me when a big charge lands; alert me if my balance drops below 500; watch for my salary; notify me about new transactions

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **BankMCP (noskillish (open-source project))**: create_watch rules (balance threshold, large debit, payee match, missing payment) post to a webhook; watches store last_checked and a consent_expiring event fires 7 days ahead. Checks run at most four times a day.
- **MX Platform API (MX Technologies, Inc.)**: The webhook index lists Transactions webhooks for created, updated or deleted transactions and Aggregation webhooks with counts of new data; members carry aggregated_at. Default aggregation is about every three hours.
- **Plaid (Plaid Inc.)**: SYNC_UPDATES_AVAILABLE fires when new transactions arrive, checks run one to four times a day by institution, and /item/get reports last_successful_update for freshness.
- **Powens (Powens SAS)**: CONNECTION_SYNCED and USER_SYNCED webhooks deliver new data after each synchronisation for permanent users, and accounts carry last_update for freshness.
- **Tink (Tink AB)**: account-booked-transactions:modified and account-transactions:modified webhooks fire on new, updated or deleted transactions with the earliest and latest modified dates, and refresh:finished marks each refresh.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Belvo (Belvo Tecnologias Ltda.)**: new_transactions_available fires after each recurrent refresh, but the default refresh is every seven days, so alerts lag by up to a week unless a faster rate is bought.
- **Flinks (Flinks Technology Inc.)**: Webhooks deliver data after a refresh, but nightly refresh is at most daily and fails for banks needing MFA, so watches go quiet for part of the base.
- **Salt Edge Account Information (Salt Edge Limited)**: Success callbacks fire whenever a connection's data changes and background_refresh exists, but the callback names the connection, not the transaction, so the agent re-reads to find what is new.
- **Yodlee Core API (Yodlee, Inc.)**: Notification events can be subscribed for data updates and refreshes, and accounts carry lastUpdated, but the event payload signals that data changed, not which transaction, so the agent must re-read.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Basiq (Basiq Pty Ltd)**: Webhooks cover users and consents 'to name a few'; the event-type list is served by an authenticated API call, so whether a new-transaction event exists was not established.
- **Teller (Teller, Inc.)**: Not read: teller.io's robots.txt disallows ClaudeBot, Claude-Web and anthropic-ai, so the docs were not fetched.

- not this job: Akoya (Akoya LLC): Webhooks carry only maintenance and consent events; there is no transaction event, so the agent polls.
- not this job: Enable Banking (Enable Banking Oy): Webhooks cover payment status only; account data must be polled by the agent, at most four times a day in the background.
- not this job: GoCardless Bank Account Data (GoCardless Ltd): The Bank Account Data endpoints and guides show no data webhooks; the agent must poll under bank caps as low as four calls a day per endpoint.
- not this job: TrueLayer (TrueLayer Limited): Data API webhooks only signal that an async request finished; there is no new-transaction event, so the agent polls under bank caps.
- not this job: Yapily (Yapily Ltd): Webhook categories cover payment status, async processing and categorisation completion; none fires on a new account transaction, so the agent polls under the four-a-day cap.

## What stops agents finishing

- four unattended reads a day, so alerts lag
- consent lapses with no event, so the watch goes quiet

## Around it

Before: banking-data.connect-consent. After: notifications.push, messaging.send.

## Where this comes from

Weight 7 of 100 in Bank data & open banking: 3 of 41 accounts (Leggen alerts, Driggsby big-charge detection, Tiller anomaly finding); BankMCP and Plaid document watches and webhooks

As data: https://www.anchorterminal.com/api/v1/use-cases/banking-data.watch-alert.json, or the MCP tool get_use_case with id banking-data.watch-alert. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
